aspose file tools
The moose likes Web Services and the fly likes Complex data type serialization (JWSDP) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Complex data type serialization (JWSDP)" Watch "Complex data type serialization (JWSDP)" New topic

Complex data type serialization (JWSDP)

Venkatesh Krishnappa

Joined: May 26, 2003
Posts: 16
I have an immediate issue to be resolved related to handling complex data types and Iam stuck there. Please help me in finding a solution.
I have Axis 1.1RC1 enabled JRun web server, which publishes my web services (server)
On another machine, Iam using JWSDP 1.1 with tomcat for accessing the services (as a client)
everything goes well when Iam returning primitive types and even with bean kind of complex types (yes, after adding a SerializerFactory and typemapping).
now, I added a HashMap member variable in this complex type, which is a return value.
I generated the wsdl using Java2WSDL at the axis end.
then I tried using 'ant generate-stubs' on the generated wsdl at the JWSDP end, but I encountered a problem saying 'modeler error: unsupported type Map'
My questions are :
my config.xml has <wsdl> and not <service>. How can I specify the type mappings when wsdl is present ?
I can't have <service> because the web services implementation is not on JWSDP, instead it's on Axis. It's not an RMI implementation and hence I don't have any information for interface name and servant name to put in config.xml.
I know wsdl contains information about those complex return types, then why don't 'ant generate-stubs' can generate serializers for them like the way it did for a java bean type of my complex type. Iam totally lost at this point.
Iam using HashMap, but the 'ant generate-stubs' complains about the Map interface. any clue why it goes by the interface name ?

If the above explaination is a bit confusing, then please let me know how to handle java collection classes and nested custom types in this kind of architecture scenario.
I would be very grateful if you can throw some ideas regarding this.
I agree. Here's the link:
subject: Complex data type serialization (JWSDP)