I have a simple service that returns an unbounded array containing custom objects generated/altered by JiBX to provide XML binding. When I invoke the service, it executes OK on the server side, but on the client side I get a SoapFault: [ID = 'NoSerializer']. The message also mentioned that I "must include a custom-serializer element for this type in the deployment descriptor.
I thought that at one point I had a working web service returning an Array of custom Objects without a custom serializer, but I may be wrong. Is this possible? Also, while there appear to be several custom serializer examples here on the forum, it looks like they are all created and registered in startup code, rather than in a deployment descriptor. Could someone post an example of how a custom serializer is initialized in a deployment descriptor (identifying which deployment descriptor, and where and how the initialization should be inserted) or point to an existing example if one is already posted? Lastly, are there any obscure pitfalls when creating custom serializers in conjunction with JiBX, or is it simple a matter of using the standard JiBX marshalling/unmarshalling contexts? -- View this message in context: http://www.nabble.com/Creating-a-Serializer-for-JiBX-altered-classes-tp14327762p14327762.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
