Re: Axis to Axis2 migration doubt
Hi Deepak,
I am gettigg the below message when using java2wsdl task.
java.lang.NoClassDefFoundError: javax/xml/rpc/holders/StringHolder.
here is the build file content.
taskdef name=java2wsdl
classname=org.apache.ws.java2wsdl.Java2WSDLTask
classpathref=axis2.classpath
loaderref=axis/
java2wsdl
className=dd.app.webservice.${target.directory.each}.service.${target.servicename.each}
outputLocation=http://localhost:8080/services/${target.servicename.each};
targetNamespace=urn:${target.servicename.each}
classpath
pathelement path=${axis.class.path}/
pathelement
location=${deploy.home}/install/classes/
/classpath
/java2wsdl
my application was developed using axis1.2rc2 and used StringHolder
,Currently I am upgrading to Axis2.1.5.
If axis2.1.5 is not supported StringHolders,How to upgrade the existing java
files?
Could you please le me know how to over come these issues(java2wsdl and
existing appilication issues like to support StringHolders)
Thanks in advance,
mikkilineni
deepak.pansheriya wrote:
In my axis deployment file I use following operation node to describe IN
and OUT parameter of my method having signature as
public short WMLS_GetFromStore(String WellTypeIn, String
XMLIn,StringHolder XMLOut, StringHolder SuppMsgOut)
operation name=WMLS_GetFromStore
parameter name=TypeIn mode=IN/
parameter name=XMLIn mode=IN/
parameter name=XMLOut mode=OUT/
parameter name=SuppMsgOut mode=OUT/
/operation
How to achieve same in Axis2? I can not able to find out way to define
parameter as OUT type with AXIS2.
could you please update me with way of achieving same with AXIS2?
With Regards,
Deepak Jerambhai Pansheriya
Tata Consultancy Services
Yantra Park -(STPI)
Mailto: deepak.pansher...@tcs.com
Website: http://www.tcs.com
Experience certainty. IT Services
Business Solutions
Outsourcing
=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
--
View this message in context:
http://www.nabble.com/Axis-to-Axis2-migration-doubt-tp11942874p25332775.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: [AXIS2] Migration Issues for Axis1 - Axis2
On Wed, Feb 4, 2009 at 5:43 PM, Sumit Gaikaiwari sgaikaiw...@unica.comwrote: Hi, I am working on migration of web-services in our project from Axis1 to Axis2. In generating client/server classes I found those are not equivalent to classes generated by Axis1 WSDL2Java utility. We have an inheritance hierarchy of data classes created in WSDL. When java classes are created using Axis1 wsdl2java, it adds a multi-value constructor to each class which passes values required by super class using super(param1, param2…) and instantiates it's own instance variable from remaining argument. Whereas, axis2 wsdl2java do not generate any constructor, so the only constructor which can be invoked is default constructor. We were using multi-value constructors in earlier business logic, so if we use these new classes directly, we will have to change code in all such places. Is there any way Axis2 to generate classes in such manner? Please let me know if I should add any other option to create such hierarchy. I have tried using ADB and XMLBeans binding. Below is the command I tried by using ADB binding- WSDL2Java -uri PlanIntegrationServices1_0.wsdl -d adb -s -o build2 -u there is no such option with ADB. There is no particular reason for not having this but it has not done that :). thanks, Amila. I have also attached wsdl as well as classes generated by axis1 and axis2 style; you can notice there is a multiple arg constructor in axis1 style classes but not in axis2 generated code. Kind Regards, Sumit Gaikaiwari -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: [AXIS2] Migration Issues for Axis1 - Axis2
Hi, if your application uses existing Java data objects then you may want to use JiBX data binding with Axis2. You will need to define the binding between Java objects and the XML messages. Sumit Gaikaiwari-3 wrote: Hi, I am working on migration of web-services in our project from Axis1 to Axis2. In generating client/server classes I found those are not equivalent to classes generated by Axis1 WSDL2Java utility. We have an inheritance hierarchy of data classes created in WSDL. When java classes are created using Axis1 wsdl2java, it adds a multi-value constructor to each class which passes values required by super class using super(param1, param2...) and instantiates it's own instance variable from remaining argument. Whereas, axis2 wsdl2java do not generate any constructor, so the only constructor which can be invoked is default constructor. We were using multi-value constructors in earlier business logic, so if we use these new classes directly, we will have to change code in all such places. Is there any way Axis2 to generate classes in such manner? Please let me know if I should add any other option to create such hierarchy. I have tried using ADB and XMLBeans binding. Below is the command I tried by using ADB binding- WSDL2Java -uri PlanIntegrationServices1_0.wsdl -d adb -s -o build2 -u I have also attached wsdl as well as classes generated by axis1 and axis2 style; you can notice there is a multiple arg constructor in axis1 style classes but not in axis2 generated code. Kind Regards, Sumit Gaikaiwari -- View this message in context: http://www.nabble.com/-AXIS2--Migration-Issues-for-Axis1--%3E-Axis2-tp21829252p21883065.html Sent from the Axis - User mailing list archive at Nabble.com.
[AXIS2] Migration Issues for Axis1 - Axis2
Hi, I am working on migration of web-services in our project from Axis1 to Axis2. In generating client/server classes I found those are not equivalent to classes generated by Axis1 WSDL2Java utility. We have an inheritance hierarchy of data classes created in WSDL. When java classes are created using Axis1 wsdl2java, it adds a multi-value constructor to each class which passes values required by super class using super(param1, param2...) and instantiates it's own instance variable from remaining argument. Whereas, axis2 wsdl2java do not generate any constructor, so the only constructor which can be invoked is default constructor. We were using multi-value constructors in earlier business logic, so if we use these new classes directly, we will have to change code in all such places. Is there any way Axis2 to generate classes in such manner? Please let me know if I should add any other option to create such hierarchy. I have tried using ADB and XMLBeans binding. Below is the command I tried by using ADB binding- WSDL2Java -uri PlanIntegrationServices1_0.wsdl -d adb -s -o build2 -u I have also attached wsdl as well as classes generated by axis1 and axis2 style; you can notice there is a multiple arg constructor in axis1 style classes but not in axis2 generated code. Kind Regards, Sumit Gaikaiwari
Re: Sandesha2 error after Axis2 migration
I have found the same issue : https://issues.apache.org/jira/browse/SANDESHA2-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591999#action_12591999 I have the same bug but I don't know how to fix it. I use Axis2 1.4, Sandesha2 1.3. The message is sent correctly but the server print a message each minutes : [WARN] Sender.checkForOrphanMessages() - A message has been waiting for a MakeConnection call. The message will continue to wait, but there may be a problem with the client configuration. Sandesha message type 7. Anyone have already have the same problem and correct it please ? Thanks Fabien Couvert a écrit : Thank you very much Amila. Axis2 1.4.1 RC1 correct the problem :) But now Sandesha2 give me a recurrent warning every minutes when I try to send one message, the message is sent correctly but the server write this line in the log : 2008-07-28 11:11:23,354 [WARN] Sender.checkForOrphanMessages() - A message has been waiting for a MakeConnection call. The message will continue to wait, but there may be a problem with the client configuration. Sandesha message type 7. Do you have any idea please ? Thank you Amila Suriarachchi a écrit : I think this is a problem with Axis2 1.4. Please have a look at with the Axis2 1.4.1 RC1 http://people.apache.org/~nandana/axis2-1.4.1/RC1/dist/ http://people.apache.org/%7Enandana/axis2-1.4.1/RC1/dist/ thanks, Amila. On Fri, Jul 25, 2008 at 5:07 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Nobody have an idea please ? Sandesha2 policies needs to be change from Axis2 1.3 to Axis2 1.4 ?! help Fabien Couvert a écrit : Here it is : 2008-07-24 11:40:40,192 [ERROR] AxisServlet.doPost() - java.lang.NullPointerException at org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java:122) 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.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131) 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(Unknown Source) Samisa Abeysinghe a écrit : Fabien Couvert wrote: Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. What is the stack trace? Samisa... Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: Sandesha2 error after Axis2 migration
Thank you very much Amila. Axis2 1.4.1 RC1 correct the problem :) But now Sandesha2 give me a recurrent warning every minutes when I try to send one message, the message is sent correctly but the server write this line in the log : 2008-07-28 11:11:23,354 [WARN] Sender.checkForOrphanMessages() - A message has been waiting for a MakeConnection call. The message will continue to wait, but there may be a problem with the client configuration. Sandesha message type 7. Do you have any idea please ? Thank you Amila Suriarachchi a écrit : I think this is a problem with Axis2 1.4. Please have a look at with the Axis2 1.4.1 RC1 http://people.apache.org/~nandana/axis2-1.4.1/RC1/dist/ http://people.apache.org/%7Enandana/axis2-1.4.1/RC1/dist/ thanks, Amila. On Fri, Jul 25, 2008 at 5:07 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Nobody have an idea please ? Sandesha2 policies needs to be change from Axis2 1.3 to Axis2 1.4 ?! help Fabien Couvert a écrit : Here it is : 2008-07-24 11:40:40,192 [ERROR] AxisServlet.doPost() - java.lang.NullPointerException at org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java:122) 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.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131) 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(Unknown Source) Samisa Abeysinghe a écrit : Fabien Couvert wrote: Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. What is the stack trace? Samisa... Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sandesha2 error after Axis2 migration
I think this is a problem with Axis2 1.4. Please have a look at with the Axis2 1.4.1 RC1 http://people.apache.org/~nandana/axis2-1.4.1/RC1/dist/ thanks, Amila. On Fri, Jul 25, 2008 at 5:07 PM, Fabien Couvert [EMAIL PROTECTED]wrote: Nobody have an idea please ? Sandesha2 policies needs to be change from Axis2 1.3 to Axis2 1.4 ?! help Fabien Couvert a écrit : Here it is : 2008-07-24 11:40:40,192 [ERROR] AxisServlet.doPost() - java.lang.NullPointerException at org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java:122) 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.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131) 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(Unknown Source) Samisa Abeysinghe a écrit : Fabien Couvert wrote: Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. What is the stack trace? Samisa... Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: Sandesha2 error after Axis2 migration
Nobody have an idea please ? Sandesha2 policies needs to be change from Axis2 1.3 to Axis2 1.4 ?! help Fabien Couvert a écrit : Here it is : 2008-07-24 11:40:40,192 [ERROR] AxisServlet.doPost() - java.lang.NullPointerException at org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java:122) 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.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131) 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(Unknown Source) Samisa Abeysinghe a écrit : Fabien Couvert wrote: Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. What is the stack trace? Samisa... Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sandesha2 error after Axis2 migration
Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sandesha2 error after Axis2 migration
Fabien Couvert wrote: Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. What is the stack trace? Samisa... Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sandesha2 error after Axis2 migration
Here it is : 2008-07-24 11:40:40,192 [ERROR] AxisServlet.doPost() - java.lang.NullPointerException at org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java:122) 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.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131) 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(Unknown Source) Samisa Abeysinghe a écrit : Fabien Couvert wrote: Hi all, I did a migration from Axis2 1.3 to Axis2 1.4 on Tomcat 6.0. Now I get an error when I deploy my webservice : /[ERROR] SandeshaModule.init() - Could not load module policies. Using default values./ When I try to use RM in my application I get a NullPointerException. What is the stack trace? Samisa... Anyone have an idea please? Everything works fine with Axis2 1.3. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] migration from Axis1
Thank you for your answer.
We decided, on our side, to not go further in the migration process,
and stick currently to Axis1, because :
- the session : flash webservices classes do not support WS-
Adressing, (and we cannot add a custom soap enveloppe).
- complex beans with arrays would have made us use the wsdl2java
which would have been a major rewrite of the app (a dozen services,
maybe 50 operations per service, a lot of beans, ...)
and a lack of time to do all of this, we sadly a small structure and
cannot afford having these kind of major changes.
Thanks anyway.
Tom
On 5 avr. 08, at 16:43, Anne Thomas Manes wrote:
I gather that your original WSDL is using RPC/encoded.
Axis2 does not support SOAP encoding, and it is more rigorous about
SOAP and WSDL conformance than Axis. According to the specifications,
faults MUST be defined using document/literal; therefore, the fault
message parts MUST reference elements rather than types.
Try this:
In the bindings, change all use=encoded attributes to use=literal.
In your types section, add an element definition for each fault
message and define its type as the type used in the part definition,
e.g., for this fault:
wsdl:message name=OurCustomException
wsdl:part name=fault type=impl:OurCustomException/
/wsdl:message
define the following element:
xsd:element name=OurCustomException
type=impl:OurCustomException/
And modify the fault message definition like so:
wsdl:message name=OurCustomException
wsdl:part name=fault element=impl:OurCustomException/
/wsdl:message
Anne
On Tue, Apr 1, 2008 at 10:21 AM, Thomas Burdairon
[EMAIL PROTECTED] wrote:
Thank you for your advices, I'm trying to generate java classes
from my old
wsdl files,
and while java files are generated almost without problems (need
to remove
some use=encoded so the operation is OK),
I cannot manage to generate java files from WSDL with operations
declared
with faults.
ex :
wsdl:message name=OurCustomException
wsdl:part name=fault type=impl:OurCustomException/
/wsdl:message
- we get Part 'fault' of fault message
'{urn:our.package.SoapGeography}
OurCustomException' must be defined with 'element=QName' and not
'type=QName'
- change to element=impl:OurCustomException
But at this time we get some
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type
was mapped
to the name OurCustomException with namespace
urn:our.package.SoapGeography
that prevent java classes to be generated, and I cant see what's
wrong.
the command line used is :
.build/axis2-1.3/bin/wsdl2java.sh -d xmlbeans -uri
~/Desktop/wsdls/Geography.wsdl -ss -g -sd -o output -p our.package
Another question while here :
In Axis 1.4, we were using the class
org.apache.axis.handlers.SimpleSessionHandler to manage the session.
On 1st works, i used a soapsession for my services and so my
messages now
contain some WS Addressing parts.
The problem is that our clients are written in flash
actionscript, and
webservice is very limited on this platform, and the addressing
namespace
does not seem to be declared.
Is there any simplier solution?
Has anybody ever used Flash with axis2 and a session management ?
Thanks for your time !
Tom
On 29 mars 08, at 14:14, Anne Thomas Manes wrote:
If you want to keep the WSDL the same, then I suggest you use the
WSDL-first approach rather than the POJO approach. Take the WSDL
from
your Axis 1.4 service and use WSDL2Java to generate a new service
skeleton.
Anne
On Fri, Mar 28, 2008 at 5:47 AM, Thomas Burdairon
[EMAIL PROTECTED] wrote:
Greatings
I'm working on a migration from Axis1.4 to Axis2 1.3.
We choosed to use the POJO approach since it seems to be the
easiest
one. That means I don't generate my WSDL, they are
autogenerated by
axis.
I am currently encountering 2 major problems.
- Beans presents in WSDL
Some of our services return different objects depending of the
parameters. To do so, we have a simple inheritance schema that
look
like :
interface A
object B implements Aobject C implement A...
All the methods in the service return A, so by default the
generated
WSDL only contains the definition of A.
In Axis1, there an extraClasses parameter in the WSDL that we were
using to declare objects B and C.I couldn't find an equivalent in
Axis2 (in the service.xml).I've read http://issues.apache.org/
jira/
browse/AXIS2-1056, but it seem to fix only java2wsdl and this
isn't
what I am looking for.Is there any way for it?or, in your opinion,
would a patch be easy to write?
- Beans description in WSDL for List :Some of the javabeans
sent or
received by our webservices contains List
One nice feature in axis1 was that java.util.List were
converted in
the WSDL as type=impl:ArrayOf_xsd_anyTypeNow, it looks like
Re: [Axis2] migration from Axis1
I gather that your original WSDL is using RPC/encoded.
Axis2 does not support SOAP encoding, and it is more rigorous about
SOAP and WSDL conformance than Axis. According to the specifications,
faults MUST be defined using document/literal; therefore, the fault
message parts MUST reference elements rather than types.
Try this:
In the bindings, change all use=encoded attributes to use=literal.
In your types section, add an element definition for each fault
message and define its type as the type used in the part definition,
e.g., for this fault:
wsdl:message name=OurCustomException
wsdl:part name=fault type=impl:OurCustomException/
/wsdl:message
define the following element:
xsd:element name=OurCustomException type=impl:OurCustomException/
And modify the fault message definition like so:
wsdl:message name=OurCustomException
wsdl:part name=fault element=impl:OurCustomException/
/wsdl:message
Anne
On Tue, Apr 1, 2008 at 10:21 AM, Thomas Burdairon
[EMAIL PROTECTED] wrote:
Thank you for your advices, I'm trying to generate java classes from my old
wsdl files,
and while java files are generated almost without problems (need to remove
some use=encoded so the operation is OK),
I cannot manage to generate java files from WSDL with operations declared
with faults.
ex :
wsdl:message name=OurCustomException
wsdl:part name=fault type=impl:OurCustomException/
/wsdl:message
- we get Part 'fault' of fault message '{urn:our.package.SoapGeography}
OurCustomException' must be defined with 'element=QName' and not
'type=QName'
- change to element=impl:OurCustomException
But at this time we get some
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped
to the name OurCustomException with namespace urn:our.package.SoapGeography
that prevent java classes to be generated, and I cant see what's wrong.
the command line used is :
.build/axis2-1.3/bin/wsdl2java.sh -d xmlbeans -uri
~/Desktop/wsdls/Geography.wsdl -ss -g -sd -o output -p our.package
Another question while here :
In Axis 1.4, we were using the class
org.apache.axis.handlers.SimpleSessionHandler to manage the session.
On 1st works, i used a soapsession for my services and so my messages now
contain some WS Addressing parts.
The problem is that our clients are written in flash actionscript, and
webservice is very limited on this platform, and the addressing namespace
does not seem to be declared.
Is there any simplier solution?
Has anybody ever used Flash with axis2 and a session management ?
Thanks for your time !
Tom
On 29 mars 08, at 14:14, Anne Thomas Manes wrote:
If you want to keep the WSDL the same, then I suggest you use the
WSDL-first approach rather than the POJO approach. Take the WSDL from
your Axis 1.4 service and use WSDL2Java to generate a new service
skeleton.
Anne
On Fri, Mar 28, 2008 at 5:47 AM, Thomas Burdairon
[EMAIL PROTECTED] wrote:
Greatings
I'm working on a migration from Axis1.4 to Axis2 1.3.
We choosed to use the POJO approach since it seems to be the easiest
one. That means I don't generate my WSDL, they are autogenerated by
axis.
I am currently encountering 2 major problems.
- Beans presents in WSDL
Some of our services return different objects depending of the
parameters. To do so, we have a simple inheritance schema that look
like :
interface A
object B implements Aobject C implement A...
All the methods in the service return A, so by default the generated
WSDL only contains the definition of A.
In Axis1, there an extraClasses parameter in the WSDL that we were
using to declare objects B and C.I couldn't find an equivalent in
Axis2 (in the service.xml).I've read http://issues.apache.org/jira/
browse/AXIS2-1056, but it seem to fix only java2wsdl and this isn't
what I am looking for.Is there any way for it?or, in your opinion,
would a patch be easy to write?
- Beans description in WSDL for List :Some of the javabeans sent or
received by our webservices contains List
One nice feature in axis1 was that java.util.List were converted in
the WSDL as type=impl:ArrayOf_xsd_anyTypeNow, it looks like
type=xs:anyType
i tried to convert some of them ito arrays, just to see and i get
maxOccurs=unbounded minOccurs=0 seems weird since it is not
explicitly said it is an array, but why not ...
problem is i used to use ListNumber as type and it's strangely
deserialized.is Number type supported by Axis2?is there an official
list of supported java types ?
thanks for your time and your answers
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Re: [Axis2] migration from Axis1
Thank you for your advices, I'm trying to generate java classes from
my old wsdl files,
and while java files are generated almost without problems (need to
remove some use=encoded so the operation is OK),
I cannot manage to generate java files from WSDL with operations
declared with faults.
ex :
wsdl:message name=OurCustomException
wsdl:part name=fault type=impl:OurCustomException/
/wsdl:message
- we get Part 'fault' of fault message
'{urn:our.package.SoapGeography} OurCustomException' must be defined
with 'element=QName' and not 'type=QName'
- change to element=impl:OurCustomException
But at this time we get some
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was
mapped to the name OurCustomException with namespace
urn:our.package.SoapGeography
that prevent java classes to be generated, and I cant see what's wrong.
the command line used is :
.build/axis2-1.3/bin/wsdl2java.sh -d xmlbeans -uri ~/Desktop/wsdls/
Geography.wsdl -ss -g -sd -o output -p our.package
Another question while here :
In Axis 1.4, we were using the class
org.apache.axis.handlers.SimpleSessionHandler to manage the session.
On 1st works, i used a soapsession for my services and so my messages
now contain some WS Addressing parts.
The problem is that our clients are written in flash actionscript,
and webservice is very limited on this platform, and the addressing
namespace does not seem to be declared.
Is there any simplier solution?
Has anybody ever used Flash with axis2 and a session management ?
Thanks for your time !
Tom
On 29 mars 08, at 14:14, Anne Thomas Manes wrote:
If you want to keep the WSDL the same, then I suggest you use the
WSDL-first approach rather than the POJO approach. Take the WSDL from
your Axis 1.4 service and use WSDL2Java to generate a new service
skeleton.
Anne
On Fri, Mar 28, 2008 at 5:47 AM, Thomas Burdairon
[EMAIL PROTECTED] wrote:
Greatings
I'm working on a migration from Axis1.4 to Axis2 1.3.
We choosed to use the POJO approach since it seems to be the easiest
one. That means I don't generate my WSDL, they are autogenerated by
axis.
I am currently encountering 2 major problems.
- Beans presents in WSDL
Some of our services return different objects depending of the
parameters. To do so, we have a simple inheritance schema that look
like :
interface A
object B implements Aobject C implement A...
All the methods in the service return A, so by default the generated
WSDL only contains the definition of A.
In Axis1, there an extraClasses parameter in the WSDL that we were
using to declare objects B and C.I couldn't find an equivalent in
Axis2 (in the service.xml).I've read http://issues.apache.org/jira/
browse/AXIS2-1056, but it seem to fix only java2wsdl and this isn't
what I am looking for.Is there any way for it?or, in your opinion,
would a patch be easy to write?
- Beans description in WSDL for List :Some of the javabeans sent or
received by our webservices contains List
One nice feature in axis1 was that java.util.List were converted in
the WSDL as type=impl:ArrayOf_xsd_anyTypeNow, it looks like
type=xs:anyType
i tried to convert some of them ito arrays, just to see and i get
maxOccurs=unbounded minOccurs=0 seems weird since it is not
explicitly said it is an array, but why not ...
problem is i used to use ListNumber as type and it's strangely
deserialized.is Number type supported by Axis2?is there an official
list of supported java types ?
thanks for your time and your answers
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] migration from Axis1
Greatings I'm working on a migration from Axis1.4 to Axis2 1.3. We choosed to use the POJO approach since it seems to be the easiest one. That means I don't generate my WSDL, they are autogenerated by axis. I am currently encountering 2 major problems. - Beans presents in WSDL Some of our services return different objects depending of the parameters. To do so, we have a simple inheritance schema that look like : interface A object B implements Aobject C implement A... All the methods in the service return A, so by default the generated WSDL only contains the definition of A. In Axis1, there an extraClasses parameter in the WSDL that we were using to declare objects B and C.I couldn't find an equivalent in Axis2 (in the service.xml).I've read http://issues.apache.org/jira/ browse/AXIS2-1056, but it seem to fix only java2wsdl and this isn't what I am looking for.Is there any way for it?or, in your opinion, would a patch be easy to write? - Beans description in WSDL for List :Some of the javabeans sent or received by our webservices contains List One nice feature in axis1 was that java.util.List were converted in the WSDL as type=impl:ArrayOf_xsd_anyTypeNow, it looks like type=xs:anyType i tried to convert some of them ito arrays, just to see and i get maxOccurs=unbounded minOccurs=0 seems weird since it is not explicitly said it is an array, but why not ... problem is i used to use ListNumber as type and it's strangely deserialized.is Number type supported by Axis2?is there an official list of supported java types ? thanks for your time and your answers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] Migration issue from Axis1 to Axis2
Hello Axis User, I am migrating a webservice that was using Axis1 to Axis2. In the server-config.wsdd, the parameter scope was set to session (parameter name=scope value=Session/). This way, while the client was in the same HTTP session, the same web service was used (the constructor was not called). How can I do the same in Axis2? I don't see anything on the web! Thanks in advance, Pierre
Re: [AXIS2] Migration issue from Axis1 to Axis2
Hello Axis User, I am migrating a webservice that was using Axis1 to Axis2. In the server-config.wsdd, the parameter scope was set to session (parameter name=scope value=Session/). This way, while the client was in the same HTTP session, the same web service was used (the constructor was not called). How can I do the same in Axis2? I don't see anything on the web! Thanks in advance, you can specify the session in services.xml , please refer to the following article for more information www.developer.com/java/web/article.php/3620661 Thanks Deepal Pierre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Migration issue from Axis1 to Axis2
Thanks, it is working exactly as I wanted! Pierre Deepal Jayasinghe [EMAIL PROTECTED] 14/02/2008 11:40 Veuillez répondre à axis-user@ws.apache.org A axis-user@ws.apache.org cc Objet Re: [AXIS2] Migration issue from Axis1 to Axis2 Hello Axis User, I am migrating a webservice that was using Axis1 to Axis2. In the server-config.wsdd, the parameter scope was set to session (parameter name=scope value=Session/). This way, while the client was in the same HTTP session, the same web service was used (the constructor was not called). How can I do the same in Axis2? I don't see anything on the web! Thanks in advance, you can specify the session in services.xml , please refer to the following article for more information www.developer.com/java/web/article.php/3620661 Thanks Deepal Pierre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Accessing WSDL causes NullPointerException (on .NET to Axis2 migration)
Hello, I'm trying to switch my web service created using .NET to Axis2. At first, I've generated server-side skeleton codes from currently publishing WSDL by wsdl2java. Next, I've built .aar file using generated ant file and upload it to the server through Axis2 administration site. (Business logic was not implemented at that point, because I only wanted to make sure it works) On the administration page, the service looks available and activated. And I've made sure .aar contains WSDL file in META-INF directory. At last, accessing new WSDL causes the exception below: org.apache.axis2.AxisFault at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1148) at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1077) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent .java:280) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23. jar.so) at javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23. jar.so) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(catalina-5. 5.23.jar.soa01s4g.so) at org.apache.catalina.core.ApplicationFilterChain.doFilter(catalina-5.5. 23.jar.soa01s4g.so) at org.apache.catalina.core.StandardWrapperValve.invoke(catalina-5.5.23.jar.soa 01s4g.so) at org.apache.catalina.core.StandardContextValve.invoke(catalina-5.5.23.jar.soa 01s4g.so) at org.apache.catalina.core.StandardHostValve.invoke(catalina-5.5.23.jar. soa01s4g.so) at org.apache.catalina.valves.ErrorReportValve.invoke(catalina-5.5.23.jar.soa01 s4g.so) at org.apache.catalina.core.StandardEngineValve.invoke(catalina-5.5.23.jar.soa0 1s4g.so) at org.apache.catalina.connector.CoyoteAdapter.service(catalina-5.5.23.jar.soa0 1s4g.so) at org.apache.coyote.http11.Http11Processor.process(tomcat-http-5.5.23.jar.so) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(tomcat-http-5.5.23.jar.so) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(tomcat-util-5.5.23. jar.so) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(tomcat-util-5.5. 23.jar.so) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(tomcat-util-5. 5.23.jar.so) at java.lang.Thread.run(libgcj.so.7rh) Caused by: java.lang.NullPointerException at org.apache.axiom.om.impl.util.OMSerializerUtil.generateSetPrefix(OMSerialize rUtil.java:560) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializ erUtil.java:273) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializ erUtil.java:172) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl. java:768) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl. java:756) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:383) at org.apache.axis2.util.XMLPrettyPrinter.prettify(XMLPrettyPrinter.java: 135) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1144) ...19 more What was wrong? I'm using Axis2 1.3, Tomcat 5.5.20 and JDK1.5.0_06. Thanks in advance Kengo Seki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Accessing WSDL causes NullPointerException (on .NET to Axis2 migration)
Can you send the created aar so that We can check what's going on. Thanks, Keith. On Nov 22, 2007 1:46 PM, [EMAIL PROTECTED] wrote: Hello, I'm trying to switch my web service created using .NET to Axis2. At first, I've generated server-side skeleton codes from currently publishing WSDL by wsdl2java. Next, I've built .aar file using generated ant file and upload it to the server through Axis2 administration site. (Business logic was not implemented at that point, because I only wanted to make sure it works) On the administration page, the service looks available and activated. And I've made sure .aar contains WSDL file in META-INF directory. At last, accessing new WSDL causes the exception below: org.apache.axis2.AxisFault at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1148) at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1077) at org.apache.axis2.transport.http.ListingAgent.processListService (ListingAgent .java:280) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23 . jar.so) at javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23 . jar.so) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (catalina-5. 5.23.jar.soa01s4g.so) at org.apache.catalina.core.ApplicationFilterChain.doFilter(catalina-5.5 . 23.jar.soa01s4g.so) at org.apache.catalina.core.StandardWrapperValve.invoke( catalina-5.5.23.jar.soa 01s4g.so) at org.apache.catalina.core.StandardContextValve.invoke( catalina-5.5.23.jar.soa 01s4g.so) at org.apache.catalina.core.StandardHostValve.invoke(catalina-5.5.23.jar . soa01s4g.so) at org.apache.catalina.valves.ErrorReportValve.invoke( catalina-5.5.23.jar.soa01 s4g.so) at org.apache.catalina.core.StandardEngineValve.invoke( catalina-5.5.23.jar.soa0 1s4g.so) at org.apache.catalina.connector.CoyoteAdapter.service( catalina-5.5.23.jar.soa0 1s4g.so) at org.apache.coyote.http11.Http11Processor.process(tomcat-http-5.5.23.jar.so ) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(tomcat-http-5.5.23.jar.so) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket( tomcat-util-5.5.23. jar.so) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( tomcat-util-5.5. 23.jar.so) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (tomcat-util-5. 5.23.jar.so) at java.lang.Thread.run(libgcj.so.7rh) Caused by: java.lang.NullPointerException at org.apache.axiom.om.impl.util.OMSerializerUtil.generateSetPrefix (OMSerialize rUtil.java:560) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart (OMSerializ erUtil.java:273) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart (OMSerializ erUtil.java:172) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize (OMElementImpl. java:768) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize (OMElementImpl. java:756) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:383) at org.apache.axis2.util.XMLPrettyPrinter.prettify(XMLPrettyPrinter.java : 135) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1144) ...19 more What was wrong? I'm using Axis2 1.3, Tomcat 5.5.20 and JDK1.5.0_06. Thanks in advance Kengo Seki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
RE: Accessing WSDL causes NullPointerException (on .NET to Axis2 migration)
/actionMapping outputActionMappinghttp://adcentric.nazuki.jp/soap/v2/Analyze/Service.asmx /NazukiWebServiceSoap/RefreshSSGListResponse/outputActionMapping /operation /service /serviceGroup If there are any other necessary information, please point out. Thanks, Kengo -- From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 22, 2007 5:26 PM To: axis-user@ws.apache.org Subject: Re: Accessing WSDL causes NullPointerException (on .NET to Axis2 migration) Can you send the created aar so that We can check what's going on. Thanks, Keith. On Nov 22, 2007 1:46 PM, [EMAIL PROTECTED] wrote: Hello, I'm trying to switch my web service created using .NET to Axis2. At first, I've generated server-side skeleton codes from currently publishing WSDL by wsdl2java. Next, I've built .aar file using generated ant file and upload it to the server through Axis2 administration site. (Business logic was not implemented at that point, because I only wanted to make sure it works) On the administration page, the service looks available and activated. And I've made sure .aar contains WSDL file in META-INF directory. At last, accessing new WSDL causes the exception below: org.apache.axis2.AxisFault at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.description.AxisService.getWSDL (AxisService.java:1148) at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1077) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent .java:280) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23. jar.so) at javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23 . jar.so) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(catalina-5. 5.23.jar.soa01s4g.so) at org.apache.catalina.core.ApplicationFilterChain.doFilter (catalina-5.5. 23.jar.soa01s4g.so) at org.apache.catalina.core.StandardWrapperValve.invoke(catalina-5.5.23.jar.soa 01s4g.so) at org.apache.catalina.core.StandardContextValve.invoke (catalina-5.5.23.jar.soa 01s4g.so) at org.apache.catalina.core.StandardHostValve.invoke(catalina-5.5.23.jar. soa01s4g.so) at org.apache.catalina.valves.ErrorReportValve.invoke(catalina-5.5.23.jar.soa01 s4g.so) at org.apache.catalina.core.StandardEngineValve.invoke(catalina-5.5.23.jar.soa0 1s4g.so) at org.apache.catalina.connector.CoyoteAdapter.service(catalina-5.5.23.jar.soa0 1s4g.so) at org.apache.coyote.http11.Http11Processor.process(tomcat-http-5.5.23.jar.so) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(tomcat-http-5.5.23.jar.so) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(tomcat-util-5.5.23. jar.so) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (tomcat-util-5.5. 23.jar.so) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(tomcat-util-5. 5.23.jar.so ) at java.lang.Thread.run(libgcj.so.7rh) Caused by: java.lang.NullPointerException at org.apache.axiom.om.impl.util.OMSerializerUtil.generateSetPrefix(OMSerialize rUtil.java:560) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart (OMSerializ erUtil.java:273) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializ erUtil.java:172) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl. java:768) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl. java:756) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize (OMNodeImpl.java:383) at org.apache.axis2.util.XMLPrettyPrinter.prettify(XMLPrettyPrinter.java: 135) at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1144) ...19 more What was wrong? I'm using Axis2 1.3, Tomcat 5.5.20 and JDK1.5.0_06. Thanks in advance Kengo Seki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
RE: Accessing WSDL causes NullPointerException (on .NET to Axis2 migration)
Keith, Thanks a lot! The problem was solved. Adding parameter locked=false name=useOriginalwsdltrue/parameter parameter locked=false name=modifyUserWSDLPortAddresstrue/parameter to services.xml makes it work. Thanks, Kengo From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 22, 2007 7:53 PM To: axis-user@ws.apache.org Subject: Re: Accessing WSDL causes NullPointerException (on .NET to Axis2 migration) Hi, I used the WSDL you have given here and generated java code using wsdl2java with the following options -uri /home/keith/Desktop/test.wsdl -ss -sd -o /opt/test ran ant and deployed the aar that was created. I was able to get the WSDL as http://localhost:8080/axis2/services/NazukiWebService?wsdl2 and http://localhost:8080/axis2/services/NazukiWebService?wsdl2 Note that the services.xml has parameter name=useOriginalwsdltrue/parameter and it will serve the WSDL in the META-INF. If you remove this parameter or set it to false Axis2 will serve a generated WSDL. I used Axis2-1.3. Thanks, Keith. On Nov 22, 2007 3:08 PM, [EMAIL PROTECTED] wrote: Hello Keith, Thank you for your fast reply. Though I tried to send my aar file to the mailing list several times, my posts ware rejected with below SMTP error... 552 Message rejected as it is spam (body) So, I will describe my aar contents. At first, directory structure is like this: NazukiWebService.aar ├─jp │ └─nazuki │ ├─adcentric │ │ └─soap │ │ └─v2 │ │ └─analyze │ │ └─service_asmx │ │ AnalyzeType01$1.class │ │ AnalyzeType01$Factory.class │ │ AnalyzeType01.class │ │ AnalyzeType01Response$1.class │ │ AnalyzeType01Response$Factory.class │ │ AnalyzeType01Response.class │ │ AnalyzeType02$1.class │ │ AnalyzeType02$Factory.class │ │ AnalyzeType02.class │ │ AnalyzeType02Response$1.class │ │ AnalyzeType02Response$Factory.class │ │ AnalyzeType02Response.class │ │ AnalyzeType03$1.class │ │ AnalyzeType03$Factory.class │ │ AnalyzeType03.class │ │ AnalyzeType03Response$1.class │ │ AnalyzeType03Response$Factory.class │ │ AnalyzeType03Response.class │ │ AnalyzeType04$1.class │ │ AnalyzeType04$Factory.class │ │ AnalyzeType04.class │ │ AnalyzeType04Response$1.class │ │ AnalyzeType04Response$Factory.class │ │ AnalyzeType04Response.class │ │ ArrayOfAnyType$1.class │ │ ArrayOfAnyType$Factory.class │ │ ArrayOfAnyType.class │ │ ArrayOfCategory$1.class │ │ ArrayOfCategory$Factory.class │ │ ArrayOfCategory.class │ │ ArrayOfKeyword$1.class │ │ ArrayOfKeyword$Factory.class │ │ ArrayOfKeyword.class │ │ Category$1.class │ │ Category$Factory.class │ │ Category.class │ │ ExtensionMapper.class │ │ Keyword$1.class │ │ Keyword$Factory.class │ │ Keyword.class │ │ RefreshLicenceTable$1.class │ │ RefreshLicenceTable$Factory.class │ │ RefreshLicenceTable.class │ │ RefreshLicenceTableResponse$1.class │ │ RefreshLicenceTableResponse$Factory.class │ │ RefreshLicenceTableResponse.class │ │ RefreshSSGList$1.class │ │ RefreshSSGList$Factory.class │ │ RefreshSSGList.class │ │ RefreshSSGListResponse$1.class │ │ RefreshSSGListResponse$Factory.class │ │ RefreshSSGListResponse.class │ │ Type01Result$1.class │ │ Type01Result$Factory.class │ │ Type01Result.class │ │ Type02Result$1.class │ │ Type02Result$Factory.class │ │ Type02Result.class │ │ Type03Result$1.class │ │ Type03Result$Factory.class │ │ Type03Result.class
Axis to Axis2 migration doubt
In my axis deployment file I use following operation node to describe IN and OUT parameter of my method having signature as public short WMLS_GetFromStore(String WellTypeIn, String XMLIn,StringHolder XMLOut, StringHolder SuppMsgOut) operation name=WMLS_GetFromStore parameter name=TypeIn mode=IN/ parameter name=XMLIn mode=IN/ parameter name=XMLOut mode=OUT/ parameter name=SuppMsgOut mode=OUT/ /operation How to achieve same in Axis2? I can not able to find out way to define parameter as OUT type with AXIS2. could you please update me with way of achieving same with AXIS2? With Regards, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Outsourcing =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: Axis to Axis2 migration doubt
Well Axis2 does not support the holder concept , but you can easily achieve your goal - Just write a services.xml with specifying service class name - Do not worry about the operation name, Axis2 will automatically will creating the service analyzing the service impl class Thanks Deepal In my axis deployment file I use following operation node to describe IN and OUT parameter of my method having signature as public short WMLS_GetFromStore(String WellTypeIn, String XMLIn,StringHolder XMLOut, StringHolder SuppMsgOut) operation name=WMLS_GetFromStore parameter name=TypeIn mode=IN/ parameter name=XMLIn mode=IN/ parameter name=XMLOut mode=OUT/ parameter name=SuppMsgOut mode=OUT/ /operation How to achieve same in Axis2? I can not able to find out way to define parameter as OUT type with AXIS2. could you please update me with way of achieving same with AXIS2? With Regards, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis to Axis2 migration doubt
Hi Deepal, Could you give me one example source code or any URL from where I can get how to implement. Thanks, Deepak Deepal jayasinghe [EMAIL PROTECTED] 08/01/2007 04:49 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Axis to Axis2 migration doubt For that you have to create a Java bean (with the proprieties MLOut, SuppMsgOut ) and return that . Dear Deepal, When I am doing as directed by you, I get webservices which take all arguments as IN type only.But my requirement is that the 3rd and 4th argument XMLOut, SuppMsgOut should be return type(OUT mode). thanks Deepak *Deepal Jayasinghe [EMAIL PROTECTED]* 08/01/2007 03:59 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Axis to Axis2 migration doubt Well Axis2 does not support the holder concept , but you can easily achieve your goal - Just write a services.xml with specifying service class name - Do not worry about the operation name, Axis2 will automatically will creating the service analyzing the service impl class Thanks Deepal In my axis deployment file I use following operation node to describe IN and OUT parameter of my method having signature as public short WMLS_GetFromStore(String WellTypeIn, String XMLIn,StringHolder XMLOut, StringHolder SuppMsgOut) operation name=WMLS_GetFromStore parameter name=TypeIn mode=IN/ parameter name=XMLIn mode=IN/ parameter name=XMLOut mode=OUT/ parameter name=SuppMsgOut mode=OUT/ /operation How to achieve same in Axis2? I can not able to find out way to define parameter as OUT type with AXIS2. could you please update me with way of achieving same with AXIS2? With Regards, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT3DCE =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Thanks, Deepal . The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT3E26 =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: Axis to Axis2 migration doubt
Dear Deepal, When I am doing as directed by you, I get webservices which take all arguments as IN type only.But my requirement is that the 3rd and 4th argument XMLOut, SuppMsgOut should be return type(OUT mode). thanks Deepak Deepal Jayasinghe [EMAIL PROTECTED] 08/01/2007 03:59 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Axis to Axis2 migration doubt Well Axis2 does not support the holder concept , but you can easily achieve your goal - Just write a services.xml with specifying service class name - Do not worry about the operation name, Axis2 will automatically will creating the service analyzing the service impl class Thanks Deepal In my axis deployment file I use following operation node to describe IN and OUT parameter of my method having signature as public short WMLS_GetFromStore(String WellTypeIn, String XMLIn,StringHolder XMLOut, StringHolder SuppMsgOut) operation name=WMLS_GetFromStore parameter name=TypeIn mode=IN/ parameter name=XMLIn mode=IN/ parameter name=XMLOut mode=OUT/ parameter name=SuppMsgOut mode=OUT/ /operation How to achieve same in Axis2? I can not able to find out way to define parameter as OUT type with AXIS2. could you please update me with way of achieving same with AXIS2? With Regards, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT3DCE =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: Axis to Axis2 migration doubt
For that you have to create a Java bean (with the proprieties MLOut, SuppMsgOut ) and return that . Dear Deepal, When I am doing as directed by you, I get webservices which take all arguments as IN type only.But my requirement is that the 3rd and 4th argument XMLOut, SuppMsgOut should be return type(OUT mode). thanks Deepak *Deepal Jayasinghe [EMAIL PROTECTED]* 08/01/2007 03:59 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Axis to Axis2 migration doubt Well Axis2 does not support the holder concept , but you can easily achieve your goal - Just write a services.xml with specifying service class name - Do not worry about the operation name, Axis2 will automatically will creating the service analyzing the service impl class Thanks Deepal In my axis deployment file I use following operation node to describe IN and OUT parameter of my method having signature as public short WMLS_GetFromStore(String WellTypeIn, String XMLIn,StringHolder XMLOut, StringHolder SuppMsgOut) operation name=WMLS_GetFromStore parameter name=TypeIn mode=IN/ parameter name=XMLIn mode=IN/ parameter name=XMLOut mode=OUT/ parameter name=SuppMsgOut mode=OUT/ /operation How to achieve same in Axis2? I can not able to find out way to define parameter as OUT type with AXIS2. could you please update me with way of achieving same with AXIS2? With Regards, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT3DCE =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis to Axis2 migration doubt
[EMAIL PROTECTED] wrote: How to achieve same in Axis2? I can not able to find out way to define parameter as OUT type with AXIS2. could you please update me with way of achieving same with AXIS2? Hi Deepak! 2 comments here. First, the Web Services Application Server (WSAS) from WSO2, which you can find at http://wso2.com/products/wsas, contains an Axis2 custom deployer for Axis1 services. This allows you to drop your existing service classes (jars) and server-config.wsdd into the Axis2-based server, and get some of the benefits of Axis2 (Modules, etc) without having to rewrite your code. You might want to check that out as a first step. Second, I definitely think that the holder concept is of great value, and it would be nice if Axis2 supported it in the native ADB databinding. Could you perhaps file a JIRA about this? Thanks, --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the
following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say that
there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for Axis2?
TIA,
Ted Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the
following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say that
there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for Axis2?
TIA,
Ted Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So the
operation name did not have to match the method name. Is this still the
case? The reason I ask is because I am getting an Operation not found
exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for
Axis2?
TIA,
Ted Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.* to Axis2 Migration Question
Hi Ted
Can you show us the operation wsdl:operation name=get from your wsdl?
better yet could you display the entire wsdl for your service?
Thanks,
---
This e-mail message (including attachments, if any) is intended for the use of
the individual or entity to which it is addressed and may contain information
that is privileged, proprietary , confidential and exempt from disclosure. If
you are not the intended recipient, you are notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
- Original Message -
From: Ted Jones [EMAIL PROTECTED]
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 2:10 PM
Subject: RE: Axis 1.* to Axis2 Migration Question
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So the
operation name did not have to match the method name. Is this still the
case? The reason I ask is because I am getting an Operation not found
exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for
Axis2?
TIA,
Ted Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.* to Axis2 Migration Question
make sure you set the soap action correctly.
-- dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So the
operation name did not have to match the method name. Is this still the
case? The reason I ask is because I am getting an Operation not found
exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to convert,
the java:msg provider in Axis 1.3 specifies that the service class
contains the following method signature (among others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a message
provider and will default to an method based on it's signature? Does
the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and response
envelopes as arguments. What is the parallel implementation for
Axis2?
TIA,
Ted Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
My WSDL is pasted in below. This same WSDL works in Axis 1.3. When I execute the getBookCollection operation, it really accesses a method in the service that grabs the SOAP Action value and uses that to query against the database, gets a value and updates the SOAP response. This allows a dynamic behavior that does not require us to recreate the web service to accommodate a specific operation name. Here is a snippet from the userguide for Axis 1.2 that lead us down this path: snippet __ Message services Finally, we arrive at Message style services, which should be used when you want Axis to step back and let your code at the actual XML instead of turning it into Java objects. There are four valid signatures for your message-style service methods: public Element [] method(Element [] bodies); public SOAPBodyElement [] method (SOAPBodyElement [] bodies); public Document method(Document body); public void method(SOAPEnvelope req, SOAPEnvelope resp); The first two will pass your method arrays of either DOM Elements or SOAPBodyElements - the arrays will contain one element for each XML element inside the soap:body in the envelope. The third signature will pass you a DOM Document representing the soap:body, and expects the same in return. The fourth signature passes you two SOAPEnvelope objects representing the request and response messages. This is the signature to use if you need to look at or modify headers in your service method. Whatever you put into the response envelope will automatically be sent back to the caller when you return. Note that the response envelope may already contain headers which have been inserted by other Handlers. ___ /snippet It is the fourth signature that we were able to utilize. The method name was not the operation name, but an arbitrary value we defined. Here is my WSDL: definitions name=Books targetNamespace=http://com.test/BooksWebService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://com.test/BooksWebService; xmlns:schema1=http://test.com/books/input; xmlns:schema2=http://www.test.com/XMLSchema/DataSets/Books; types xsd:schema targetNamespace=http://com.test/BooksWebService; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xsd:import namespace=http://test.com/books/input; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service/B ooksWebService/BooksInput.xsd / xsd:import namespace=http://www.test.com/XMLSchema/DataSets/Books; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service/B ooksWebService/Books.xsd / /xsd:schema /types message name=Books_getBookCollection_getBookCollectionInput documentationInput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionInput element=schema1:getBookCollectionByTitleRequest / /message message name=Books_getBookCollection_getBookCollectionOutput documentationOutput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionOutput element=schema2:bookCollection / /message portType name=Books operation name=getBookCollection input message=tns:Books_getBookCollection_getBookCollectionInput / output message=tns:Books_getBookCollection_getBookCollectionOutput / /operation /portType binding name=Books type=tns:Books soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / operation name=getBookCollection soap:operation style=document soapAction=BooksWebService.Books.getBookCollection / input soap:body use=literal / /input output soap:body use=literal / /output /operation /binding service name=Books port name=Books binding=tns:Books soap:address location=http://testServer:8085/BooksWebService/services/service; / /port /service /definitions Thanks very much, Ted -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 1:38 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.* to Axis2 Migration Question Hi Ted Can you show us the operation wsdl:operation name=get from your wsdl? better yet could you display the entire wsdl for your service? Thanks, --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited
Re: Axis 1.* to Axis2 Migration Question
can you paste the autogenerated wsdl when you point your browse to ?wsdl thanks, dims On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote: My WSDL is pasted in below. This same WSDL works in Axis 1.3. When I execute the getBookCollection operation, it really accesses a method in the service that grabs the SOAP Action value and uses that to query against the database, gets a value and updates the SOAP response. This allows a dynamic behavior that does not require us to recreate the web service to accommodate a specific operation name. Here is a snippet from the userguide for Axis 1.2 that lead us down this path: snippet __ Message services Finally, we arrive at Message style services, which should be used when you want Axis to step back and let your code at the actual XML instead of turning it into Java objects. There are four valid signatures for your message-style service methods: public Element [] method(Element [] bodies); public SOAPBodyElement [] method (SOAPBodyElement [] bodies); public Document method(Document body); public void method(SOAPEnvelope req, SOAPEnvelope resp); The first two will pass your method arrays of either DOM Elements or SOAPBodyElements - the arrays will contain one element for each XML element inside the soap:body in the envelope. The third signature will pass you a DOM Document representing the soap:body, and expects the same in return. The fourth signature passes you two SOAPEnvelope objects representing the request and response messages. This is the signature to use if you need to look at or modify headers in your service method. Whatever you put into the response envelope will automatically be sent back to the caller when you return. Note that the response envelope may already contain headers which have been inserted by other Handlers. ___ /snippet It is the fourth signature that we were able to utilize. The method name was not the operation name, but an arbitrary value we defined. Here is my WSDL: definitions name=Books targetNamespace=http://com.test/BooksWebService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://com.test/BooksWebService; xmlns:schema1=http://test.com/books/input; xmlns:schema2=http://www.test.com/XMLSchema/DataSets/Books; types xsd:schema targetNamespace=http://com.test/BooksWebService; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xsd:import namespace=http://test.com/books/input; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service/B ooksWebService/BooksInput.xsd / xsd:import namespace=http://www.test.com/XMLSchema/DataSets/Books; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service/B ooksWebService/Books.xsd / /xsd:schema /types message name=Books_getBookCollection_getBookCollectionInput documentationInput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionInput element=schema1:getBookCollectionByTitleRequest / /message message name=Books_getBookCollection_getBookCollectionOutput documentationOutput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionOutput element=schema2:bookCollection / /message portType name=Books operation name=getBookCollection input message=tns:Books_getBookCollection_getBookCollectionInput / output message=tns:Books_getBookCollection_getBookCollectionOutput / /operation /portType binding name=Books type=tns:Books soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / operation name=getBookCollection soap:operation style=document soapAction=BooksWebService.Books.getBookCollection / input soap:body use=literal / /input output soap:body use=literal / /output /operation /binding service name=Books port name=Books binding=tns:Books soap:address location=http://testServer:8085/BooksWebService/services/service; / /port /service /definitions Thanks very much, Ted -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 1:38 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.* to Axis2 Migration Question Hi Ted Can you show us the operation wsdl:operation name=get from your wsdl? better yet could you display the entire wsdl for your service? Thanks, --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you
RE: Axis 1.* to Axis2 Migration Question
The soap action is set. Is this value being used to determine which
operation to execute? Is there a way to force it to pick the method
specified in the service.xml that uses the OMElement
methodName(OMElement element) signature?
Thanks,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 1:50 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
make sure you set the soap action correctly.
-- dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So
the operation name did not have to match the method name. Is this
still the case? The reason I ask is because I am getting an Operation
not found exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to
convert, the java:msg provider in Axis 1.3 specifies that the
service class contains the following method signature (among
others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the
request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a
message provider and will default to an method based on it's
signature? Does the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the
following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className
value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and
response envelopes as arguments. What is the parallel
implementation for
Axis2?
TIA,
Ted Jones
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.* to Axis2 Migration Question
Yes, if you look at the autogenerated wsdl, you can see which soap
action to set for which operation.
http://wso2.org/library/176
-- dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
The soap action is set. Is this value being used to determine which
operation to execute? Is there a way to force it to pick the method
specified in the service.xml that uses the OMElement
methodName(OMElement element) signature?
Thanks,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 1:50 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
make sure you set the soap action correctly.
-- dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
Thanks for the response dims. The Axis 1.* implementation is such that
it does not matter what the method name is, as long as the signature
matches one if the expected method signatures. If the method name was
specified in the allowableMethods property, it would be executed. So
the operation name did not have to match the method name. Is this
still the case? The reason I ask is because I am getting an Operation
not found exception.
Thanks for your help,
Ted
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 14, 2006 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom
public OMElement nameOfMethod(OMElement element)
thanks,
dims
On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote:
To be more specific as to what Axis 1.3 logic I am trying to
convert, the java:msg provider in Axis 1.3 specifies that the
service class contains the following method signature (among
others):
public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req,
org.apache.axis.message.SOAPEnvelope resp)
throws Exception { ... }
This has worked well for us by allowing us to interrogate the
request,
execute our business logic, and return the results in the SOAP
response.
Is there an equivalent solution in Axis2?
TIA,
Ted
-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say
that there is no parallel Axis2 form of a service that uses a
message provider and will default to an method based on it's
signature? Does the operation need to be specified now?
Thanks
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 2:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.* to Axis2 Migration Question
This is a good place to start:
http://ws.apache.org/axis2/1_1/migration.html
HTH,
Robert
On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote:
I have a web service in Axis 1.3 that is defined using the
following
deployment descriptor:
service name=myservice provider=java:MSG
parameter name=allowedMethods value=executeMyService/
parameter name=className
value=com.soap.service.MyWebService/
/service
The method (executeMyService) accepts the soap request and
response envelopes as arguments. What is the parallel
implementation for
Axis2?
TIA,
Ted Jones
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers
RE: Axis 1.* to Axis2 Migration Question
Hmmm... I get this when trying to get to the Axis2 generated WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Here is my service.xml for the deployed service: service name=service description Test Web Service /description parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/paramete r parameter name=allowedMethods locked=falseexecuteDataservice/parameter operation name=executeDataservice messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service FYI - The WSDL is generated dynamically from a servlet, it is not in the META-INF directory. Thanks, Ted -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 2:41 PM To: axis-user@ws.apache.org Cc: Martin Gainty Subject: Re: Axis 1.* to Axis2 Migration Question can you paste the autogenerated wsdl when you point your browse to ?wsdl thanks, dims On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote: My WSDL is pasted in below. This same WSDL works in Axis 1.3. When I execute the getBookCollection operation, it really accesses a method in the service that grabs the SOAP Action value and uses that to query against the database, gets a value and updates the SOAP response. This allows a dynamic behavior that does not require us to recreate the web service to accommodate a specific operation name. Here is a snippet from the userguide for Axis 1.2 that lead us down this path: snippet __ Message services Finally, we arrive at Message style services, which should be used when you want Axis to step back and let your code at the actual XML instead of turning it into Java objects. There are four valid signatures for your message-style service methods: public Element [] method(Element [] bodies); public SOAPBodyElement [] method (SOAPBodyElement [] bodies); public Document method(Document body); public void method(SOAPEnvelope req, SOAPEnvelope resp); The first two will pass your method arrays of either DOM Elements or SOAPBodyElements - the arrays will contain one element for each XML element inside the soap:body in the envelope. The third signature will pass you a DOM Document representing the soap:body, and expects the same in return. The fourth signature passes you two SOAPEnvelope objects representing the request and response messages. This is the signature to use if you need to look at or modify headers in your service method. Whatever you put into the response envelope will automatically be sent back to the caller when you return. Note that the response envelope may already contain headers which have been inserted by other Handlers. ___ /snippet It is the fourth signature that we were able to utilize. The method name was not the operation name, but an arbitrary value we defined. Here is my WSDL: definitions name=Books targetNamespace=http://com.test/BooksWebService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://com.test/BooksWebService; xmlns:schema1=http://test.com/books/input; xmlns:schema2=http://www.test.com/XMLSchema/DataSets/Books; types xsd:schema targetNamespace=http://com.test/BooksWebService; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xsd:import namespace=http://test.com/books/input; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service /B ooksWebService/BooksInput.xsd / xsd:import namespace=http://www.test.com/XMLSchema/DataSets/Books; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service /B ooksWebService/Books.xsd / /xsd:schema /types message name=Books_getBookCollection_getBookCollectionInput documentationInput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionInput element=schema1:getBookCollectionByTitleRequest / /message message name=Books_getBookCollection_getBookCollectionOutput documentationOutput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionOutput element=schema2:bookCollection / /message portType name=Books operation name=getBookCollection input message
Re: Axis 1.* to Axis2 Migration Question
ah. i forgot about that. then set the soap action to the name of the method (also read up the article i sent in my prev email) thanks, dims On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote: Hmmm... I get this when trying to get to the Axis2 generated WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Here is my service.xml for the deployed service: service name=service description Test Web Service /description parameter name=ServiceClass locked=falsecom.test.soap.lds.service.DataServiceWebService/paramete r parameter name=allowedMethods locked=falseexecuteDataservice/parameter operation name=executeDataservice messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service FYI - The WSDL is generated dynamically from a servlet, it is not in the META-INF directory. Thanks, Ted -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 2:41 PM To: axis-user@ws.apache.org Cc: Martin Gainty Subject: Re: Axis 1.* to Axis2 Migration Question can you paste the autogenerated wsdl when you point your browse to ?wsdl thanks, dims On 12/14/06, Ted Jones [EMAIL PROTECTED] wrote: My WSDL is pasted in below. This same WSDL works in Axis 1.3. When I execute the getBookCollection operation, it really accesses a method in the service that grabs the SOAP Action value and uses that to query against the database, gets a value and updates the SOAP response. This allows a dynamic behavior that does not require us to recreate the web service to accommodate a specific operation name. Here is a snippet from the userguide for Axis 1.2 that lead us down this path: snippet __ Message services Finally, we arrive at Message style services, which should be used when you want Axis to step back and let your code at the actual XML instead of turning it into Java objects. There are four valid signatures for your message-style service methods: public Element [] method(Element [] bodies); public SOAPBodyElement [] method (SOAPBodyElement [] bodies); public Document method(Document body); public void method(SOAPEnvelope req, SOAPEnvelope resp); The first two will pass your method arrays of either DOM Elements or SOAPBodyElements - the arrays will contain one element for each XML element inside the soap:body in the envelope. The third signature will pass you a DOM Document representing the soap:body, and expects the same in return. The fourth signature passes you two SOAPEnvelope objects representing the request and response messages. This is the signature to use if you need to look at or modify headers in your service method. Whatever you put into the response envelope will automatically be sent back to the caller when you return. Note that the response envelope may already contain headers which have been inserted by other Handlers. ___ /snippet It is the fourth signature that we were able to utilize. The method name was not the operation name, but an arbitrary value we defined. Here is my WSDL: definitions name=Books targetNamespace=http://com.test/BooksWebService; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://com.test/BooksWebService; xmlns:schema1=http://test.com/books/input; xmlns:schema2=http://www.test.com/XMLSchema/DataSets/Books; types xsd:schema targetNamespace=http://com.test/BooksWebService; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xsd:import namespace=http://test.com/books/input; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service /B ooksWebService/BooksInput.xsd / xsd:import namespace=http://www.test.com/XMLSchema/DataSets/Books; schemaLocation=http://testServer:8085/BooksWebService/servlet/Service /B ooksWebService/Books.xsd / /xsd:schema /types message name=Books_getBookCollection_getBookCollectionInput documentationInput message for operation Books/getBookCollection./documentation part name=Books_getBookCollection_getBookCollectionInput element=schema1:getBookCollectionByTitleRequest / /message message name=Books_getBookCollection_getBookCollectionOutput documentationOutput message for operation Books/getBookCollection./documentation part name
Axis 1.* to Axis2 Migration Question
I have a web service in Axis 1.3 that is defined using the following deployment descriptor: service name=myservice provider=java:MSG parameter name=allowedMethods value=executeMyService/ parameter name=className value=com.soap.service.MyWebService/ /service The method (executeMyService) accepts the soap request and response envelopes as arguments. What is the parallel implementation for Axis2? TIA, Ted Jones
Re: Axis 1.* to Axis2 Migration Question
This is a good place to start: http://ws.apache.org/axis2/1_1/migration.html HTH, Robert On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote: I have a web service in Axis 1.3 that is defined using the following deployment descriptor: service name=myservice provider=java:MSG parameter name=allowedMethods value=executeMyService/ parameter name=className value=com.soap.service.MyWebService/ /service The method (executeMyService) accepts the soap request and response envelopes as arguments. What is the parallel implementation for Axis2? TIA, Ted Jones - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis 1.* to Axis2 Migration Question
So, after looking through the documentation, is it accurate to say that there is no parallel Axis2 form of a service that uses a message provider and will default to an method based on it's signature? Does the operation need to be specified now? Thanks -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 13, 2006 2:42 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.* to Axis2 Migration Question This is a good place to start: http://ws.apache.org/axis2/1_1/migration.html HTH, Robert On 12/13/06, Ted Jones [EMAIL PROTECTED] wrote: I have a web service in Axis 1.3 that is defined using the following deployment descriptor: service name=myservice provider=java:MSG parameter name=allowedMethods value=executeMyService/ parameter name=className value=com.soap.service.MyWebService/ /service The method (executeMyService) accepts the soap request and response envelopes as arguments. What is the parallel implementation for Axis2? TIA, Ted Jones - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis1-axis2 migration of serializers
Hi We are using lot of custom serializers (for each custom type in our application) in our axis1 based webservices fasade. Is it possible to use it still with axis2 (after migration) ??? The code of these serliazers is mostly all the code of the application (since the service class only delegates invocations to our application server). So if it is problematic to reuse such seralizers, perhaps it would be easier to just rewrite this part it in actual supported way ( axiom?? - I do not now exactly which way/approach is now suggested for such things ;) ) ?? Thanks for any help/hints bartek -- ** ConSol* Consulting Solutions Software Poland ul. Bronowicka 10A, 30-084 Kraków tel. +48 (012) 6231525 [EMAIL PROTECTED] http://www.consol.de ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Migration
Hi,
I want to migrate to Axis 2 but it causes several problems for instance the
ant task and Handler classes:
1.)
target name=wsdl2java
codegen wsdlfilename=${local.wsdl}
serverside=true
packagename=de.test
/codegen
/target
causes the following error message:
javax.xml.stream.FactoryConfigurationError: Provider
com.bea.xml.stream.MXParserFactory not found
2.)
What's equivalent to this from Axis 1.4:
axis-wsdl2java url=${local.wsdl}
output=${src}
testcase=true
deployscope=session
serverSide=true
skeletonDeploy=true
noimports=false
mapping
namespace=http://www.domainname.de/appname/;
package=de.domainname.appname.webservice
/
/axis-wsdl2java
I don't understand how I can use the new namespacetopackages attribute (the
old mapping is not more allowed?!)?
3.)
What is the code for the following Handler code snippet?
String userID = msgContext.getUsername();
String password = msgContext.getPassword();
String remoteIP = msgContext.getStrProp(Constants.MC_REMOTE_ADDR);
Thank you very much for your help!
Regards,
Ralph
Re: [Axis2] Migration
There is a migration guide that covers both Handlers and databinding:
http://ws.apache.org/axis2/1_0/migration.html
I think most if not all of your questions are answered there. Anything that's left, just follow up and maybe we can help.
One thing you'll need to solve is your classpath, as you'll need a
reference to all the jars under the std distro lib directory. There is
a full tutorial on ant in the codegen guide:
http://ws.apache.org/axis2/tools/1_0/CodegenToolReference.html
HTH,
Robert
http://www.braziloutsource.com/
On 5/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,I want to migrate to Axis 2 but it causes several problems for instance theant task and Handler classes:1.)target name=wsdl2javacodegen
wsdlfilename=${local.wsdl}
serverside=true
packagename=de.test/codegen/targetcauses the following error message:javax.xml.stream.FactoryConfigurationError: Providercom.bea.xml.stream.MXParserFactory
not found2.)What's equivalent to this from Axis 1.4:axis-wsdl2java
url="">output=${src}testcase=truedeployscope=session
serverSide=trueskeletonDeploy=truenoimports=falsemapping
namespace=http://www.domainname.de/appname/
package=de.domainname.appname.webservice//axis-wsdl2javaI don't understand how I can use the new namespacetopackages attribute (theold mapping is not more allowed?!)?
3.)What is the code for the following Handler code snippet?String userID = msgContext.getUsername();String password = msgContext.getPassword();String remoteIP = msgContext.getStrProp(Constants.MC_REMOTE_ADDR
);Thank you very much for your help!Regards,Ralph
Re: [Axis2] Migration
Hi Ralph,
1. We've found that the Ant task needs the jars inside the ant lib
folder so the easiest solution will be to copy the axis2 lib into the
ant lib directory. do an ant -diagnostics and see whether ant has
picked up the classes just to be sure :)
2. Our ant task is somewhat primitive so it does not allow the
mappings to be nested as in the old ant task. As for the attribute
please include the string namespace=package seperated by commas.
example
codegen namespacetopackages=urn:myNamespace=org.me,http://myns=org.myns; /
We do understand that this needs to be improved. We'll soon improve
the ant task, to the user friendly level of the Axis1 ant task
3. oops ! we do not support getting the username,password through the
messagecontext directly. In the servlet case you'll need to access the
Constants.Configuration.TRANSPORT_IN_URL property in the message
context to get the request URL
HTH
Ajith
On 5/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
I want to migrate to Axis 2 but it causes several problems for instance the
ant task and Handler classes:
1.)
target name=wsdl2java
codegen wsdlfilename=${local.wsdl}
serverside=true
packagename=de.test
/codegen
/target
causes the following error message:
javax.xml.stream.FactoryConfigurationError: Provider
com.bea.xml.stream.MXParserFactory not found
2.)
What's equivalent to this from Axis 1.4:
axis-wsdl2java url=${local.wsdl}
output=${src}
testcase=true
deployscope=session
serverSide=true
skeletonDeploy=true
noimports=false
mapping
namespace=http://www.domainname.de/appname/;
package=de.domainname.appname.webservice
/
/axis-wsdl2java
I don't understand how I can use the new namespacetopackages attribute (the
old mapping is not more allowed?!)?
3.)
What is the code for the following Handler code snippet?
String userID = msgContext.getUsername();
String password = msgContext.getPassword();
String remoteIP = msgContext.getStrProp(Constants.MC_REMOTE_ADDR);
Thank you very much for your help!
Regards,
Ralph
--
Ajith Ranabahu
AW: [Axis2] Migration
Thanks four your answer.
I have read the articles
again but it solves not my problems.
Von: robert lazarski
[mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. Mai 2006
15:35
An: axis-user@ws.apache.org
Betreff: Re: [Axis2] Migration
There is a migration
guide that covers both Handlers and databinding:
http://ws.apache.org/axis2/1_0/migration.html
I think most if not all of your questions are answered there. Anything that's
left, just follow up and maybe we can help.
One thing you'll need to solve is your classpath, as you'll need a reference to
all the jars under the std distro lib directory. There is a full tutorial on
ant in the codegen guide:
http://ws.apache.org/axis2/tools/1_0/CodegenToolReference.html
HTH,
Robert
http://www.braziloutsource.com/
On 5/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
I want to migrate to Axis 2 but it causes several problems for instance the
ant task and Handler classes:
1.)
target
name=wsdl2java
codegen
wsdlfilename=${local.wsdl}
serverside=true
packagename=de.test
/codegen
/target
causes the following error message:
javax.xml.stream.FactoryConfigurationError: Provider
com.bea.xml.stream.MXParserFactory not found
2.)
What's equivalent to this from Axis 1.4:
axis-wsdl2java
url="">
output=${src}
testcase=true
deployscope=session
serverSide=true
skeletonDeploy=true
noimports=false
mapping
namespace=http://www.domainname.de/appname/
package=de.domainname.appname.webservice
/
/axis-wsdl2java
I don't understand how I can use the new namespacetopackages attribute (the
old mapping is not more allowed?!)?
3.)
What is the code for the following Handler code snippet?
String userID = msgContext.getUsername();
String password = msgContext.getPassword();
String remoteIP = msgContext.getStrProp(Constants.MC_REMOTE_ADDR
);
Thank you very much for your help!
Regards,
Ralph
AW: [Axis2] Migration
Hi, your answer helped me a lot. Thanks!! 1. We've found that the Ant task needs the jars inside the ant lib folder so the easiest solution will be to copy the axis2 lib into the ant lib directory. do an ant -diagnostics and see whether ant has picked up the classes just to be sure :) I use Eclipse, so I had added the libraries in Preferences | Ant | Runtime | Classpath and now it works. I don't understand why this is now necessary because in Axis 1 this was not needed. 2. Our ant task is somewhat primitive so it does not allow the mappings to be nested as in the old ant task. As for the attribute please include the string namespace=package seperated by commas. example codegen namespacetopackages=urn:myNamespace=org.me,http://myns=org.myns; / This works for me. We do understand that this needs to be improved. We'll soon improve the ant task, to the user friendly level of the Axis1 ant task Do you know approximately the next release date? 3. oops ! we do not support getting the username,password through the messagecontext directly. In the servlet case you'll need to access the Constants.Configuration.TRANSPORT_IN_URL property in the message context to get the request URL I can't follow you in this point. Do you mean it is not possible to get username, password and IP address in an Axis 2 Handler class. In Axis 1.2.4 I used this to implement logging and authentication. I really need this feature. Regards, Ralph
Re: [Axis2] Migration 0.93-0.94
Thanks a lot!
Am Freitag 03 März 2006 14:48 schrieb Deepal Jayasinghe:
private MessageContext makeCall(MessageContext requestContext, String
action) throws AxisFault {
ServiceClient client;
MessageContext result = null;
try {
client = new ServiceClient();
Options option = new Options();
option.setTo(targetEPR);
option.setAction(action);
option.setTransportInProtocol(Constants.TRANSPORT_HTTP);
OperationClient opClient =
client.createClient(ServiceClient.ANON_OUT_IN_OP);
opClient.addMessageContext(requestContext);
opClient.execute(true);
return
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
} catch (AxisFault e) {
if (debug) e.printStackTrace();
}
return result;
}
///
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(soap/
axis2/config,null);
try {
msgContext = new MessageContext(configContext);
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
Note : If you want to use your axis2.xml then you have to put that into
conf directory inside the repository or you can give absoloute path for
axis2.xml as second paramter (null in this case) to
createConfigurationContextFromFileSystem
Filipp Akinfiev wrote:
hi all,
please help me to migrate from 0.93 to 0.94 following code:
===
private MessageContext makeCall(MessageContext requestContext, String
action) {
Call call;
MessageContext result = null;
try {
call = new Call();
call.setTo(targetEPR);
call.setTransportInfo(Constants.TRANSPORT_HTTP,
Constants.TRANSPORT_HTTP,
false);
QName opName = new QName(urn:XMLWSIntf-IXMLWS,
action);
OperationDescription opdesc = new
OperationDescription(opName); //Blocking invocation
result = (MessageContext)
call.invokeBlocking(opdesc ,requestContext);
} catch (AxisFault e) {
if(debug)e.printStackTrace();
}
return result;
}
===
ConfigurationContextFactory fac = new
ConfigurationContextFactory(); ConfigurationContext configContext =
fac.buildClientConfigurationContext(soap/axis2/config);
try {
msgContext = new MessageContext(configContext);
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
===
thanks in advance!
[Axis2] Migration 0.93-0.94
hi all,
please help me to migrate from 0.93 to 0.94 following code:
===
private MessageContext makeCall(MessageContext requestContext, String
action) {
Call call;
MessageContext result = null;
try {
call = new Call();
call.setTo(targetEPR);
call.setTransportInfo(Constants.TRANSPORT_HTTP,
Constants.TRANSPORT_HTTP,
false);
QName opName = new QName(urn:XMLWSIntf-IXMLWS,
action);
OperationDescription opdesc = new OperationDescription(opName);
//Blocking invocation
result = (MessageContext)
call.invokeBlocking(opdesc ,requestContext);
} catch (AxisFault e) {
if(debug)e.printStackTrace();
}
return result;
}
===
ConfigurationContextFactory fac = new ConfigurationContextFactory();
ConfigurationContext configContext =
fac.buildClientConfigurationContext(soap/axis2/config);
try {
msgContext = new MessageContext(configContext);
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
===
thanks in advance!
Re: [Axis2] Migration 0.93-0.94
private MessageContext makeCall(MessageContext requestContext, String
action) throws AxisFault {
ServiceClient client;
MessageContext result = null;
try {
client = new ServiceClient();
Options option = new Options();
option.setTo(targetEPR);
option.setAction(action);
option.setTransportInProtocol(Constants.TRANSPORT_HTTP);
OperationClient opClient =
client.createClient(ServiceClient.ANON_OUT_IN_OP);
opClient.addMessageContext(requestContext);
opClient.execute(true);
return
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
} catch (AxisFault e) {
if (debug) e.printStackTrace();
}
return result;
}
///
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(soap/axis2/config,null);
try {
msgContext = new MessageContext(configContext);
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
Note : If you want to use your axis2.xml then you have to put that into
conf directory inside the repository or you can give absoloute path for
axis2.xml as second paramter (null in this case) to
createConfigurationContextFromFileSystem
Filipp Akinfiev wrote:
hi all,
please help me to migrate from 0.93 to 0.94 following code:
===
private MessageContext makeCall(MessageContext requestContext, String
action) {
Call call;
MessageContext result = null;
try {
call = new Call();
call.setTo(targetEPR);
call.setTransportInfo(Constants.TRANSPORT_HTTP,
Constants.TRANSPORT_HTTP,
false);
QName opName = new QName(urn:XMLWSIntf-IXMLWS,
action);
OperationDescription opdesc = new OperationDescription(opName);
//Blocking invocation
result = (MessageContext)
call.invokeBlocking(opdesc ,requestContext);
} catch (AxisFault e) {
if(debug)e.printStackTrace();
}
return result;
}
===
ConfigurationContextFactory fac = new ConfigurationContextFactory();
ConfigurationContext configContext =
fac.buildClientConfigurationContext(soap/axis2/config);
try {
msgContext = new MessageContext(configContext);
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
===
thanks in advance!
--
Thanks,
Deepal
~Future is Open~
Re: AXIS 1.x to AXIS2 Migration Roadmap
hmm, I didn't have a time to look in to the doc. But anyway, I created a JIRA for this, so that we won't miss it. Any volunteers for writing this ? This should be written by someone who is in both Axis 1.x and Axis2 ( and loves to work on both of the systems :) ) Venkat Reddy wrote: Eran, That page seem to have good content for comparing between 1.x v2.0, useful for new users. But the existing users of Axis 1.x would need migration plan that has sections to show how to migrate handler code, deployment code, clients, and service implementations. I think we need to provide elaborate documentation on this, for the benefit of 1.x users. - venkat On 9/15/05, Eran Chinthaka [EMAIL PROTECTED] wrote: http://ws.apache.org/axis2/migration.html Kr wrote: Hi All, I have fair experience with AXIS 1.x and now planning to switch to AXIS2. Does anybody have AXIS 1.x to AXIS2 migration roadmap. What are the various differences between the two based on parameters like performance, ease-of-use, ws-security, support for various java-xml-data-binding-frameworks etc. When should be look for migrating our exisiting web services providers and consumer built using AXIS 1.X to AXIS2. Any issues that we can forecast ? Please suggest ? Thanks Regards, Kr.
AXIS 1.x to AXIS2 Migration Roadmap
Hi All, I have fair experience with AXIS 1.x and now planning to switch to AXIS2. Does anybody have AXIS 1.x to AXIS2 migration roadmap. What are the various differences between the two based on parameters like performance, ease-of-use, ws-security, support for various java-xml-data-binding-frameworks etc. When should be look for migrating our exisiting web services providers and consumer built using AXIS 1.X to AXIS2. Any issues that we can forecast ? Please suggest ? Thanks Regards, Kr.
Re: AXIS 1.x to AXIS2 Migration Roadmap
http://ws.apache.org/axis2/migration.html Kr wrote: Hi All, I have fair experience with AXIS 1.x and now planning to switch to AXIS2. Does anybody have AXIS 1.x to AXIS2 migration roadmap. What are the various differences between the two based on parameters like performance, ease-of-use, ws-security, support for various java-xml-data-binding-frameworks etc. When should be look for migrating our exisiting web services providers and consumer built using AXIS 1.X to AXIS2. Any issues that we can forecast ? Please suggest ? Thanks Regards, Kr.
