Comments on LC issues

These are the comments and suggestions by the "gSOAP project group" on the
LC working drafts of SOAP 1.2 specifications.

The comments below were carefully evaluated in our current gSOAP
prototype implementation of the SOAP 1.2 working drafts.

1. SOAP RPC return value accessor is ambiguous and imposes unnecessary
   processing complexities (as explained by us in an earlier message).

2. Section in "SOAP 1.2 Adjuncts" forbids id and ref attribute
   information items to appear in the same element information item.
   It is our opinion that this constraint unnecessarily limits the
   object graph data model. The resulting admissible data model does
   not allow for "pointer chain" graphs (as explained by us in an
   earlier message).

3. To comment on the Editor's request for comments on "generics":

      It is our opinion that generics should be kept in the specification.
      Generics are useful mainly from a practical point of view because
      generics do not widen the gap between SOAP RPC and SOAP DOC/LIT
      data models. We believe that abolishing generics only widens this
      data modeling gap, thereby unnecessarily limiting the expressiveness
      of the data model of SOAP RPC.

4. We do not oppose the array representation of SOAP RPC invocation.
   However, we do strongly suggest the use of generic types to support
   both struct and array parameter paradigms. In fact, it is our
   opinion that generics should be the ONLY parameter marshalling type.
   In that way, polymorphic remote methods and remote methods with
   variable number of parameters can be supported, while providing a
   similar functionality as parameter marshallings based on structs
   and arrays.

Best regards,

- Robert van Engelen, gSOAP project group.
  Dept. of Computer Science, FSU, 162LOV/471DSL
  Phone: (850)644-9661/645-0309, Fax: (850)644-0058
  Email:, URL:

Received on Friday, 19 July 2002 16:01:06 UTC