Re: axis2 rc1.4 error in wsdl2java generated stub
The runtime jars is Axis2 1.4.1, and the axis2_home is correct. (Java runtime jdk1.6.0_03) I tried with the axis command (wsdl2java) and with the ant task. Same result ... On Wed, Jan 21, 2009 at 5:28 AM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Tue, Jan 20, 2009 at 3:52 PM, Marco Rossi mros...@gmail.com wrote: Same problem. I have the web service generated with axis 1.3; the client generated with the 1.3 version compile, but with the 1.4.1 doesn't work: please check your runtime jars. you need to have Axis2 1.4.1 jars in the class path to compile the code generated with the axis2 1.4.1 thanks, Amila. must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) It's a bug? On Wed, Apr 30, 2008 at 12:27 PM, tezcan.dilshener.ext...@hvbis.comwrote: Hi I am receiving the following error in my wsdl2java generated stub for my simple service in Eclipse. The type EchoStub.EchoResponse must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) When I replace the axis2 v1.4 jars with axis2 v1.3 the error does not occur. Is there a newer version of the axis2 code gerator tools that are for v1.4? This also occurs when I use the command line version of wsdl2java.bat found under \bin directory. Cheers Tezcan -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: axis2 rc1.4 error in wsdl2java generated stub
Same problem. I have the web service generated with axis 1.3; the client generated with the 1.3 version compile, but with the 1.4.1 doesn't work: must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) It's a bug? On Wed, Apr 30, 2008 at 12:27 PM, tezcan.dilshener.ext...@hvbis.com wrote: Hi I am receiving the following error in my wsdl2java generated stub for my simple service in Eclipse. The type EchoStub.EchoResponse must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) When I replace the axis2 v1.4 jars with axis2 v1.3 the error does not occur. Is there a newer version of the axis2 code gerator tools that are for v1.4? This also occurs when I use the command line version of wsdl2java.bat found under \bin directory. Cheers Tezcan
Re: axis2 inheritance doesn't work?
Ok, thanks. On Fri, Jan 16, 2009 at 5:25 PM, Deepal Jayasinghe deep...@gmail.comwrote: The problem is due to the wsdl, even though you have changed services.xml and added the new operation. Axis2 can not generate the correct wsdl for that method, that is why you are encountering such a problem. Well to solve the problem there are few ways - Need to edit the wsdl - Add the method to the service class and just call super.method. Thank you! Deepal On Fri, Jan 16, 2009 at 11:09 AM, Marco Rossi mros...@gmaile .com wrote: Sorry, i found the parentOperation, but with a wrong value return and input parameter. This is the mothod i want to expose: public String ParentMethod(String param){ return hallo; } But In the stub generated (JAX-WS) i found this one: public void ParentMethod() On Fri, Jan 16, 2009 at 4:09 PM, Marco Rossi mros...@gmail.com wrote: I try with the messageReceiver and with the MEP attribute, but it doesn't work. With the JAW-WS client i don't see the parent operation. I need to add something else in the configuration file? On Fri, Jan 16, 2009 at 3:46 PM, Deepal Jayasinghe dee...@opensource.lk wrote: Well you need one more thing, you need to add the MEP attribute into the operation or add the message receiver inside the operation. Like below; operation name=parentMethod messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation For more information read http://wso2.org/library/2060 Thank you! Deepal Thanks for your replay, Deepal ! I try with this configuration: service name=AddressBookService scope=application description POJO: AddressBook Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers parameter name=ServiceClasssample.addressbook.service.AddressBookService/parameter operation name=parentMethod / /service In the wsdl now i see the parentMethod method, but it doesn't generate the correct stub (using JAX-WS for the client). It's seem to ignore the parent method. On Fri, Jan 16, 2009 at 3:22 PM, Deepal Jayasinghe dee...@opensource.lk mailto:dee...@opensource.lk wrote: Actually what I meant to say there was you have inheritance support for beans not for the service class. When I developed the POJO I wanted to support service class inheritance as well, but due to some of the complexity I stop doing that. However implementing that is not hard, only thing you need to is to add the operations that you need to expose from the parent classes to services.xml, then everything would work fine. Thank you! Deepal In this article (http://www.developer.com/xml/article.php/10929_3726461_3) Deepal Jayasinghe introduces the axis2 framework. Axis2 POJO supports inheritance, so you can write your service class to extend some other class and publish parent(s) method(s) automatically. I try this example, but in the wsdl generated i don't see the methods of the parent class. What's wrong? -- Thank you! http://blogs.deepal.org http://deepal.org -- Thank you! http://blogs.deepal.org http://deepal.org
axis2 inheritance doesn't work?
In this article (http://www.developer.com/xml/article.php/10929_3726461_3) Deepal Jayasinghe introduces the axis2 framework. Axis2 POJO supports inheritance, so you can write your service class to extend some other class and publish parent(s) method(s) automatically. I try this example, but in the wsdl generated i don't see the methods of the parent class. What's wrong?
Re: axis2 inheritance doesn't work?
Thanks for your replay, Deepal ! I try with this configuration: service name=AddressBookService scope=application description POJO: AddressBook Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers parameter name=ServiceClasssample.addressbook.service.AddressBookService/parameter operation name=parentMethod / /service In the wsdl now i see the parentMethod method, but it doesn't generate the correct stub (using JAX-WS for the client). It's seem to ignore the parent method. On Fri, Jan 16, 2009 at 3:22 PM, Deepal Jayasinghe dee...@opensource.lkwrote: Actually what I meant to say there was you have inheritance support for beans not for the service class. When I developed the POJO I wanted to support service class inheritance as well, but due to some of the complexity I stop doing that. However implementing that is not hard, only thing you need to is to add the operations that you need to expose from the parent classes to services.xml, then everything would work fine. Thank you! Deepal In this article (http://www.developer.com/xml/article.php/10929_3726461_3) Deepal Jayasinghe introduces the axis2 framework. Axis2 POJO supports inheritance, so you can write your service class to extend some other class and publish parent(s) method(s) automatically. I try this example, but in the wsdl generated i don't see the methods of the parent class. What's wrong? -- Thank you! http://blogs.deepal.org http://deepal.org
Re: axis2 inheritance doesn't work?
I try with the messageReceiver and with the MEP attribute, but it doesn't work. With the JAW-WS client i don't see the parent operation. I need to add something else in the configuration file? On Fri, Jan 16, 2009 at 3:46 PM, Deepal Jayasinghe dee...@opensource.lkwrote: Well you need one more thing, you need to add the MEP attribute into the operation or add the message receiver inside the operation. Like below; operation name=parentMethod messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation For more information read http://wso2.org/library/2060 Thank you! Deepal Thanks for your replay, Deepal ! I try with this configuration: service name=AddressBookService scope=application description POJO: AddressBook Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers parameter name=ServiceClasssample.addressbook.service.AddressBookService/parameter operation name=parentMethod / /service In the wsdl now i see the parentMethod method, but it doesn't generate the correct stub (using JAX-WS for the client). It's seem to ignore the parent method. On Fri, Jan 16, 2009 at 3:22 PM, Deepal Jayasinghe dee...@opensource.lk mailto:dee...@opensource.lk wrote: Actually what I meant to say there was you have inheritance support for beans not for the service class. When I developed the POJO I wanted to support service class inheritance as well, but due to some of the complexity I stop doing that. However implementing that is not hard, only thing you need to is to add the operations that you need to expose from the parent classes to services.xml, then everything would work fine. Thank you! Deepal In this article (http://www.developer.com/xml/article.php/10929_3726461_3) Deepal Jayasinghe introduces the axis2 framework. Axis2 POJO supports inheritance, so you can write your service class to extend some other class and publish parent(s) method(s) automatically. I try this example, but in the wsdl generated i don't see the methods of the parent class. What's wrong? -- Thank you! http://blogs.deepal.org http://deepal.org -- Thank you! http://blogs.deepal.org http://deepal.org
Re: axis2 inheritance doesn't work?
Sorry, i found the parentOperation, but with a wrong value return and input parameter. This is the mothod i want to expose: public String ParentMethod(String param){ return hallo; } But In the stub generated (JAX-WS) i found this one: public void ParentMethod() On Fri, Jan 16, 2009 at 4:09 PM, Marco Rossi mros...@gmail.com wrote: I try with the messageReceiver and with the MEP attribute, but it doesn't work. With the JAW-WS client i don't see the parent operation. I need to add something else in the configuration file? On Fri, Jan 16, 2009 at 3:46 PM, Deepal Jayasinghe dee...@opensource.lkwrote: Well you need one more thing, you need to add the MEP attribute into the operation or add the message receiver inside the operation. Like below; operation name=parentMethod messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation For more information read http://wso2.org/library/2060 Thank you! Deepal Thanks for your replay, Deepal ! I try with this configuration: service name=AddressBookService scope=application description POJO: AddressBook Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers parameter name=ServiceClasssample.addressbook.service.AddressBookService/parameter operation name=parentMethod / /service In the wsdl now i see the parentMethod method, but it doesn't generate the correct stub (using JAX-WS for the client). It's seem to ignore the parent method. On Fri, Jan 16, 2009 at 3:22 PM, Deepal Jayasinghe dee...@opensource.lk mailto:dee...@opensource.lk wrote: Actually what I meant to say there was you have inheritance support for beans not for the service class. When I developed the POJO I wanted to support service class inheritance as well, but due to some of the complexity I stop doing that. However implementing that is not hard, only thing you need to is to add the operations that you need to expose from the parent classes to services.xml, then everything would work fine. Thank you! Deepal In this article (http://www.developer.com/xml/article.php/10929_3726461_3) Deepal Jayasinghe introduces the axis2 framework. Axis2 POJO supports inheritance, so you can write your service class to extend some other class and publish parent(s) method(s) automatically. I try this example, but in the wsdl generated i don't see the methods of the parent class. What's wrong? -- Thank you! http://blogs.deepal.org http://deepal.org -- Thank you! http://blogs.deepal.org http://deepal.org
Re: axis2 https Unexpected EOF in prolog
You're are right! With this options all works fine (with or without https). Thank you Murali. On Dec 13, 2007 8:47 PM, Murali Krishnan [EMAIL PROTECTED] wrote: Not very sure if this will help, but you can try this in your client code: Set this property as one of the options for the ServiceClient... options.setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE); Murali - Original Message From: Marco Rossi [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Thursday, December 13, 2007 12:36:58 PM Subject: axis2 https Unexpected EOF in prolog Hi, i have to test a webservices build with axis2 (tomcat6, linux red hat). We have a reverse proxy to expose this service to the client (via SSL); so if i create a test client with axis2 (same library, same version) and use the internal endpoint ( http://myserver/myService) all works fine. But il I try to test the same come with the reverse proxy endpoint https://myproxy/myService i get the following org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] Any idea? Thanks, Marco -- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ+
axis2 https Unexpected EOF in prolog
Hi, i have to test a webservices build with axis2 (tomcat6, linux red hat). We have a reverse proxy to expose this service to the client (via SSL); so if i create a test client with axis2 (same library, same version) and use the internal endpoint (http://myserver/myService) all works fine. But il I try to test the same come with the reverse proxy endpoint https://myproxy/myService i get the following org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] Any idea? Thanks, Marco
Axis2 Quick Start Example WSDL not valid
Hi, I try to create the wsdl from the example code present in the Quick Start Guide, the *StockQuoteService* ( http://ws.apache.org/axis2/1_3/quickstartguide.html), using the ant task: target name=generate.wsdl depends=compile.service taskdef name=java2wsdl classname=org.apache.ws.java2wsdl.Java2WSDLTask classpathref=axis2.classpath/ java2wsdl className= samples.quickstart.service.pojo.StockQuoteService outputLocation=${build.dir} targetNamespace=http://quickstart.samples/; schemaTargetNamespace=http://quickstart.samples/xsd; classpath pathelement path=${axis2.classpath}/ pathelement location=${build.dir}/classes/ /classpath /java2wsdl /target With the generated WSDL file (see attachment) i create a java client, and all works fine, but it's an invalid xml file - i tried with XMLSPY. In the block wsdl:input mime:content type=text/xml part=update/ /wsdl:input the parser show the follow error: attribute 'part' in extensibility element 'mime:content' refers to part 'update' wich could not be found in message 'updateRequest'. What's wrong, it's a bug? Marco ?xml version=1.0 encoding=UTF-8? wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:axis2=http://quickstart.samples/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:ns0=http://quickstart.samples/xsd; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:ns1=http://org.apache.axis2/xsd; xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; targetNamespace=http://quickstart.samples/; wsdl:types xs:schema xmlns:ns=http://quickstart.samples/xsd; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://quickstart.samples/xsd; xs:element name=getPrice xs:complexType xs:sequence xs:element minOccurs=0 name=symbol nillable=true type=xs:string/ /xs:sequence /xs:complexType /xs:element xs:element name=getPriceResponse xs:complexType xs:sequence xs:element minOccurs=0 name=return type=xs:double/ /xs:sequence /xs:complexType /xs:element xs:element name=update xs:complexType xs:sequence xs:element minOccurs=0 name=symbol nillable=true type=xs:string/ xs:element minOccurs=0 name=price type=xs:double/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=updateRequest wsdl:part name=parameters element=ns0:update/ /wsdl:message wsdl:message name=getPriceRequest wsdl:part name=parameters element=ns0:getPrice/ /wsdl:message wsdl:message name=getPriceResponse wsdl:part name=parameters element=ns0:getPriceResponse/ /wsdl:message wsdl:portType name=StockQuoteServicePortType wsdl:operation name=update wsdl:input message=axis2:updateRequest wsaw:Action=urn:update/ /wsdl:operation wsdl:operation name=getPrice wsdl:input message=axis2:getPriceRequest wsaw:Action=urn:getPrice/ wsdl:output message=axis2:getPriceResponse wsaw:Action=urn:getPriceResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=StockQuoteServiceSOAP11Binding type=axis2:StockQuoteServicePortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=update soap:operation soapAction=urn:update style=document/ wsdl:input soap:body use=literal/ /wsdl:input /wsdl:operation wsdl:operation name=getPrice soap:operation soapAction=urn:getPrice style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=StockQuoteServiceSOAP12Binding type=axis2:StockQuoteServicePortType soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=update soap12:operation soapAction=urn:update style=document/ wsdl:input soap12:body use=literal/ /wsdl:input /wsdl:operation wsdl:operation name=getPrice soap12:operation soapAction=urn:getPrice style=document/ wsdl:input