Hi Srinivas, Thanks this works.
I made this to work by copying just "axis.jar" from a latest nightly build to my existing 1.1RC2 build. Do you think, it is preferable to release in our production with just updating axis.jar like this or do u prefer taking complete nightly build for installing in our production env? Thanks Swamy -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2003 3:14 PM To: [EMAIL PROTECTED] Subject: RE: Document Style web service bug yes, use latest nightly build. --- Anjaneya Swamy Varada <[EMAIL PROTECTED]> wrote: > Hi Srinivas, > > Thaks for the response. > > I am using Axis 1.1 RC2 and it looks like in 1.1 RC2 > org.apache.axis.encoding.XMLType doesn't > has "SOAP_DOCUMENT" as a field. Can we make this to work with 1.1 RC2? should I get > recent > nightly build? Do you know the stable version of recent nightly builds? > > Thanks > Swamy > > > -----Original Message----- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 11, 2003 2:27 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: Document Style web service bug > > > Try this... > > --- Anjaneya Swamy Varada <[EMAIL PROTECTED]> wrote: > > Hi Bhanu, > > > > Were you able to create a "message" style service using the below signature: > > > > org.w3c.dom.Document parseData(org.w3c.dom.Document doc){ > > // logic processed > > return doc; > > } > > > > When I am trying to invoke the server I get the following error: > > > > java.io.IOException: No serializer found for class > > org.apache.xerces.dom.DeferredDocumentImpl > in > > registry [EMAIL PROTECTED] > > at > > > org.apache.axis.encoding.SerializationContextImpl.serializeActual(SerializationContextImpl.java:1273) > > at > > org.apache.axis.encoding.SerializationContextImpl.serialize(SerializationContextImpl.java:787) > > at > > > org.apache.axis.encoding.SerializationContextImpl.outputMultiRefs(SerializationContextImpl.java:858) > > at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:155) > > at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:413) > > at org.apache.axis.message.MessageElement.output(MessageElement.java:779) > > at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:270) > > at org.apache.axis.SOAPPart.getAsString(SOAPPart.java:483) > > at org.apache.axis.SOAPPart.getAsBytes(SOAPPart.java:375) > > at org.apache.axis.Message.getContentType(Message.java:400) > > at > > org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:341) > > at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:122) > > at > > org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71) > > at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150) > > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120) > > at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180) > > at org.apache.axis.client.Call.invokeEngine(Call.java:2526) > > at org.apache.axis.client.Call.invoke(Call.java:2515) > > at org.apache.axis.client.Call.invoke(Call.java:2210) > > at org.apache.axis.client.Call.invoke(Call.java:2133) > > at org.apache.axis.client.Call.invoke(Call.java:1656) > > at messages.TestLogMsgWithDocument.doit(TestLogMsgWithDocument.java:49) > > at messages.TestLogMsgWithDocument.main(TestLogMsgWithDocument.java:62) > > > > Any ideas? > > > > Thanks > > Swamy > > > > > > -----Original Message----- > > From: Bhanu Pabreja [mailto:[EMAIL PROTECTED] > > Sent: Monday, May 05, 2003 7:43 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Document Style web service bug > > > > > > Great idea I will try to implement it tommorow but I hope it will process to > > do this method ... > > > > org.w3c.dom.Document parseData(org.w3c.dom.Document doc){ > > // logic processed > > return doc; > > } > > > > -----Original Message----- > > From: Rajal Shah [mailto:[EMAIL PROTECTED] > > Sent: Monday, May 05, 2003 6:44 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Document Style web service bug > > > > > > Dumdum (BP) > > > > You don't really need to create a WSDL, (look at my sample I provided you).. > > The service in my example code it good enough to be deployed as is.. You can > > deploy it and get the WSDL definition directly using the ?WSDL query on your > > service. > > > > -- > > Rajal > > > > > > -----Original Message----- > > From: dumdum 420 [mailto:[EMAIL PROTECTED] > > Sent: Monday, May 05, 2003 3:14 PM > > To: [EMAIL PROTECTED] > > Subject: Document Style web service bug > > > > > > I have generated a wsdl file using Java2WSDL utility : > > > > <?xml version="1.0" encoding="UTF-8"?> > > <wsdl:definitions targetNamespace="urn:firmTaxonomy" > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > > xmlns:impl="urn:firmTaxonomy" xmlns:intf="urn:firmTaxonomy" > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > <wsdl:types> > > <schema targetNamespace="" xmlns="http://www.w3.org/2001/XMLSchema";> > > <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> > > <element name="in0" type="xsd:string"/> > > <element > > name="fetchTaxonomyPreferredTermBranchOnBasisOfPreferredTermIDReturn" > > type="xsd:string"/> > > <element name="in0" type="xsd:string"/> > > <element name="fetchTaxonomyPreferredTermOnBasisOfPreferredTermIDReturn" > > type="xsd:string"/> > > <element name="in0" type="xsd:string"/> > > <element name="in1" type="xsd:string"/> > > <element name="fetchTaxonomyPreferredTermBranchReturn" > > type="xsd:string"/> > > <element name="in0" type="xsd:string"/> > > <element name="in1" type="xsd:string"/> > > <element name="fetchTaxonomyPreferredTermReturn" type="xsd:string"/> > > <element name="fetchFirmTaxonomyReturn" type="xsd:string"/> > > </schema> > > </wsdl:types> > > > > <wsdl:message name="fetchTaxonomyPreferredTermBranchResponse"> > > > > <wsdl:part element="fetchTaxonomyPreferredTermBranchReturn" > > name="fetchTaxonomyPreferredTermBranchReturn"/> > > > > </wsdl:message> > > > > <wsdl:message > > name="fetchTaxonomyPreferredTermBranchOnBasisOfPreferredTermIDRequest"> > > > > <wsdl:part element="in0" name="in0"/> > > > > </wsdl:message> > > > > <wsdl:message name="fetchFirmTaxonomyRequest"> > > > > </wsdl:message> > > > > <wsdl:message name="fetchTaxonomyPreferredTermResponse"> > > > > <wsdl:part element="fetchTaxonomyPreferredTermReturn" > > name="fetchTaxonomyPreferredTermReturn"/> > > > > </wsdl:message> > > > > <wsdl:message > > name="fetchTaxonomyPreferredTermBranchOnBasisOfPreferredTermIDResponse"> > > > > <wsdl:part > > element="fetchTaxonomyPreferredTermBranchOnBasisOfPreferredTermIDReturn" > > name="fetchTaxonomyPreferredTermBranchOnBasisOfPreferredTermIDReturn"/> > > > > </wsdl:message> > > > > <wsdl:message name="fetchFirmTaxonomyResponse"> > > > > <wsdl:part element="fetchFirmTaxonomyReturn" > > name="fetchFirmTaxonomyReturn"/> > > > > </wsdl:message> > > > > <wsdl:message > > name="fetchTaxonomyPreferredTermOnBasisOfPreferredTermIDRequest"> > > > > <wsdl:part element="in0" name="in0"/> > > > > </wsdl:message> > > > > <wsdl:message > > name="fetchTaxonomyPreferredTermOnBasisOfPreferredTermIDResponse"> > > > > <wsdl:part > > element="fetchTaxonomyPreferredTermOnBasisOfPreferredTermIDReturn" > > name="fetchTaxonomyPreferredTermOnBasisOfPreferredTermIDReturn"/> > > > > </wsdl:message> > > > > <wsdl:message name="fetchTaxonomyPreferredTermBranchRequest"> > === message truncated === ===== Davanum Srinivas - http://webservices.apache.org/~dims/ __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com
