Hi Randal.. We're using xmlbeans with the current axis-port in jbossws which I think is based on Axis 1.1. I suggest you create your axis webservices as "message-style" services (if I remember correctly your methods get/return a Document/Element) and then "manually" do the deserialization/serialization to/from xmlobjects in your service (using the XmlObject.parse/newDomNode methods). It may not be the "cleanest" solution but you wont have any hassle with custom (de)serializers and will have full control of the message content.
If you choose this solution there might be some "horrible" performance bottlenecks in Axis that may need to be fixed, mail me and I'll point you to my jbossws fixes (which essentially fix the axis code). good luck! regards, Ole -----Ursprungligt meddelande----- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Skickat: to 9/22/2005 7:45 Till: user@xmlbeans.apache.org Ämne: XmlBeans and Axis - Serializer/Deserializer question Hello all, This may have been answered already, but, I can't seem to find a solution. I am constrained to using XmlBeans 1.0.4 and Axis 1.1. I can't seem to pass an XmlBean object from a client to a webservice. I have created a document style service method, set up the appropriate WSDL (importing the schema files that were used to generate the XmlBeans), and failed miserably trying to write custom (de)serializers. I've seen a few references through Google about a set of XmlBeans specific (De)serializers located at a specific web URL (Which I can't seem to connect to, I get a 404 error). Can anyone point me in the right direction? I find it hard to believe that I am the only user of XmlBeans that is trying to send one to a web service and needs help doing so. Thanks in advance! Randy ----------------------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
