• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

.NET doesn't Serialize Java Set

 
Luigi Smith
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have a webservice that wraps some Java objects to send them over the wire. The problem is that these Java objects contain references to each other (ie. circular). It's fine from our end because we use SOAP RPC style to send the object graph to the .NET layer. However, on the way back, .NET complains about our java Sets in this objects. It looks like it's trying to convert to arrays.

Has anyone had any experience with this dilemna?

Thanks,
 
Balaji Loganathan
author and deputy
Bartender
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Luigi Smith:
However, on the way back, .NET complains about our java Sets in this objects. It looks like it's trying to convert to arrays.


Are you able to generate .NET stubs for the given WSDL ?
What complains are you getting from .NET?
 
Luigi Smith
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, WSDL generation is fine, but we at runtime it says there is an invalid type. I can provide more details when I return to work next week.

Thank you,
Lou
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It would help if you could post the relevant parts of your WSDL document for us to see.

(PS. remember to use the UBB CODE tags for code snippets)
 
Luigi Smith
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks folks for taking a look. Here's the information.

The following is the error I receive:

Invalid Request for setTestObject
com.bea.wlw.runtime.core.request.RequestValidationException: Error
deserializing arguments.
Encountered an xml tag without a recognized type: the type must be
declared with an xsi:type attribute.
Caused by: com.bea.xml.marshal.XmlEncodingException: Encountered an xml
tag without a recognized type: the type must be declared with an
xsi:type attribute.


Here's the WSDL file for the functions were concerned with (Note: this is a partial WSDL from what BEA generated):

[Balaji]Deleted the Code Section for better reading, see the next reply for code section please.
[ August 24, 2004: Message edited by: Balaji Loganathan ]
 
Luigi Smith
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here's a better post with smilies disabled: ;)


[ August 24, 2004: Message edited by: Balaji Loganathan ]
 
Consider Paul's rocket mass heater.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic