Hi David, The Muse samples have all the basic features I think you need. The apache-httpd sample shows how to create and configure custom serializers on both the server and client side.
The general idea is that Muse has default serializer support for primitive types and a few basic complex types (i.e. Date, Element). For all other custom types that you expose directly to Muse either as operation input or output, you need to also configure your own serializers. This way, Muse can know how to serialize/deserialize your custom types. -Vinh -----Original Message----- From: david2 [mailto:[EMAIL PROTECTED] Sent: Friday, December 14, 2007 7:37 AM To: [email protected] Subject: Re: Creating a Serializer for JiBX-altered classes Just found the example I was needing (of initializing a custom serializer in the (muse) deployment descriptor. It is in the sample at <Muse install dir>\samples\j2ee\apache-httpd\config\muse.xml (at the very end of the file). Here is the snippet: ... </init-param> </capability> </resource-type> <custom-serializer> <java-serializable-type>org.apache.muse.test.http.SupportedLanguage</jav a-serializable-type> <java-serializer-class>org.apache.muse.test.http.SupportedLanguageSerial izer</java-serializer-class> </custom-serializer> </muse> -- View this message in context: http://www.nabble.com/Creating-a-Serializer-for-JiBX-altered-classes-tp1 4327762p14337930.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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
