You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by "Ockleford Paul (NHS CONNECTING FOR HEALTH)" <pa...@nhs.net> on 2012/11/30 17:08:42 UTC

FW: Moving from axis 1.x to axis 2

Hi,

I need to migrate from axis 1.3 to axis 2 within an existing large web application which also exposes web service functionality. I have been reading through the documentation and also followed this tutorial: http://www.developer.com/services/article.php/10928_3777111_2/Embedding-Apache-Axis2-into-Existing-Applications.htm.

I am having no luck even getting a wsdl to generate for my existing services. If I browse to the wsdl address I get the following error: javax.servlet.ServletException: File "/axis2-web/listSingleService.jsp" not found

Is it really the case that I MUST have the axis web app installed? I really don't want to have to do this and with axis 1 I just dropped the jar files into my web app and wrote the wsdd file and that's it, my wsdl generated and my RPC services worked fine.

My second question is do I have to package my services code into a jar\aar file? All my source code already sits in my web application in WEB-INF/lib/classes/... Is there any way to just point axis 2 to the existing source instead of having to package this up? My build process already distributes these files into my web app and this worked absolutely fine with axis 1.

Finally, if does anybody have a link to a decent migration process? The one on the axis website is pretty sparse really and doesn't actually tell me what I need to do.

Thanks,

Paul

********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients
NHSmail provides an email address for your career in the NHS and can be accessed anywhere

********************************************************************************************************************

AW: Moving from axis 1.x to axis 2

Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.

Axis2 is a total new architecture/development from scratch (years ago) than the previously still existing axis.

Axis2 is a servlet.

It doesn't help much to compare the two axis version.

Browsing as you said only works if Axis2.war is deployed/installed correct as a web app (servlet), because the missing JSP comes with this axis2.war.

I do not understand why you see this message if you have deployed axis2.war into your AS webapp directory.

At least you should see the version service coming as an example with axis2.war.

Using axis2.war é all, you can well go for a JAXWS web services (java with annotations) and then either drop a war into AS/webapp, drop an yourservice.aar into AS/axis2/WEB-INF/services OR drop a jar into AS/webapp/axis2/WEB-INF/servicejars. So with axis2 your service code is packaged intoyourservice.aar file.

aar file extension stands for axis2 archive file.

yourservice.aar files are moved to AS/wepapp/axis2/WEB-INF/services directory where they are detected by the running axis2 engine, unpacked and installed properly.

Very much like war files are moved to the AS/webapp directory where they are detected and deployed by the running AS deployment engine.

Regarding a migration: I don't have a clean way to recommend except if you have the WSDL from axis, you can try to generate your service skeleton and stubs using axis2 tools such as wsdl2java.

Maybe you have a look as well for java2wsdl, but that depends on your approach, wsdl first or code first.

It also depends about what further axis2 modules and features you intend to engage; i.e. Rampart for signing and encryption.

Also, Axis2 supports jaxws nicely, and that comes to play when you intend to generate client stubs using tools like MS Visual Studio and .NET WCF with VB.NET or C#.NET

Josef

Von: Ockleford Paul (NHS CONNECTING FOR HEALTH) [mailto:paul.ockleford@nhs.net]
Gesendet: Freitag, 30. November 2012 17:09
An: java-user@axis.apache.org
Betreff: FW: Moving from axis 1.x to axis 2

Hi,

Finally, if does anybody have a link to a decent migration process? The one on the axis website is pretty sparse really and doesn't actually tell me what I need to do.

Thanks,

Paul

********************************************************************************************************************

Thank you for your co-operation.

********************************************************************************************************************