RE: Upgrade axis2 from 1.4.1 to 1.5.1
Hi Deepal, I think I found my problem. When I originally upgraded from axis1 to Axis2 I was trying to get custom exception work(since I had custom exception working in axis1) so I inherited my custom exception from org.apache.axis2.AxisFault while I was trying things. Since I couldn't get custom exception working the way I wanted I moved on but forgot to remove the inheritence of org.apache.axis2.AxisFault. After removing the org.apache.axis2.AxisFault from my exception wsdl started generating fine. I can successfully consume wsdl and make calls now. Thanks for you help. The question is why would inheriting my exception from org.apache.axis2.AxisFault would cause this issue. Thanks, Sanjay -Original Message- From: Deepal jayasinghe [mailto:deep...@gmail.com] Sent: Thursday, January 07, 2010 7:25 AM To: axis-user@ws.apache.org Subject: Re: Upgrade axis2 from 1.4.1 to 1.5.1 Hi Sanjay, I can see something has gone wrong with the WSDL generation, so could you please send me your service class or sample service so that I can regenerate the issue. Thanks, Deepal Hi Deepal, Thanks for your reply. I am attaching my wsdl. I have removed all operations except one using excludeOperations in services.xml to keep it simple. If you try to load it using SOAPUI you will get the error. wsdl2java also gives error. Thanks, Sanjay -Original Message- From: Deepal Jayasinghe [mailto:dee...@opensource.lk] Sent: Tuesday, January 05, 2010 10:22 AM To: axis-user@ws.apache.org Subject: Re: Upgrade axis2 from 1.4.1 to 1.5.1 This is a big issues, I think someone has broken Axis2 wsdl generation. Could you send us the wsdl I would like to have a look. In addition I would like to see which POJO approach you use, if you can try to give me a sample service to regenerate the issue. Thanks, Deepal Sanjay Gupta wrote: Hi, I recently upgraded our app from 1.4.1 to 1.5.1 and having some issue in wsdl. I use the POJO deployment option. I am having trouble running wsdl2java on the wsdl. I can see duplicate entry for complex type axisConfirguation in the auto generated wsdl. When I run wsdl2java from 1.4.1 version of axis2 I get the error(see below). I have tried soapui and gettings errors when I try o create a project from the wsdl. Axis2 is deployed inside tomcat 6.0.18. Any help will be greatly appreciated. Thanks, Sanjay wsdl2java -uri https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl -o . -uw -or Using AXIS2_HOME: C:\axis2-1.4.1 Using JAVA_HOME:C:\Progra~1\Java\jdk1.6.0_13 Retrieving document at 'https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl'. [ERROR] Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' org.apache.ws.commons.schema.XmlSchemaException: Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' at org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:511) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:168) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412) at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:144) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:2320) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:414) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:403) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:347) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) -- Thank you! http://blogs.deepal.org http://deepal.org
Upgrade axis2 from 1.4.1 to 1.5.1
Hi, I recently upgraded our app from 1.4.1 to 1.5.1 and having some issue in wsdl. I use the POJO deployment option. I am having trouble running wsdl2java on the wsdl. I can see duplicate entry for complex type axisConfirguation in the auto generated wsdl. When I run wsdl2java from 1.4.1 version of axis2 I get the error(see below). I have tried soapui and gettings errors when I try o create a project from the wsdl. Axis2 is deployed inside tomcat 6.0.18. Any help will be greatly appreciated. Thanks, Sanjay wsdl2java -uri https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl -o . -uw -or Using AXIS2_HOME: C:\axis2-1.4.1 Using JAVA_HOME:C:\Progra~1\Java\jdk1.6.0_13 Retrieving document at 'https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl'. [ERROR] Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' org.apache.ws.commons.schema.XmlSchemaException: Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' at org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:511) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:168) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412) at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:144) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:2320) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:414) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:403) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:347) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
RE: Upgrade to axis2 1.4.1 to 1.5.1
Hi, I went back to 1.4.1 and really would like to upgrade to 1.5.1 to fix some other issues. Does anybody have any idea on why I am getting this error? I have seen references to this error but nothing really useful. Any help would be greatly appreciated. Thanks Sanjay -Original Message- From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Wednesday, November 18, 2009 1:01 PM To: axis-user@ws.apache.org Subject: RE: Upgrade to axis2 1.4.1 to 1.5.1 Hi, Anybody has any idea on what's causing my problem. I am ready to rollback to axis2 1.4.1 but thought of checking again to see if any faced a similar issue and found a reason/resolution. Thanks Sanjay -Original Message- From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, November 17, 2009 7:16 PM To: axis-user@ws.apache.org Subject: Upgrade to axis2 1.4.1 to 1.5.1 Hi, I recently upgraded our app from 1.4.1 to 1.5.1 and having some issue in wsdl. I use the POJO deployment option. I am having trouble running wsdl2java on the wsdl. I can see duplicate entry for complex type axisConfirguation in the auto generated wsdl. When I run wsdl2java from 1.4.1 version of axis2 I get the error(see below). I have tried soapui and gettings errors when I try o create a project from the wsdl. Axis2 is deployed inside tomcat 6.0.18. Any help will be greatly appreciated. Thanks Sanjay wsdl2java -uri https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl -o . -uw -or Using AXIS2_HOME: C:\axis2-1.4.1 Using JAVA_HOME:C:\Progra~1\Java\jdk1.6.0_13 Retrieving document at 'https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl'. [ERROR] Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' org.apache.ws.commons.schema.XmlSchemaException: Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' at org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:511) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:168) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412) at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:144) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:2320) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:414) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:403) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:347) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
RE: Customizing end point location
No I didn't find any solution. I did see the JIRA as well. It was broken in 1.4.1 as well. Sanjay From: Manuel Darveau [mailto:manueldarv...@gmail.com] Sent: Friday, November 20, 2009 9:01 AM To: axis-user@ws.apache.org Subject: Re: Customizing end point location Did you found a solution? I am not able to deploy a webservice over an ssl/https connection for this reason. A message on this list from Andread Veithen (Nov 5) seems to indicate that this is broken in 1.5 but will be fixed in 1.6. He refers to AXIS2-4465. Manuel On Wed, Sep 23, 2009 at 11:49 PM, Sanjay Gupta sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote: Hi, Deos any have any suggesion on how I can accomplish this. I would appreciate any help. Thanks Sanjay -Original Message- From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com] Sent: Monday, September 21, 2009 3:40 PM To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org Subject: Customizing end point location Hi, I have pojo based servcies deployed in axis2 inside tomcat. The endpoint url inside autogenerated wsdl has http in soap12:address location even though I am using ssl on port 8443. Is there a way to change the http to https. I am able to get proper port in the url by using hostname parameter in transportReceiver tag but not https. The service itself is working fine using https on port 8443. Sanjay
RE: Upgrade to axis2 1.4.1 to 1.5.1
Hi, Anybody has any idea on what's causing my problem. I am ready to rollback to axis2 1.4.1 but thought of checking again to see if any faced a similar issue and found a reason/resolution. Thanks Sanjay -Original Message- From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, November 17, 2009 7:16 PM To: axis-user@ws.apache.org Subject: Upgrade to axis2 1.4.1 to 1.5.1 Hi, I recently upgraded our app from 1.4.1 to 1.5.1 and having some issue in wsdl. I use the POJO deployment option. I am having trouble running wsdl2java on the wsdl. I can see duplicate entry for complex type axisConfirguation in the auto generated wsdl. When I run wsdl2java from 1.4.1 version of axis2 I get the error(see below). I have tried soapui and gettings errors when I try o create a project from the wsdl. Axis2 is deployed inside tomcat 6.0.18. Any help will be greatly appreciated. Thanks Sanjay wsdl2java -uri https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl -o . -uw -or Using AXIS2_HOME: C:\axis2-1.4.1 Using JAVA_HOME:C:\Progra~1\Java\jdk1.6.0_13 Retrieving document at 'https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl'. [ERROR] Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' org.apache.ws.commons.schema.XmlSchemaException: Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' at org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:511) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:168) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412) at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:144) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:2320) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:414) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:403) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:347) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Upgrade to axis2 1.4.1 to 1.5.1
Hi, I recently upgraded our app from 1.4.1 to 1.5.1 and having some issue in wsdl. I use the POJO deployment option. I am having trouble running wsdl2java on the wsdl. I can see duplicate entry for complex type axisConfirguation in the auto generated wsdl. When I run wsdl2java from 1.4.1 version of axis2 I get the error(see below). I have tried soapui and gettings errors when I try o create a project from the wsdl. Axis2 is deployed inside tomcat 6.0.18. Any help will be greatly appreciated. Thanks Sanjay wsdl2java -uri https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl -o . -uw -or Using AXIS2_HOME: C:\axis2-1.4.1 Using JAVA_HOME:C:\Progra~1\Java\jdk1.6.0_13 Retrieving document at 'https://cwa024.connect4billing.com/axis2/services/ConnectSmService?wsdl'. [ERROR] Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' org.apache.ws.commons.schema.XmlSchemaException: Schema for namespace 'http://engine.axis2.apache.org/xsd' already contains type 'AxisConfiguration' at org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:511) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:168) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412) at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:144) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:2320) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:414) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11ToAxisServiceBuilder.java:403) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:347) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
RE: Generated WSDL HTTPS Port not 8443
Hi, I have the same issue and very interested in finding a solution. Sanjay -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Monday, November 09, 2009 1:40 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: On Thu, Nov 5, 2009 at 20:49, v2cg4ss ssel...@datamentors.com wrote: Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, https://localhost:8443/axis2/services/MyWS;); Scott Andreas Veithen-2 wrote: Generating the correct endpoint URIs for https is something that doesn't work properly in the available Axis2 releases. See AXIS2-4465 and related issues. Andreas -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Customizing end point location
Hi, Deos any have any suggesion on how I can accomplish this. I would appreciate any help. Thanks Sanjay -Original Message- From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Monday, September 21, 2009 3:40 PM To: axis-user@ws.apache.org Subject: Customizing end point location Hi, I have pojo based servcies deployed in axis2 inside tomcat. The endpoint url inside autogenerated wsdl has http in soap12:address location even though I am using ssl on port 8443. Is there a way to change the http to https. I am able to get proper port in the url by using hostname parameter in transportReceiver tag but not https. The service itself is working fine using https on port 8443. Sanjay
RE: SOAP Encoding in axis2
Hi, Is there any workaround? The problem I have is that I need to consume these services in a grails app that is already using axis2 to expose part of it as services and also consuming axis2 services. I don't think axis1 can co-exist with axis2 in the same app. Sanjay -Original Message- From: Mauro Molinari [mailto:mauro.molin...@cardinis.com] Sent: Monday, September 21, 2009 6:58 AM To: axis-user@ws.apache.org Subject: Re: SOAP Encoding in axis2 Sanjay Gupta ha scritto: Hi, I tried consuming a web service with SOAP encoding in axis2 and found out that axis2 doesn't support it. Are there any workaround? We originally used. Part of that app we have upgraded to axis2 and we are using axis2 for all the new stuff. I really don't want to go back to axis1. Sanjay No, SOAP encoding is not supported by Axis2 as of now. -- Mauro Molinari Software Designer Developer E-mail: mauro.molin...@cardinis.com
Customizing end point location
Hi, I have pojo based servcies deployed in axis2 inside tomcat. The endpoint url inside autogenerated wsdl has http in soap12:address location even though I am using ssl on port 8443. Is there a way to change the http to https. I am able to get proper port in the url by using hostname parameter in transportReceiver tag but not https. The service itself is working fine using https on port 8443. Sanjay
SOAP Encoding in axis2
Hi, I tried consuming a web service with SOAP encoding in axis2 and found out that axis2 doesn't support it. Are there any workaround? We originally used. Part of that app we have upgraded to axis2 and we are using axis2 for all the new stuff. I really don't want to go back to axis1. Sanjay
RE: MTOM support causing problem
Hi Chinmoy, The problem happens in methods that have nothing to do with mtom. They are simple service methods that return an objects array. I did putting debugging messages to make sure that service method worked fine. Thanks Sanjay From: Chinmoy Chakraborty [mailto:cch...@gmail.com] Sent: Wednesday, September 02, 2009 10:45 PM To: axis-user@ws.apache.org Subject: Re: MTOM support causing problem Are you sure that your service method is working fine? are you sending attachemnt or receiving attachment or both? On Thu, Sep 3, 2009 at 11:01 AM, Sanjay Gupta sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote: Hi, I enabled mtom support in axis2.xml and it's causing some problem in an already working application. I am using axis2 1.4.1, tomcat 6.0.18 and jdk 1.6.0.14. I have my axis2 pojo based services deployed in tomcat as an app. In the same tomcat I have a grails app that has some grails services exposed as web services using grails axis2 plugin. From my axis2 app I calls grails/axis2 services(using wsdl2java generated stub) internally and it worked fine without any issues till I enabled mtom support. Now it intermittently gives me the following error. I have tracked down the problem in the axis2 layer. Don't know if it is grails/axis2 plugin or axis2 app. I see that everything is fine just before the return in grails service. I would really appreciate any help on this. Thanks Sanjay 2009-09-02 22:25:21,451 [http-8443-31] INFO org.apache.axis2.builder.BuilderUtil - OMException in getSOAPBuilder org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:251) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677) at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at com.bwse.wsclient.service.ConnectSmStub.findTransactions(ConnectSmStub.java:1437) at com.bwse.ws.ConnectSmService.findTransactions(ConnectSmService.java:1216) at sun.reflect.GeneratedMethodAccessor2230.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke
RE: [Axis2-1.4.1 Versus 1.5]
I also see this error in one the the tomcat log file. Sep 2, 2009 11:34:53 PM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet axis2 threw exception java.lang.NullPointerException at org.apache.catalina.connector.Request.parseParameters(Request.java:2446) at org.apache.catalina.connector.Request.getParameterNames(Request.java:1082) at org.apache.catalina.connector.RequestFacade.getParameterNames(RequestFacade.java:371) at javax.servlet.ServletRequestWrapper.getParameterNames(ServletRequestWrapper.java:178) at org.springframework.web.multipart.support.DefaultMultipartHttpServletRequest.getParameterNames(DefaultMultipartHttpServletRequest.java:69) at org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.tryMultipartParams(DefaultUrlMappingInfo.java:236) at org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.checkDispatchAction(DefaultUrlMappingInfo.java:210) at org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.getActionName(DefaultUrlMappingInfo.java:168) at org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.populateParamsForMapping(DefaultUrlMappingInfo.java:138) at org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.configure(DefaultUrlMappingInfo.java:155) at org.codehaus.groovy.grails.web.mapping.filter.UrlMappingsFilter.doFilterInternal(UrlMappingsFilter.java:112) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.codehaus.groovy.grails.web.sitemesh.GrailsPageFilter.parsePage(GrailsPageFilter.java:122) at org.codehaus.groovy.grails.web.sitemesh.GrailsPageFilter.doFilter(GrailsPageFilter.java:85) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378) at org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) at org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) at org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) at org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) at org.springframework.security.ui.rememberme.RememberMeProcessingFilter.doFilterHttp(RememberMeProcessingFilter.java:109) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) at org.springframework.security.wrapper.SecurityContextHolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareRequestFilter.java:91) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) at org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:277) at org.codehaus.groovy.grails.plugins.springsecurity.GrailsAuthenticationProcessingFilter.super$3$doFilterHttp(GrailsAuthenticationProcessingFilter.groovy) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
RE: MTOM support causing problem
My problem was fixed after I changed enableMTOM to optional from true in axis2.xml. From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Wednesday, September 02, 2009 11:36 PM To: axis-user@ws.apache.org Subject: RE: MTOM support causing problem Hi Chinmoy, The problem happens in methods that have nothing to do with mtom. They are simple service methods that return an objects array. I did putting debugging messages to make sure that service method worked fine. Thanks Sanjay From: Chinmoy Chakraborty [mailto:cch...@gmail.com] Sent: Wednesday, September 02, 2009 10:45 PM To: axis-user@ws.apache.org Subject: Re: MTOM support causing problem Are you sure that your service method is working fine? are you sending attachemnt or receiving attachment or both? On Thu, Sep 3, 2009 at 11:01 AM, Sanjay Gupta sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote: Hi, I enabled mtom support in axis2.xml and it's causing some problem in an already working application. I am using axis2 1.4.1, tomcat 6.0.18 and jdk 1.6.0.14. I have my axis2 pojo based services deployed in tomcat as an app. In the same tomcat I have a grails app that has some grails services exposed as web services using grails axis2 plugin. From my axis2 app I calls grails/axis2 services(using wsdl2java generated stub) internally and it worked fine without any issues till I enabled mtom support. Now it intermittently gives me the following error. I have tracked down the problem in the axis2 layer. Don't know if it is grails/axis2 plugin or axis2 app. I see that everything is fine just before the return in grails service. I would really appreciate any help on this. Thanks Sanjay 2009-09-02 22:25:21,451 [http-8443-31] INFO org.apache.axis2.builder.BuilderUtil - OMException in getSOAPBuilder org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:251) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677) at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at com.bwse.wsclient.service.ConnectSmStub.findTransactions(ConnectSmStub.java:1437) at com.bwse.ws.ConnectSmService.findTransactions(ConnectSmService.java:1216) at sun.reflect.GeneratedMethodAccessor2230.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290
MTOM support causing problem
Hi, I enabled mtom support in axis2.xml and it's causing some problem in an already working application. I am using axis2 1.4.1, tomcat 6.0.18 and jdk 1.6.0.14. I have my axis2 pojo based services deployed in tomcat as an app. In the same tomcat I have a grails app that has some grails services exposed as web services using grails axis2 plugin. From my axis2 app I calls grails/axis2 services(using wsdl2java generated stub) internally and it worked fine without any issues till I enabled mtom support. Now it intermittently gives me the following error. I have tracked down the problem in the axis2 layer. Don't know if it is grails/axis2 plugin or axis2 app. I see that everything is fine just before the return in grails service. I would really appreciate any help on this. Thanks Sanjay 2009-09-02 22:25:21,451 [http-8443-31] INFO org.apache.axis2.builder.BuilderUtil - OMException in getSOAPBuilder org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:251) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677) at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at com.bwse.wsclient.service.ConnectSmStub.findTransactions(ConnectSmStub.java:1437) at com.bwse.ws.ConnectSmService.findTransactions(ConnectSmService.java:1216) at sun.reflect.GeneratedMethodAccessor2230.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
Consuming axis2 web services using axis1 client
Hi, Is it possible to consume an axis2 web services using axis1 client? I have a legacy application than currently uses axis1 client to consume some axis1 web services. I am building my new services in axis2 and would like to consule some of them in the legacy app using axis1 client. Thanks Sanjay
RE: Use Axis1 and Axis2 inside the same JBoss/Tomcat
I did exactly the same and have no issues. Some of my services had no return in axis1 and I couldn't make it work in axis2 so I changed them to resturn status. From: Nora Serinek [mailto:nseri...@berlin-sws.de] Sent: Wednesday, July 08, 2009 10:28 AM To: axis-user@ws.apache.org Subject: Use Axis1 and Axis2 inside the same JBoss/Tomcat Hi, We'd like to migrate from Axis 1.4 to Axis2. We'd like to migrate not all our web services at once so I wonder if it is possible to use Axis1 and Axis2 simultaneously within the same JVM. Thank you for your help Nora ### This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the system manager.
RE: MTOM - Size Limit
Hi I had a similar issue and mine was cutting off around 12k. Martin gainty had some solution but I haven't had a chance to implement it yet. Search for archive for my name. If you find any solution please let me know as well. -Original Message- From: paulpablo [mailto:pdwinn...@sciquest.com] Sent: Friday, July 10, 2009 6:02 AM To: axis-user@ws.apache.org Subject: MTOM - Size Limit I'm using MTOM to pass larger binaries. I had this working in a dev environment but when I rolled this out our test environment the size of the returned MTOM binary get cut off at 6144 bytes (6K). If it's smaller that, it works fine. Does anyone have any idea what would cause this? -- View this message in context: http://www.nabble.com/MTOM---Size-Limit-tp24427157p24427157.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis1.x in Java6
We tried it and didn't have any issues. From: Gary Yue [mailto:yueg...@yahoo.com] Sent: Thursday, June 11, 2009 4:23 PM To: axis-user@ws.apache.org Subject: Axis1.x in Java6 Hi, does anybody know if Axis1.x is compatible w/ java6? We are trying to upgrade our server (Axis1.x based) to java6 runtime. Wonder if anyone has tried this before and whether that are any known issues. thanks gary
RE: Problem with MTOM
Hi Massimiliano,
You mentioned about a workaround. Would you mind sharing that in case I can use
that.
Thanks
Sanjay
From: Massimiliano Ziccardi [mailto:massimiliano.zicca...@gmail.com]
Sent: Thursday, May 21, 2009 11:24 PM
To: axis-user@ws.apache.org
Subject: Re: Problem with MTOM
Hi.
Thank you for your help.
At the moment I'm very hurry with my project, so I'll use my workaround for
some time.
As soon as I'll be a little bit less hurry, I'll surely try to switch to a
better solution.
Thank you,
Massimiliano
On Fri, May 22, 2009 at 6:33 AM, Sanjay Gupta
sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote:
I tried the 1.2.9 snapshot on both server and client but still have issues.
This particular service i implemented is inside grails and exposed using axis2
plugin. I need to figure out how to enable soapmonitor in grails/axis2.
Massimiliano, I did generate my clients from my autogenerated wsdl. I have not
tried the solution provided by martin but I would do so soon. If you want you
can try the solution provided by martin. Just compare the source the that I
provided to him and his version to see the changes that he made and make those
changes in yours.
-Original Message-
From: Andreas Veithen
[mailto:andreas.veit...@gmail.commailto:andreas.veit...@gmail.com]
Sent: Thursday, May 21, 2009 10:33 AM
To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org
Subject: Re: Problem with MTOM
In 1.2.9-SNAPSHOT, the class
org.apache.axiom.om.impl.llom.OMStAXWrapper (part of axiom-impl.jar)
extends org.apache.axiom.om.impl.OMStAXWrapper (part of
axiom-api.jar). If you get this error, this would mean that you didn't
replace axiom-api.jar. Can you check that?
Andreas
On Thu, May 21, 2009 at 11:31, Massimiliano Ziccardi
massimiliano.zicca...@gmail.commailto:massimiliano.zicca...@gmail.com wrote:
TO Andreas: I tried with the latest snapshot, but even after replacing both
axis and axiom, I always get:
The type org.apache.axiom.om.impl.OMStAXWrapper cannot be resolved. It is
indirectly referenced from required .class filesWStestImplStub.java
TEST_CLIENT/src/it/test/ws/impl
I've searched through the jars, and I found OMStAXWrapper inside another
package...
Did I make something wrong?
TO Sanjay: I read the topic you talk about. I've autogenerated the client
starting from the wsdl: should I rewrite the stub using the logic described
there?
At the moment, I simply call the getFile(GetFile).get_return methods of my
stub to get the DataHandler
Thanks,
Massimiliano
On Wed, May 20, 2009 at 6:26 PM, Sanjay Gupta
sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com
wrote:
I had the exact same issue few weeks back and martin gainty helped me. I
haven't tried his solution yet. I have been so busy with other things. See
the thread Sending binary data(not using MTOM) using DataHandler.
Thanks
Sanjay
-Original Message-
From: Andreas Veithen
[mailto:andreas.veit...@gmail.commailto:andreas.veit...@gmail.com]
Sent: Wednesday, May 20, 2009 8:46 AM
To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org
Subject: Re: Problem with MTOM
Massimiliano,
Can you check whether replacing the Axiom JARs with version
1.2.9-SNAPSHOT fixes this issue? You can download them from [1]. If
that doesn't help, can you try to use tcpmon or Wireshark to determine
whether the content is truncated on the server or client side?
Andreas
[1]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/
On Wed, May 20, 2009 at 17:25, Massimiliano Ziccardi
massimiliano.zicca...@gmail.commailto:massimiliano.zicca...@gmail.com
wrote:
Which version of Axis2
I'm using AXIS2 1.4.1.
and Axiom do you use?
All the jars I use are from the AXIS2 1.4.1 package.
Is the client also Axis2 based?
Both client and server are AXIS2 1.4.1
Thank you very much for you prompt help!
Massimiliano
On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen
andreas.veit...@gmail.commailto:andreas.veit...@gmail.com
wrote:
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.commailto:massimiliano.zicca...@gmail.com
wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new
File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated
at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
RE: Problem with MTOM
I tried the 1.2.9 snapshot on both server and client but still have issues.
This particular service i implemented is inside grails and exposed using axis2
plugin. I need to figure out how to enable soapmonitor in grails/axis2.
Massimiliano, I did generate my clients from my autogenerated wsdl. I have not
tried the solution provided by martin but I would do so soon. If you want you
can try the solution provided by martin. Just compare the source the that I
provided to him and his version to see the changes that he made and make those
changes in yours.
-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
Sent: Thursday, May 21, 2009 10:33 AM
To: axis-user@ws.apache.org
Subject: Re: Problem with MTOM
In 1.2.9-SNAPSHOT, the class
org.apache.axiom.om.impl.llom.OMStAXWrapper (part of axiom-impl.jar)
extends org.apache.axiom.om.impl.OMStAXWrapper (part of
axiom-api.jar). If you get this error, this would mean that you didn't
replace axiom-api.jar. Can you check that?
Andreas
On Thu, May 21, 2009 at 11:31, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
TO Andreas: I tried with the latest snapshot, but even after replacing both
axis and axiom, I always get:
The type org.apache.axiom.om.impl.OMStAXWrapper cannot be resolved. It is
indirectly referenced from required .class files WStestImplStub.java
TEST_CLIENT/src/it/test/ws/impl
I've searched through the jars, and I found OMStAXWrapper inside another
package...
Did I make something wrong?
TO Sanjay: I read the topic you talk about. I've autogenerated the client
starting from the wsdl: should I rewrite the stub using the logic described
there?
At the moment, I simply call the getFile(GetFile).get_return methods of my
stub to get the DataHandler
Thanks,
Massimiliano
On Wed, May 20, 2009 at 6:26 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com
wrote:
I had the exact same issue few weeks back and martin gainty helped me. I
haven't tried his solution yet. I have been so busy with other things. See
the thread Sending binary data(not using MTOM) using DataHandler.
Thanks
Sanjay
-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
Sent: Wednesday, May 20, 2009 8:46 AM
To: axis-user@ws.apache.org
Subject: Re: Problem with MTOM
Massimiliano,
Can you check whether replacing the Axiom JARs with version
1.2.9-SNAPSHOT fixes this issue? You can download them from [1]. If
that doesn't help, can you try to use tcpmon or Wireshark to determine
whether the content is truncated on the server or client side?
Andreas
[1]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/
On Wed, May 20, 2009 at 17:25, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Which version of Axis2
I'm using AXIS2 1.4.1.
and Axiom do you use?
All the jars I use are from the AXIS2 1.4.1 package.
Is the client also Axis2 based?
Both client and server are AXIS2 1.4.1
Thank you very much for you prompt help!
Massimiliano
On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen
andreas.veit...@gmail.com
wrote:
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new
File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated
at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
RE: Problem with MTOM
I had the exact same issue few weeks back and martin gainty helped me. I
haven't tried his solution yet. I have been so busy with other things. See the
thread Sending binary data(not using MTOM) using DataHandler.
Thanks
Sanjay
-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
Sent: Wednesday, May 20, 2009 8:46 AM
To: axis-user@ws.apache.org
Subject: Re: Problem with MTOM
Massimiliano,
Can you check whether replacing the Axiom JARs with version
1.2.9-SNAPSHOT fixes this issue? You can download them from [1]. If
that doesn't help, can you try to use tcpmon or Wireshark to determine
whether the content is truncated on the server or client side?
Andreas
[1]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/
On Wed, May 20, 2009 at 17:25, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Which version of Axis2
I'm using AXIS2 1.4.1.
and Axiom do you use?
All the jars I use are from the AXIS2 1.4.1 package.
Is the client also Axis2 based?
Both client and server are AXIS2 1.4.1
Thank you very much for you prompt help!
Massimiliano
On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new
File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
RE: Access to message context in Password Callback Handler
Hi Guys, Are there any solution to my problem. This seems like a failry common requirement. I would really appreciate any help or suggestion. Thanks Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Friday, May 08, 2009 7:50 AM To: axis-user@ws.apache.org Subject: RE: Access to message context in Password Callback Handler Hi, Can anybody give me some pointers on this issue. Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, April 21, 2009 8:55 AM To: axis-user@ws.apache.org Subject: Access to message context in Password Callback Handler Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay
RE: Access to message context in Password Callback Handler
Hi Sagara, Thanks for your reply and suggestion. Your suggestion would definitely work. I have used this approach in other applications. I am going to try it. Sanjay -Original Message- From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: Wednesday, May 20, 2009 10:19 AM To: axis-user@ws.apache.org Subject: Re: Access to message context in Password Callback Handler Hi Sanjay, I have seen lot of post about this requirement, sometimes ago i also faced the same issue. AFAIK still there is no proper solution for this. cant you use following approach for your requirement..? 1. In callback handler save user profile into a database table after successful authentication . ( or persist using any other approach.) 2. In the service method retrieve above user profile from database to access required details. ( I know this is little ugly :) but possible solution) Thanks , On Wed, May 20, 2009 at 9:50 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Guys, Are there any solution to my problem. This seems like a failry common requirement. I would really appreciate any help or suggestion. Thanks Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Friday, May 08, 2009 7:50 AM To: axis-user@ws.apache.org Subject: RE: Access to message context in Password Callback Handler Hi, Can anybody give me some pointers on this issue. Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, April 21, 2009 8:55 AM To: axis-user@ws.apache.org Subject: Access to message context in Password Callback Handler Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/
RE: Access to message context in Password Callback Handler
Hi, Can anybody give me some pointers on this issue. Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, April 21, 2009 8:55 AM To: axis-user@ws.apache.org Subject: Access to message context in Password Callback Handler Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay
RE: https client - defining the keystore path
Hi Nuno, If the server has a CA issued cert then you don't need anything. In case of self signed cert I add the following two line and it works for me. I usually don't import my self-signed cert to the java cacerts. System.setProperty(javax.net.ssl.trustStore, C:/cts/axis2/client/resources/server.jks); System.setProperty(javax.net.ssl.trustStorePassword, **); Hope this helps. Thanks Sanjay -Original Message- From: Nuno Feliciano [mailto:nuno.felici...@novabase.pt] Sent: Thursday, May 07, 2009 10:08 AM To: axis-user@ws.apache.org Subject: https client - defining the keystore path Hi, I'm trying to use an axis client to consume an https webservice. I set the following properties System.setProperty(axis.socketSecureFactory, org.apache.axis.components.net.SunJSSESocketFactory); System.setProperty(javax.net.ssl.keyStore, C:\\Program Files\\Java\\jdk1.5.0_14\\.keystore); System.setProperty(javax.net.ssl.passwordStore, ); System.setProperty(javax.net.ssl.trustStore, C:\\Program Files\\Java\\jdk1.5.0_14\\jre\\lib\\security\\cacerts); But axis complains because it can't find the keystore file in my user.home java.io.FileNotFoundException: D:\Documents and Settings\user\.keystore (The system cannot find the file specified) I thought the purpose of setting the javax.net.ssl.keyStore property was to tell axis not to look in the default place for the keystore, so why is it looking in my user.home folder, and how can I change that?
Paypal API using axis2
Hi, I am trying to use axis2 to consule paypal services. I am using the following wsdl and invoking DoDirectPayment operation. I had to make one code change to the generated class that parses the response to make it work for +ve tes case. But in case of an error e.g. authentication error it's not working. I just get an Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement DoDirectPaymentResponse error. I was wondering if anybody tried consuming paypal services successfully and can share their experience and give me some pointers. https://www.sandbox.paypal.com/wsdl/PayPalSvc.wsdl Thanks Sanjay
Error handing in axis2
Hi, I am using axis2 to expose POJO as services. In case of an error I throw an custom exception. The pojo methods returns a string. When I was using axis1.2.1 the return was set to void. I had to change that to String to avoid inonly error I kept getting. I could not find a solution to that problem so I decided to return string when I upgrdaded to axis2. In case of an exception on the client side now I am getting org.apache.axis2.AxisFault with SOAP heading missing as message instead of my custom exception which has some custom variables. I am using rampart to do basic auth using username token. Am I doing something wrong or approaching it incorrectly. I would really appreciate any help/pointers. Thanks Sanjay
RE: Securing Axis2 REST Style Services
Hi Ruchith, I am using verison 1.4.1. xmlsec-1.4.1.jar Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Wednesday, April 22, 2009 7:24 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Hi Sanjay, Which version of Apache xmlsec are you using? Thanks, Ruchith On Mon, Apr 20, 2009 at 7:41 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Ruchith, Finally I got authentication working on rest call. I had to comment the db calls in the class that you provided to get past the db connection issue. Thank you so much for helping me out. Even though the authentication is working I get an error. See the stacktrace below. I see a jira for the same issue. Are there any side effect of this error? Thanks Sanjay http://wso2.org/mailarchive/ds-java-dev/2008-August/001970.html [FATAL] Bad: java.lang.NullPointerException at org.apache.xml.security.algorithms.JCEMapper.loadAlgorithms(Unknown Source) at org.apache.xml.security.algorithms.JCEMapper.init(Unknown Source) at org.apache.xml.security.Init.init(Unknown Source) at org.apache.ws.security.WSSConfig.staticInit(WSSConfig.java:233) at org.apache.ws.security.WSSConfig.init(WSSConfig.java:256) at org.apache.ws.security.WSSConfig.getNewInstance(WSSConfig.java:265) at org.apache.ws.security.WSSConfig.getDefaultWSConfig(WSSConfig.java:275) at org.apache.ws.security.message.WSSecBase.init(WSSecBase.java:52) at org.apache.ws.security.message.WSSecUsernameToken.init(WSSecUsernameToken.java:62) at org.wso2.wsas.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:183) at org.apache.axis2.engine.Phase.invoke(Phase.java:317) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130) at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:829) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:255) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) java.lang.NullPointerException at org.apache.xml.security.algorithms.JCEMapper.loadAlgorithms(Unknown Source) at org.apache.xml.security.algorithms.JCEMapper.init(Unknown Source) at org.apache.xml.security.Init.init(Unknown Source) at org.apache.ws.security.WSSConfig.staticInit(WSSConfig.java:233) at org.apache.ws.security.WSSConfig.init(WSSConfig.java:256) at org.apache.ws.security.WSSConfig.getNewInstance(WSSConfig.java:265) at org.apache.ws.security.WSSConfig.getDefaultWSConfig(WSSConfig.java:275) at org.apache.ws.security.message.WSSecBase.init(WSSecBase.java:52) at org.apache.ws.security.message.WSSecUsernameToken.init(WSSecUsernameToken.java:62) at org.wso2.wsas.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:183) at org.apache.axis2.engine.Phase.invoke(Phase.java:317) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130) at org.apache.axis2.transport.http.AxisServlet
Access to message context in Password Callback Handler
Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay
Sending binary data(not using MTOM) using DataHandler
Hi, I have written a service that returns DataHandler containing the binary data(pdf file). When I call that service by using the classes generated by wsdl2java I only get 12k of the binary data. I have seen as reference to 12K buffer wrap issue. I would appreciate if anybody can give me some pointers on how to resole this issue. BTW the service is written in grails and exposed using AXIS2 plugin and all other services(the one not dealing with binary data) work without any issue. Thanks Sanjay
RE: Sending binary data(not using MTOM) using DataHandler
Hi Martin, Thanks for your reponse. wsdl file is attached. Type is xs:base64Binary in the wsdl. The wsdl was auto generated by grails axis2 plugin. Thanks Sanjay From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Tuesday, April 21, 2009 1:22 PM To: axis-user@ws.apache.org Subject: RE: Sending binary data(not using MTOM) using DataHandler wsdl:definitions xmlns:xsd=http://www.w3.org/2001/XMLSchema; name=XSD_base64Binary ... assume the element you are referencing in your xsd is type=xsd:base64Binary datatype xsd:element name=asNonNillableElementResponse xsd:complexType xsd:sequence xsd:element name=nonNillableElement type=xsd:base64Binary nillable=false minOccurs=1 maxOccurs=1 / /xsd:sequence /xsd:complexType /xsd:element ? Martin could you display your full wsdl __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: sanjay.gu...@billwiseinc.com To: axis-user@ws.apache.org Date: Tue, 21 Apr 2009 12:18:16 -0700 Subject: Sending binary data(not using MTOM) using DataHandler Hi, I have written a service that returns DataHandler containing the binary data(pdf file). When I call that service by using the classes generated by wsdl2java I only get 12k of the binary data. I have seen as reference to 12K buffer wrap issue. I would appreciate if anybody can give me some pointers on how to resole this issue. BTW the service is written in grails and exposed using AXIS2 plugin and all other services(the one not dealing with binary data) work without any issue. Thanks Sanjay Windows Live(tm) Hotmail®:...more than just e-mail. Check it out.http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_more_042009 invoice.wsdl Description: invoice.wsdl
RE: Sending binary data(not using MTOM) using DataHandler
Hi Martin,
I am not sure about question but during debugging I noted that reader.getText()
only gives 16211 bytes which possibly gets translated into 12188 binary bytes.
I don't understand this code well. Don't you think that reader.getText() call
should gives all bytes. I did check the size inside my server side code just
before the return and size is proper.
Thanks
Sanjay
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Tuesday, April 21, 2009 7:06 PM
To: axis-user@ws.apache.org
Subject: RE: Sending binary data(not using MTOM) using DataHandler
org.apache.ws.axis2.GetInvoiceImageResponse.java:
public static GetInvoiceImageResponse
parse(javax.xml.stream.XMLStreamReader reader)
} else if(reader.hasText()) {
//Do the usual conversion
java.lang.String content =
reader.getText();
object.set_return(
org.apache.axis2.databinding.utils.ConverterUtil.convertToBase64Binary(content));
reader.next();
}
}
which calls org.apache.axis2.databinding.utils.ConverterUtil
public static javax.activation.DataHandler convertToBase64Binary(String s) {
// reusing the byteArrayDataSource from the Axiom classes
ByteArrayDataSource byteArrayDataSource = new ByteArrayDataSource(
Base64.decode(s)
);
return new DataHandler(byteArrayDataSource);
}
which calls org.apache.axiom.om.util.Base64.java
public static byte[] decode(String data) {
char[] ibuf = new char[4];
int ibufcount = 0;
byte[] obuf = new byte[data.length() / 4 * 3 + 3];
int obufcount = 0;
for (int i = 0; i data.length(); i++) {
char ch = data.charAt(i);
if (ch == S_BASE64PAD || ch S_DECODETABLE.length
S_DECODETABLE[ch] != Byte.MAX_VALUE) {
ibuf[ibufcount++] = ch;
if (ibufcount == ibuf.length) {
ibufcount = 0;
obufcount += decode0(ibuf, obuf, obufcount);
}
}
}
if (obufcount == obuf.length)
return obuf;
byte[] ret = new byte[obufcount];
System.arraycopy(obuf, 0, ret, 0, obufcount);
return ret;
}
looks as if convertToBase64Binary
call to Base64.decode
byte[] obuf = new byte[data.length() / 4 * 3 + 3];
is dividing the data length by 15
what is the expected processing Base64.decode for Base64Binary input
?
Martin Gainty
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de
déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then
we ask politely to report. Each unauthorized forwarding or manufacturing of a
copy is inadmissible. This message serves only for the exchange of information
and has no legal binding effect. Due to the easy manipulation of emails we
cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: mgai...@hotmail.com
To: axis-user@ws.apache.org
Subject: RE: Sending binary data(not using MTOM) using DataHandler
Date: Tue, 21 Apr 2009 16:21:49 -0400
wsdl:definitions xmlns:xsd=http://www.w3.org/2001/XMLSchema;
name=XSD_base64Binary
...
assume the element you are referencing in your xsd is type=xsd:base64Binary
datatype
xsd:element name=asNonNillableElementResponse
xsd:complexType
xsd:sequence
xsd:element name=nonNillableElement
type=xsd:base64Binary nillable=false
minOccurs=1 maxOccurs=1 /
/xsd:sequence
/xsd:complexType
/xsd:element
?
Martin
could you display your full wsdl
RE: Securing Axis2 REST Style Services
Hi Ruchith, Thanks for proving the class. I am assuming that I needed to add this handler to the transport phase after SOAPActionBasedDispatcher. I was able to find the wso2 dependencies from wso2wsas version 2.3. and able to compile the class by using wso2wsas-core-2.3.jar and wso2utils-2.2.jar files. But I am having trouble when I run it. The program depends javax.servlet.http.HttpServletRequest and javax.servlet.http.HttpServletResponse classes and they are available in servlet-api.jar in standard tomcat 6.0.18. But for some reason I get this error. SEVERE: StandardWrapper.Throwable java.lang.Error: Unresolved compilation problems: The import javax.servlet.http cannot be resolved The import javax.servlet.http cannot be resolved HttpServletRequest cannot be resolved to a type HttpServletRequest cannot be resolved to a type HttpServletResponse cannot be resolved to a type HttpServletResponse cannot be resolved to a type HttpServletResponse cannot be resolved at org.wso2.wsas.security.pox.POXSecurityHandler.init(POXSecurityHandler.java:44) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) I tried unzipping the servlet-api.jar in classes dir and got this error. SEVERE: Servlet /axis2 threw load() exception java.lang.ClassCastException: org.apache.axis2.transport.http.AxisServlet cannot be cast to javax.servlet.Servlet at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1104) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4058) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4364) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:924) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:887) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) I would really appreciate any help. I am using axis2-1.4.1 with rampart 1.4. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 5:52 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Oops :-) Here you go : https://wso2.org/repos/wso2/branches/wsas/java/2.2/wsas/java/modules/core/src/org/wso2/wsas/security/pox/POXSecurityHandler.java On Thu, Apr 16, 2009 at 8:36 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Ruchith, Thanks for the quick reply. Could you please point me to the link that talks about this solutions. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 4:31 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Hi, For the REST style calls you can use HTTPS + Basic Auth Have a look at this [1] handler from WSO2 WSAS. This will simply add the UsernameToken into the SOAP representation of the incoming REST request, which will be processed by Rampart (which you have already configured). Thanks, Ruchith On Thu, Apr 16, 2009 at 3:04 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user
RE: Securing Axis2 REST Style Services
) at java.sql.DriverManager.getConnection(DriverManager.java:154) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423) ... 35 more -Original Message- From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Sunday, April 19, 2009 8:44 PM To: axis-user@ws.apache.org Subject: RE: Securing Axis2 REST Style Services Hi Ruchith, Thanks for proving the class. I am assuming that I needed to add this handler to the transport phase after SOAPActionBasedDispatcher. I was able to find the wso2 dependencies from wso2wsas version 2.3. and able to compile the class by using wso2wsas-core-2.3.jar and wso2utils-2.2.jar files. But I am having trouble when I run it. The program depends javax.servlet.http.HttpServletRequest and javax.servlet.http.HttpServletResponse classes and they are available in servlet-api.jar in standard tomcat 6.0.18. But for some reason I get this error. SEVERE: StandardWrapper.Throwable java.lang.Error: Unresolved compilation problems: The import javax.servlet.http cannot be resolved The import javax.servlet.http cannot be resolved HttpServletRequest cannot be resolved to a type HttpServletRequest cannot be resolved to a type HttpServletResponse cannot be resolved to a type HttpServletResponse cannot be resolved to a type HttpServletResponse cannot be resolved at org.wso2.wsas.security.pox.POXSecurityHandler.init(POXSecurityHandler.java:44) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) I tried unzipping the servlet-api.jar in classes dir and got this error. SEVERE: Servlet /axis2 threw load() exception java.lang.ClassCastException: org.apache.axis2.transport.http.AxisServlet cannot be cast to javax.servlet.Servlet at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1104) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4058) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4364) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:924) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:887) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) I would really appreciate any help. I am using axis2-1.4.1 with rampart 1.4. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 5:52 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Oops :-) Here you go : https://wso2.org/repos/wso2/branches/wsas/java/2.2/wsas/java/modules/core/src/org/wso2/wsas/security/pox/POXSecurityHandler.java On Thu, Apr 16, 2009 at 8:36 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Ruchith, Thanks for the quick reply. Could you please point me to the link that talks about this solutions. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 4:31 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Hi, For the REST style calls you can
Securing Axis2 REST Style Services
HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user/password security using rampart and it's working fine for SOAP calls. I generated the client using wsdl2java.My question is how do I secure the REST style calls. Do I need to do anything special. I need to deploy these services into production soon and any help or pointers would be greatly appreciated. Thanks Sanjay
RE: Securing Axis2 REST Style Services
Hi Ruchith, Thanks for the quick reply. Could you please point me to the link that talks about this solutions. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 4:31 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Hi, For the REST style calls you can use HTTPS + Basic Auth Have a look at this [1] handler from WSO2 WSAS. This will simply add the UsernameToken into the SOAP representation of the incoming REST request, which will be processed by Rampart (which you have already configured). Thanks, Ruchith On Thu, Apr 16, 2009 at 3:04 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user/password security using rampart and it's working fine for SOAP calls. I generated the client using wsdl2java.My question is how do I secure the REST style calls. Do I need to do anything special. I need to deploy these services into production soon and any help or pointers would be greatly appreciated. Thanks Sanjay -- http://blog.ruchith.org
Apache Axis2 Plugin
Hi, Does this plugin support security using apache rampart module? Thanks Sanjay
RE: Implementation of WS security using Apache Rampart
Hi Shrey, Use the tutorial from the link. It worked for me without any major. http://wso2.org/library/3190 Sanjay From: shreya gupta [mailto:shreya.gupt...@gmail.com] Sent: Thursday, March 19, 2009 3:02 AM To: axis-user@ws.apache.org Subject: Implementation of WS security using Apache Rampart Hey, We are trying to implement WS security for the web service that we have developed. We are new to Axis2.could you please guide us through a step by step procedure as to how to configure apache Rampart and to implement it. The other threads i have searched do not provide sufficient help . Kindly help us.We are stuck with it since a long time :( -- Shreya
RE: InOnlyAxisOperation Error
Agree but I don't see anything wrong with my services.xml. I am clueless on what would cause this issue. I looked at the client code as well and it's using RobustOutOnlyAxisOperation for the operation. Sanjay messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers -Original Message- From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Fri 2/6/2009 7:40 PM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error From the stack trace it looks like an InOutMessageReceiver was used for an InOnly Operation. Thanks, Keith. On Fri, Feb 6, 2009 at 11:27 PM, Sanjay Gupta sanjay.gu...@primal.comwrote: Keith, Thanks for you reply and pointer. I tried your sugession but I am still getting the error. Here is the stack trace. Thanks Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) -Original Message- From: keith chapman [mailto:keithgchap...@gmail.comkeithgchap...@gmail.com ] Sent: Fri 2/6/2009 12:17 AM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error In your messageReceivers can you try using the following instead, messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers Thanks, Keith. On Fri, Feb 6, 2009 at 11:50 AM, Sanjay Gupta sanjay.gu...@primal.com wrote: Hi Keith, Here is my services.xml files. Thanks Sanjay serviceGroup service name=Provision scope=application targetNamespace= http://provision.ws.ccb.primalsw.com/; description Provision Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ /messageReceivers schema schemaNamespace=http://provision.ws.ccb.primalsw.com/xsd/ parameter name=ServiceClasscom.primalsw.ccb.ws.ProvisionHandler/parameter /service /serviceGroup -Original Message- From: keith chapman [mailto:keithgchap...@gmail.comkeithgchap...@gmail.com keithgchap...@gmail.com ] Sent: Thu 2/5/2009 10:01 PM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error Can you provide your service please. You haven't provided enough information to help you... Thanks, Keith. On Thu, Feb 5, 2009 at 10:55 PM, Sanjay Gupta sanjay.gu...@primal.com wrote: Hi, I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while calling a service which returns nothing(void). See the stack trace below. The doc mentions these four types of operations but I don't know which one to pick and how to set it during client generation
RE: InOnlyAxisOperation Error
Keith, Thanks for you reply and pointer. I tried your sugession but I am still getting the error. Here is the stack trace. Thanks Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) -Original Message- From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Fri 2/6/2009 12:17 AM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error In your messageReceivers can you try using the following instead, messageReceivers messageReceiver mep=http://www.w3.org/ns/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers Thanks, Keith. On Fri, Feb 6, 2009 at 11:50 AM, Sanjay Gupta sanjay.gu...@primal.comwrote: Hi Keith, Here is my services.xml files. Thanks Sanjay serviceGroup service name=Provision scope=application targetNamespace= http://provision.ws.ccb.primalsw.com/; description Provision Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ /messageReceivers schema schemaNamespace=http://provision.ws.ccb.primalsw.com/xsd/ parameter name=ServiceClasscom.primalsw.ccb.ws.ProvisionHandler/parameter /service /serviceGroup -Original Message- From: keith chapman [mailto:keithgchap...@gmail.comkeithgchap...@gmail.com ] Sent: Thu 2/5/2009 10:01 PM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error Can you provide your service please. You haven't provided enough information to help you... Thanks, Keith. On Thu, Feb 5, 2009 at 10:55 PM, Sanjay Gupta sanjay.gu...@primal.com wrote: Hi, I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while calling a service which returns nothing(void). See the stack trace below. The doc mentions these four types of operations but I don't know which one to pick and how to set it during client generation. DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem I have both types of operations with return and without return. All my operations takes some kind of argument simple as well as some that takes customer objects. Any help will be greatly appreciated. Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive
InOnlyAxisOperation Error
Hi, I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while calling a service which returns nothing(void). See the stack trace below. The doc mentions these four types of operations but I don't know which one to pick and how to set it during client generation. DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem I have both types of operations with return and without return. All my operations takes some kind of argument simple as well as some that takes customer objects. Any help will be greatly appreciated. Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619)
RE: InOnlyAxisOperation Error
Hi Keith, Here is my services.xml files. Thanks Sanjay serviceGroup service name=Provision scope=application targetNamespace=http://provision.ws.ccb.primalsw.com/; description Provision Service /description messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ /messageReceivers schema schemaNamespace=http://provision.ws.ccb.primalsw.com/xsd/ parameter name=ServiceClasscom.primalsw.ccb.ws.ProvisionHandler/parameter /service /serviceGroup -Original Message- From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Thu 2/5/2009 10:01 PM To: axis-user@ws.apache.org Subject: Re: InOnlyAxisOperation Error Can you provide your service please. You haven't provided enough information to help you... Thanks, Keith. On Thu, Feb 5, 2009 at 10:55 PM, Sanjay Gupta sanjay.gu...@primal.comwrote: Hi, I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while calling a service which returns nothing(void). See the stack trace below. The doc mentions these four types of operations but I don't know which one to pick and how to set it during client generation. DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem I have both types of operations with return and without return. All my operations takes some kind of argument simple as well as some that takes customer objects. Any help will be greatly appreciated. Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
InOnlyAxisOperation
Hi, I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while calling a service which returns nothing(void). See the stack trace below. The doc mentions these four types of operations but I don't know which one to pick and how to set it during client generation. DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem I have both types of operations with return and without return. All my operations takes some kind of argument simple as well as some that takes customer objects. Any help will be greatly appreciated. Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619)
RE: InOnlyAxisOperation
Hi, I read some messages which pointed out at server.xml. My server.xml looks good as far as I can see. But I still have issue. I even tried removing in-only receiver without any luck. service name=Customer scope=application targetNamespace=http://customer.ws.ccb.primalsw.com/; description Customer 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 schema schemaNamespace=http://customer.ws.ccb.primalsw.com/xsd/ parameter name=ServiceClasscom.primalsw.ccb.ws.CustomerHandler/parameter /service From: Sanjay Gupta [mailto:sanjay.gu...@primal.com] Sent: Wednesday, February 04, 2009 11:12 AM To: axis-user@ws.apache.org Subject: InOnlyAxisOperation Hi, I just have upgraded my axis 1.2 web services to 1.4.1 and getting error while calling a service which returns nothing(void). See the stack trace below. The doc mentions these four types of operations but I don't know which one to pick and how to set it during client generation. DoInOnly, NoParameters, TwoWayOneParameterEcho, and MultipleParametersAddItem I have both types of operations with return and without return. All my operations takes some kind of argument simple as well as some that takes customer objects. Any help will be greatly appreciated. Sanjay [ERROR] An access occurred that is not valid. java.lang.UnsupportedOperationException: An access occurred that is not valid. at org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:109) at org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContextBuilder.java:190) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.jav :37) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619)
