Hi. I've download the Castor serializers and used the IBM article code.
However, I still can't get AXIS to do certain things.. The client is what I am writing. I want to connect to a server, which runs GSoap, and use my generated classes to get an XML representation of what is on the server. However, I can't seem to be able to use my generated classes much - it always uses a StringHolder, or <typeName>Holder. The castor classes don't seem to be used much. Does the server need to be running AXIS in order to use the generated classes properly? On a seperate type of question, is there any way of getting the raw SOAP data (i.e. the XML) through AXIS, or is that level of detail always hidden from the developer with AXIS? Thanks for your help. James Carbone Cedric <[EMAIL PROTECTED]> 21/01/2004 14:55 Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject RE: Using Castor with AXIS Hi James, This is the URL in Axis CVS to download the stuff you search : http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/encoding/ ser/castor/ I hope this URL help U. Cheers, Cedric Carbone Neopost Industrie [EMAIL PROTECTED] --------- For your information, i used, thanks an IBM tutorial ( see IBM's article http://www-106.ibm.com/developerworks/webservices/library/ws-castor/ ), Castor XML into Axis, 3 months ago. However, I have finded bugs with WSDL2Java tool when my message is complex (in fact, where my XSD is complex). Today, I haven't fix the problem with complex XML Schema so I use Castor XML outside Axis framework. This is my message I sended 3 months ago on axis-mailing list : --- The problem (described in this article) happens when I use the WSDL2Java tool, with my WSDL (my WSDL import a complex XSD file (between <types> tags)). For each complexType, WSDL2Java generate an invalid XML by misplacing a fex '<' and '>' in the output. For example, in the WSDD file, the qname attribut of typeMapping tag contains 'ns:>message>request>elem' <typeMapping xmlns:ns="http://neopost.com/schema"; qname="ns:>message>request>elem" type="java:com.neopost.schema._message_request_elem" serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" encodingStyle="" /> I think the problem is that WSDL2Java replaces each underscore in the name of data classes (this classes will be replace by Castor XML generation) with > in WSDD file. So the class com.neopost.schema._message_request_elem (type attribute) becomes ns:>message>request>elem (qname attribute). Note that this bug appears not only on a WSDD generated file. For example, in a MessageSOAPBindingStub class, I get : qName = new javax.xml.namespace.QName("http://neopost.com/schema";, ">message>request>elem"); in the constructor. Note that I use Axis 1.1 from CVS version (because the version 1.1 final don't contain org.apache.axis.encoding.ser.castor.* package). Would you have any suggestion that might help me to solve my problem ? Do you think this could be fixed in a near future. I found the idea of mixing Axis and Castor capabilities really appealing but I would not recommend to use it as it is because of a obvious lack of "polish". Regards, ___ Cedric Carbone Neopost Industrie [EMAIL PROTECTED] -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoye : mercredi 21 janvier 2004 15:40 A : [EMAIL PROTECTED] Objet : Using Castor with AXIS Hi. I'm relatively new to using AXIS, but have been using Castor for some time. Currently I generate classes using Castor, and also need to generate similar classes (only on the client side) for Axis using the WSDL2Java tool. I have seen org.apache.axis.encoding.ser.castor mentioned in some posts, but cannot find it in CVS, or the 1.1 version of Axis which I have downloaded. I understand this might help me. As I need to only do client side, is there any document that describes how to go through the process of using Castor generated classes on client side with Axis? Any help would be appreciated. Thanks James This email is intended solely for the use of the named addressee(s). Any unauthorised disclosure, copying or distribution of the confidential information contained therein, or the taking of any action based on it, is prohibited. The sender disclaims any liability for the integrity of this email. Legally binding declarations must be in written form.
