Rethinking the Java SOAP stack
Saved in:
| Title: | Rethinking the Java SOAP stack |
|---|---|
| Authors: | Steve Loughran, Edmund Smith |
| Contributors: | The Pennsylvania State University CiteSeerX Archives |
| Source: | http://www.ogf.org/pipermail/ogsa-wg/attachments/20050304/7a2261d5/attachment.pdf. |
| Publication Year: | 2005 |
| Collection: | CiteSeerX |
| Description: | — This paper examines the current SOAP APIs in Java, and in particular the Java API for XML-based RPC, commonly known as JAX-RPC, which is effectively the standard API for SOAP on the Java platform. We claim that JAX-RPC, and indeed any SOAP API that relies upon a perfect two-way mapping between XML data and native language objects is fundamentally flawed. Furthermore, we claim that the attempt JAX-RPC makes to extend the remote method invocation metaphor to SOAP services is counterproductive. We base our argument both upon experience with JAX-RPC and SOAP, and upon experience of previous distributed com-puting technologies. We argue that JAX-RPC is not capable of delivering on the SOAP design goals, but conclude by suggesting an alternate system, Alpine, which is free from many known flaws of existing systems, and should prove better able to deliver upon the promise of SOAP. I. |
| Document Type: | text |
| File Description: | application/pdf |
| Language: | English |
| Relation: | http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.536.1869 |
| Availability: | http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.536.1869 http://www.ogf.org/pipermail/ogsa-wg/attachments/20050304/7a2261d5/attachment.pdf |
| Rights: | Metadata may be used without restrictions as long as the oai identifier remains attached to it. |
| Accession Number: | edsbas.993C36FD |
| Database: | BASE |
Nájsť tento článok vo Web of Science | Abstract: | — This paper examines the current SOAP APIs in Java, and in particular the Java API for XML-based RPC, commonly known as JAX-RPC, which is effectively the standard API for SOAP on the Java platform. We claim that JAX-RPC, and indeed any SOAP API that relies upon a perfect two-way mapping between XML data and native language objects is fundamentally flawed. Furthermore, we claim that the attempt JAX-RPC makes to extend the remote method invocation metaphor to SOAP services is counterproductive. We base our argument both upon experience with JAX-RPC and SOAP, and upon experience of previous distributed com-puting technologies. We argue that JAX-RPC is not capable of delivering on the SOAP design goals, but conclude by suggesting an alternate system, Alpine, which is free from many known flaws of existing systems, and should prove better able to deliver upon the promise of SOAP. I. |
|---|