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 JERIL NADAR <je...@gmail.com> on 2014/12/05 13:33:58 UTC
Axis 1.4.2 to Axis2 1.6 Migration
Hi,
I got your mail id from your Axis migration page :
http://axis.apache.org/axis2/java/core/docs/migration.html
I have one quick question for you. Your help would be highly appreciated.
Our project receives Webservice response from an external system.
We have webservice clients written to send the request and receive the
response/fault message accordingly.
Till recently they were using Axis 1.4.2 but now are planning to move to
Axis2 1.6.
They are ready with the Webservice part and have shared their WSDL file.
The operations remains the same but now they have moved from RPC style to
Document style.
*So my question is if we continue to remain with the older client (axis
1.4.2) will it make any difference?*
*If yes, what changes would be required from our side for the client code?*
Any help would be useful.
--
Thanks,
Jeril Nadar
John 3:16
Re: Axis 1.4.2 to Axis2 1.6 Migration
Posted by JERIL NADAR <je...@gmail.com>.
thanks very much Josef and Tomas.
Let me try this out.
Would reach you if I need further help.
On Fri, Dec 5, 2014 at 8:10 PM, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> What I would do in your situation is:
>
> Why not paly that migration in small steps and learn.
>
> Take one of the CL/SV examples and build it to use RPC Style.
>
> Then if CL/SV are running, change the server side only to Document Style
> and look what happens.
>
> Also very informational and nearly a must have with this two examples is
> the use of a TCP monitor or
>
> Wireshark in-between CL/SV to see the wire protocol.
>
>
>
> Josef
>
>
>
>
>
> *From:* JERIL NADAR [mailto:jeril842002@gmail.com]
> *Sent:* Freitag, 5. Dezember 2014 13:34
> *To:* java-user@axis.apache.org
> *Subject:* Axis 1.4.2 to Axis2 1.6 Migration
>
>
>
> Hi,
>
> I got your mail id from your Axis migration page :
> http://axis.apache.org/axis2/java/core/docs/migration.html
>
> I have one quick question for you. Your help would be highly appreciated.
>
> Our project receives Webservice response from an external system.
> We have webservice clients written to send the request and receive the
> response/fault message accordingly.
> Till recently they were using Axis 1.4.2 but now are planning to move to
> Axis2 1.6.
> They are ready with the Webservice part and have shared their WSDL file.
> The operations remains the same but now they have moved from RPC style to
> Document style.
>
>
>
> *So my question is if we continue to remain with the older client (axis
> 1.4.2) will it make any difference?*
>
> *If yes, what changes would be required from our side for the client code?*
>
>
>
> Any help would be useful.
>
>
>
> --
>
> Thanks,
> Jeril Nadar
> John 3:16
>
>
>
--
Thanks,
Jeril Nadar
John 3:16
RE: Axis 1.4.2 to Axis2 1.6 Migration
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
What I would do in your situation is:
Why not paly that migration in small steps and learn.
Take one of the CL/SV examples and build it to use RPC Style.
Then if CL/SV are running, change the server side only to Document Style and look what happens.
Also very informational and nearly a must have with this two examples is the use of a TCP monitor or
Wireshark in-between CL/SV to see the wire protocol.
Josef
From: JERIL NADAR [mailto:jeril842002@gmail.com]
Sent: Freitag, 5. Dezember 2014 13:34
To: java-user@axis.apache.org
Subject: Axis 1.4.2 to Axis2 1.6 Migration
Hi,
I got your mail id from your Axis migration page : http://axis.apache.org/axis2/java/core/docs/migration.html
I have one quick question for you. Your help would be highly appreciated.
Our project receives Webservice response from an external system.
We have webservice clients written to send the request and receive the response/fault message accordingly.
Till recently they were using Axis 1.4.2 but now are planning to move to Axis2 1.6.
They are ready with the Webservice part and have shared their WSDL file.
The operations remains the same but now they have moved from RPC style to Document style.
So my question is if we continue to remain with the older client (axis 1.4.2) will it make any difference?
If yes, what changes would be required from our side for the client code?
Any help would be useful.
--
Thanks,
Jeril Nadar
John 3:16
Re: Axis 1.4.2 to Axis2 1.6 Migration
Posted by JERIL NADAR <je...@gmail.com>.
thanks very much.
I will check this out.
On Fri, Dec 5, 2014 at 6:30 PM, satyapriya sahoo <sahoo.satyapriya@gmail.com
> wrote:
> JERIL,
>
> In RPC you can pass whole XML as a STRING, BUT in Document style you
> need to pass as an Object not a String.
> Consider the bellow example.
>
> XML:
> <emp>
> <emp-no>1</emp-no>
> <emp-name>aaa</emp-name>
> </emp>
>
> In RPC you can pass the whole xml as a String, but in document style U
> need to Reccompile your wsdl. There you will get so many bean classes.
> Like here May be one EMP class. and in the EMP class there will be 2
> setters() method present where it set the value for emp-no and emp-name.
> Here you can't pass as string, you need to pass the EMP class Object.
>
> NOTE:
> *******
> For changing from RPC to Document Style, You have to Recompile the WSDL.
>
> Hope this information help you to proceed further.
>
> Thanks,
> Satya
>
> On Fri, Dec 5, 2014 at 6:04 PM, JERIL NADAR <je...@gmail.com> wrote:
>
>>
>> Hi,
>> I got your mail id from your Axis migration page :
>> http://axis.apache.org/axis2/java/core/docs/migration.html
>> I have one quick question for you. Your help would be highly appreciated.
>> Our project receives Webservice response from an external system.
>> We have webservice clients written to send the request and receive the
>> response/fault message accordingly.
>> Till recently they were using Axis 1.4.2 but now are planning to move to
>> Axis2 1.6.
>> They are ready with the Webservice part and have shared their WSDL file.
>> The operations remains the same but now they have moved from RPC style to
>> Document style.
>>
>> *So my question is if we continue to remain with the older client (axis
>> 1.4.2) will it make any difference?*
>> *If yes, what changes would be required from our side for the client
>> code?*
>>
>> Any help would be useful.
>>
>>
>>
>> --
>> Thanks,
>> Jeril Nadar
>> John 3:16
>>
>>
>>
>>
>
--
Thanks,
Jeril Nadar
John 3:16
Re: Axis 1.4.2 to Axis2 1.6 Migration
Posted by satyapriya sahoo <sa...@gmail.com>.
JERIL,
In RPC you can pass whole XML as a STRING, BUT in Document style you need
to pass as an Object not a String.
Consider the bellow example.
XML:
<emp>
<emp-no>1</emp-no>
<emp-name>aaa</emp-name>
</emp>
In RPC you can pass the whole xml as a String, but in document style U need
to Reccompile your wsdl. There you will get so many bean classes.
Like here May be one EMP class. and in the EMP class there will be 2
setters() method present where it set the value for emp-no and emp-name.
Here you can't pass as string, you need to pass the EMP class Object.
NOTE:
*******
For changing from RPC to Document Style, You have to Recompile the WSDL.
Hope this information help you to proceed further.
Thanks,
Satya
On Fri, Dec 5, 2014 at 6:04 PM, JERIL NADAR <je...@gmail.com> wrote:
>
> Hi,
> I got your mail id from your Axis migration page :
> http://axis.apache.org/axis2/java/core/docs/migration.html
> I have one quick question for you. Your help would be highly appreciated.
> Our project receives Webservice response from an external system.
> We have webservice clients written to send the request and receive the
> response/fault message accordingly.
> Till recently they were using Axis 1.4.2 but now are planning to move to
> Axis2 1.6.
> They are ready with the Webservice part and have shared their WSDL file.
> The operations remains the same but now they have moved from RPC style to
> Document style.
>
> *So my question is if we continue to remain with the older client (axis
> 1.4.2) will it make any difference?*
> *If yes, what changes would be required from our side for the client code?*
>
> Any help would be useful.
>
>
>
> --
> Thanks,
> Jeril Nadar
> John 3:16
>
>
>
>
Axis 1.4.2 to Axis2 1.6 Migration
Posted by JERIL NADAR <je...@gmail.com>.
Hi,
I got your mail id from your Axis migration page :
http://axis.apache.org/axis2/java/core/docs/migration.html
I have one quick question for you. Your help would be highly appreciated.
Our project receives Webservice response from an external system.
We have webservice clients written to send the request and receive the
response/fault message accordingly.
Till recently they were using Axis 1.4.2 but now are planning to move to
Axis2 1.6.
They are ready with the Webservice part and have shared their WSDL file.
The operations remains the same but now they have moved from RPC style to
Document style.
*So my question is if we continue to remain with the older client (axis
1.4.2) will it make any difference?*
*If yes, what changes would be required from our side for the client code?*
Any help would be useful.
--
Thanks,
Jeril Nadar
John 3:16
Re: Axis 1.4.2 to Axis2 1.6 Migration
Posted by Tomas Andersen <ta...@morecom.no>.
The change from RPC to Document style is not so big. Axis2 also supports RPC, but by building the clientstub code with xmlbeans you can use Document mode.
RPC style:
WebRequest webRequest = WebRequest.newInstance()
webRequest.set()
Document style:
WebRequestDocument webRequest = WebRequestDocument.Factory.newInstance()
webRequest.set()
Almost all subelements are equal so if you have decoupled the build of all the subtypes you can reuse the old code.
You need to use Factory.newInstance() instead of newInstance for all types.
Also the Document style is easier when working with simpletypes, instead of making converter methods for basic types to/from native javatypes
You can use set(string), set(int) on the simpletype elements.. Like this:
RPC style;
In old style you had to make converter methods from native types
textType.setTextType(TextType type)
private TextType generateTextTypeFromString(String input) {
TextType textType = TextType.newInstance();
textType.setTextType(inndata);
return textType;
}
Document style:
In document style you can use String, Integer etc directly.
accessType.setConfigName(String type);
I don't know if this was a good answer, but I recently converted to Document style because ADB RPC style did not handle empty tags on this form : <tag/>
With the document model I both get an easier way to write the client and it handles responses better.
Regards,
Tomas Andersen
From: JERIL NADAR <je...@gmail.com>>
Reply-To: "java-user@axis.apache.org<ma...@axis.apache.org>" <ja...@axis.apache.org>>
Date: Friday 5 December 2014 13:33
To: "java-user@axis.apache.org<ma...@axis.apache.org>" <ja...@axis.apache.org>>
Subject: Axis 1.4.2 to Axis2 1.6 Migration
Hi,
I got your mail id from your Axis migration page : http://axis.apache.org/axis2/java/core/docs/migration.html
I have one quick question for you. Your help would be highly appreciated.
Our project receives Webservice response from an external system.
We have webservice clients written to send the request and receive the response/fault message accordingly.
Till recently they were using Axis 1.4.2 but now are planning to move to Axis2 1.6.
They are ready with the Webservice part and have shared their WSDL file.
The operations remains the same but now they have moved from RPC style to Document style.
So my question is if we continue to remain with the older client (axis 1.4.2) will it make any difference?
If yes, what changes would be required from our side for the client code?
Any help would be useful.
--
Thanks,
Jeril Nadar
John 3:16