On Tuesday 02 July 2002 15:51, Herreman, Christophe wrote: > Am I mistaken if I think that sending a java Vector, or Map or Hashmap over > the SOAP wire will not be received well in a .Net client? > > In our system design, SOAP is used for interoperability and the .NET > compatibility is important, so only primitives, and arrays or complex types > of primitives are allowed. > > The OO backend translates its content to these types to communicate to the > other side. > > Am I correct in this matter ? > The O in SOAP was spelling error ?
It should arrive well, provided that the type of the content in the collection is well-known at "the other end", in your case .NET. What types does the .NET implementation understand? And here lies the problem. What is well-known, and what is not? SOAP leaves it up to each end to figure that out, and only "publish" a limited set of "standard" types. It is funny that another inter-language technology is facing similar problems. OMG's Data Object Model, called JDO in Java is trying to bridge the objects across languages as well. It seems to me, they have been better in defining "standard" types, and allows everything else to become BLOBs. Niclas -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
