next Server Subsystem Use Cases
up Common Use Cases
previous SOAP Message Generation
  Contents
PDF version   PostScript version

Java Interpretation

As we have already outlined in Section 1.3.2, we will utilise a superset of the Java interface to define services (i.e. remote methods). This is rendered necessary by the need to resolve the semantic mismatch between Java and SOAP method signatures: the absence of a formalism to indicate output parameters in Java. Whereas the discussion of the solution to this problem is the subject of Section 4.2, we are left with the need to extract the constitutive elements of a Java method signature--that is, a method name and a set of formal parameters, together with their passing mode. Notice the similarity with the output of the SOAP interpretation process.
next Server Subsystem Use Cases
up Common Use Cases
previous SOAP Message Generation
  Contents

Copyright © 2001 Jean-Marc Rosengard