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 sjtirtha <sj...@gmail.com> on 2007/08/16 09:41:53 UTC
TypeMapping in Axis
Hi,
I use Eclipse WTP to generate a java skeleton for a Web
Service implementation based on the existing WSDL.
After creating the java skeleton, I realized that Axis generated a new WSDL
that is possibly in run time by the servlet generated.
But this generated WSDL is not the same one with the existing WSDL that I
used to generate the java skeleton.
For example, Axis changes the following datatype from a simpleType into
complexType. And when I see into the deploy.wsdd, axis map "char8" into a
simple String without restriction. It should cause a incompatibility between
the the WS Client that is built based on the existing WSDL and the WS
implementation that uses the new generated WSDL.
How can I set Axis to use always the existing WSDL and not using the
generated WSDL. The problem is the WS client communicates with some other WS
implementation that use this existing WSDL.
<xsd:simpleType name="char8" >
<xsd:restriction base="xsd:string" >
<xsd:maxLength value= "8"/>
</xsd:restriction>
</xsd:simpleType >
to
<complexType name="char8">
<simpleContent>
<extension/>
</simpleContent>
</complexType>
Regards,
Steve
Re: TypeMapping in Axis
Posted by sjtirtha <sj...@gmail.com>.
Hi,
thanks for the infos. I can set axis using the original wsdl. Now I'm
testing the integration.
regards,
steve
On 8/16/07, Upul Godage <up...@gmail.com> wrote:
>
> You can find more details here.
>
> http://ws.apache.org/axis/java/reference.html#DeploymentWSDDReference
> Search for: *wsdlFile
>
> *Upul
> *
> *
> On 8/16/07, Upul Godage <up...@gmail.com> wrote:
> >
> > Hi,
> >
> > useOriginalwsdl... thing is for "Axis2."
> >
> > You are using "Axis". That is where wsdds are used.
> >
> > Try putting <wsdlFile> entry below in your deploy.wsdd. The wsdl
> > location should be in the classpath I think.
> >
> > <service ...>
> > ...
> > <wsdlFile>class/path/original.wsdl</wsdlFile>
> > </service>
> >
> >
> >
> > Upul
> >
> >
> > On 8/16/07, sjtirtha <sjtirtha@gmail.com > wrote:
> > >
> > > Hi,
> > >
> > > I put <parameter locked="false"
> > > name="useOriginalwsdl">true</parameter> in server-config.wsdd and
> > > deploy.wsdd.
> > > But it doesn't work either. I don't find the service.xml in my project
> > > folder.
> > >
> > > The parameter should do what I want to, but it doesn't work. And how
> > > can Axis find the original wsdl file ?
> > >
> > > Steve
> > >
> > >
> > > On 8/16/07, Upul Godage <upulg.dev@gmail.com > wrote:
> > > >
> > > > Hi,
> > > >
> > > > in Axis 1 in wsdd (wsdl in classpath I think)
> > > > <service ...>
> > > > ...
> > > > <wsdlFile> original.wsdl</wsdlFile>
> > > > </service>
> > > >
> > > > in Axis2 in services.xml (wsdl in META-INF)
> > > > <service ...>
> > > > ...
> > > > <parameter locked="false" name="useOriginalwsdl">true</parameter>
> > > > </service>
> > > >
> > > > Hope this helps.
> > > >
> > > > Upul
> > > >
> > > > On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I use Eclipse WTP to generate a java skeleton for a Web
> > > > > Service implementation based on the existing WSDL.
> > > > > After creating the java skeleton, I realized that Axis generated a
> > > > > new WSDL that is possibly in run time by the servlet generated.
> > > > > But this generated WSDL is not the same one with the existing WSDL
> > > > > that I used to generate the java skeleton.
> > > > >
> > > > > For example, Axis changes the following datatype from a simpleType
> > > > > into complexType. And when I see into the deploy.wsdd, axis map
> > > > > "char8" into a simple String without restriction. It should cause a
> > > > > incompatibility between the the WS Client that is built based on the
> > > > > existing WSDL and the WS implementation that uses the new generated WSDL.
> > > > >
> > > > > How can I set Axis to use always the existing WSDL and not using
> > > > > the generated WSDL. The problem is the WS client communicates with some
> > > > > other WS implementation that use this existing WSDL.
> > > > >
> > > > > <xsd:simpleType name="char8" >
> > > > > <xsd:restriction base="xsd:string" >
> > > > > <xsd:maxLength value= "8"/>
> > > > > </xsd:restriction>
> > > > > </xsd:simpleType >
> > > > > to
> > > > >
> > > > > <complexType name="char8">
> > > > > <simpleContent>
> > > > > <extension/>
> > > > > </simpleContent>
> > > > > </complexType>
> > > > >
> > > > > Regards,
> > > > >
> > > > > Steve
> > > > >
> > > >
> > > >
> > >
> >
>
Re: TypeMapping in Axis
Posted by Upul Godage <up...@gmail.com>.
You can find more details here.
http://ws.apache.org/axis/java/reference.html#DeploymentWSDDReference
Search for: *wsdlFile
*Upul
*
*
On 8/16/07, Upul Godage <up...@gmail.com> wrote:
>
> Hi,
>
> useOriginalwsdl... thing is for "Axis2."
>
> You are using "Axis". That is where wsdds are used.
>
> Try putting <wsdlFile> entry below in your deploy.wsdd. The wsdl location
> should be in the classpath I think.
>
> <service ...>
> ...
> <wsdlFile>class/path/original.wsdl</wsdlFile>
> </service>
>
>
>
> Upul
>
>
> On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
> >
> > Hi,
> >
> > I put <parameter locked="false" name="useOriginalwsdl">true</parameter>
> > in server-config.wsdd and deploy.wsdd.
> > But it doesn't work either. I don't find the service.xml in my project
> > folder.
> >
> > The parameter should do what I want to, but it doesn't work. And how can
> > Axis find the original wsdl file ?
> >
> > Steve
> >
> >
> > On 8/16/07, Upul Godage <upulg.dev@gmail.com > wrote:
> > >
> > > Hi,
> > >
> > > in Axis 1 in wsdd (wsdl in classpath I think)
> > > <service ...>
> > > ...
> > > <wsdlFile> original.wsdl</wsdlFile>
> > > </service>
> > >
> > > in Axis2 in services.xml (wsdl in META-INF)
> > > <service ...>
> > > ...
> > > <parameter locked="false" name="useOriginalwsdl">true</parameter>
> > > </service>
> > >
> > > Hope this helps.
> > >
> > > Upul
> > >
> > > On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I use Eclipse WTP to generate a java skeleton for a Web
> > > > Service implementation based on the existing WSDL.
> > > > After creating the java skeleton, I realized that Axis generated a
> > > > new WSDL that is possibly in run time by the servlet generated.
> > > > But this generated WSDL is not the same one with the existing WSDL
> > > > that I used to generate the java skeleton.
> > > >
> > > > For example, Axis changes the following datatype from a simpleType
> > > > into complexType. And when I see into the deploy.wsdd, axis map
> > > > "char8" into a simple String without restriction. It should cause a
> > > > incompatibility between the the WS Client that is built based on the
> > > > existing WSDL and the WS implementation that uses the new generated WSDL.
> > > >
> > > > How can I set Axis to use always the existing WSDL and not using the
> > > > generated WSDL. The problem is the WS client communicates with some other WS
> > > > implementation that use this existing WSDL.
> > > >
> > > > <xsd:simpleType name="char8" >
> > > > <xsd:restriction base="xsd:string" >
> > > > <xsd:maxLength value= "8"/>
> > > > </xsd:restriction>
> > > > </xsd:simpleType >
> > > > to
> > > >
> > > > <complexType name="char8">
> > > > <simpleContent>
> > > > <extension/>
> > > > </simpleContent>
> > > > </complexType>
> > > >
> > > > Regards,
> > > >
> > > > Steve
> > > >
> > >
> > >
> >
>
Re: TypeMapping in Axis
Posted by Upul Godage <up...@gmail.com>.
Hi,
useOriginalwsdl... thing is for "Axis2."
You are using "Axis". That is where wsdds are used.
Try putting <wsdlFile> entry below in your deploy.wsdd. The wsdl location
should be in the classpath I think.
<service ...>
...
<wsdlFile>class/path/original.wsdl</wsdlFile>
</service>
Upul
On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
>
> Hi,
>
> I put <parameter locked="false" name="useOriginalwsdl">true</parameter> in
> server-config.wsdd and deploy.wsdd.
> But it doesn't work either. I don't find the service.xml in my project
> folder.
>
> The parameter should do what I want to, but it doesn't work. And how can
> Axis find the original wsdl file ?
>
> Steve
>
>
> On 8/16/07, Upul Godage <up...@gmail.com> wrote:
> >
> > Hi,
> >
> > in Axis 1 in wsdd (wsdl in classpath I think)
> > <service ...>
> > ...
> > <wsdlFile> original.wsdl</wsdlFile>
> > </service>
> >
> > in Axis2 in services.xml (wsdl in META-INF)
> > <service ...>
> > ...
> > <parameter locked="false" name="useOriginalwsdl">true</parameter>
> > </service>
> >
> > Hope this helps.
> >
> > Upul
> >
> > On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > I use Eclipse WTP to generate a java skeleton for a Web
> > > Service implementation based on the existing WSDL.
> > > After creating the java skeleton, I realized that Axis generated a new
> > > WSDL that is possibly in run time by the servlet generated.
> > > But this generated WSDL is not the same one with the existing WSDL
> > > that I used to generate the java skeleton.
> > >
> > > For example, Axis changes the following datatype from a simpleType
> > > into complexType. And when I see into the deploy.wsdd, axis map
> > > "char8" into a simple String without restriction. It should cause a
> > > incompatibility between the the WS Client that is built based on the
> > > existing WSDL and the WS implementation that uses the new generated WSDL.
> > >
> > > How can I set Axis to use always the existing WSDL and not using the
> > > generated WSDL. The problem is the WS client communicates with some other WS
> > > implementation that use this existing WSDL.
> > >
> > > <xsd:simpleType name="char8" >
> > > <xsd:restriction base="xsd:string" >
> > > <xsd:maxLength value= "8"/>
> > > </xsd:restriction>
> > > </xsd:simpleType >
> > > to
> > >
> > > <complexType name="char8">
> > > <simpleContent>
> > > <extension/>
> > > </simpleContent>
> > > </complexType>
> > >
> > > Regards,
> > >
> > > Steve
> > >
> >
> >
>
Re: TypeMapping in Axis
Posted by sjtirtha <sj...@gmail.com>.
Hi,
I put <parameter locked="false" name="useOriginalwsdl">true</parameter> in
server-config.wsdd and deploy.wsdd.
But it doesn't work either. I don't find the service.xml in my project
folder.
The parameter should do what I want to, but it doesn't work. And how can
Axis find the original wsdl file ?
Steve
On 8/16/07, Upul Godage <up...@gmail.com> wrote:
>
> Hi,
>
> in Axis 1 in wsdd (wsdl in classpath I think)
> <service ...>
> ...
> <wsdlFile>original.wsdl</wsdlFile>
> </service>
>
> in Axis2 in services.xml (wsdl in META-INF)
> <service ...>
> ...
> <parameter locked="false" name="useOriginalwsdl">true</parameter>
> </service>
>
> Hope this helps.
>
> Upul
>
> On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
> >
> > Hi,
> >
> > I use Eclipse WTP to generate a java skeleton for a Web
> > Service implementation based on the existing WSDL.
> > After creating the java skeleton, I realized that Axis generated a new
> > WSDL that is possibly in run time by the servlet generated.
> > But this generated WSDL is not the same one with the existing WSDL that
> > I used to generate the java skeleton.
> >
> > For example, Axis changes the following datatype from a simpleType into
> > complexType. And when I see into the deploy.wsdd, axis map "char8" into
> > a simple String without restriction. It should cause a incompatibility
> > between the the WS Client that is built based on the existing WSDL and the
> > WS implementation that uses the new generated WSDL.
> >
> > How can I set Axis to use always the existing WSDL and not using the
> > generated WSDL. The problem is the WS client communicates with some other WS
> > implementation that use this existing WSDL.
> >
> > <xsd:simpleType name="char8" >
> > <xsd:restriction base="xsd:string" >
> > <xsd:maxLength value= "8"/>
> > </xsd:restriction>
> > </xsd:simpleType >
> > to
> >
> > <complexType name="char8">
> > <simpleContent>
> > <extension/>
> > </simpleContent>
> > </complexType>
> >
> > Regards,
> >
> > Steve
> >
>
>
Re: TypeMapping in Axis
Posted by Upul Godage <up...@gmail.com>.
Hi,
in Axis 1 in wsdd (wsdl in classpath I think)
<service ...>
...
<wsdlFile>original.wsdl</wsdlFile>
</service>
in Axis2 in services.xml (wsdl in META-INF)
<service ...>
...
<parameter locked="false" name="useOriginalwsdl">true</parameter>
</service>
Hope this helps.
Upul
On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
>
> Hi,
>
> I use Eclipse WTP to generate a java skeleton for a Web
> Service implementation based on the existing WSDL.
> After creating the java skeleton, I realized that Axis generated a new
> WSDL that is possibly in run time by the servlet generated.
> But this generated WSDL is not the same one with the existing WSDL that I
> used to generate the java skeleton.
>
> For example, Axis changes the following datatype from a simpleType into
> complexType. And when I see into the deploy.wsdd, axis map "char8" into a
> simple String without restriction. It should cause a incompatibility between
> the the WS Client that is built based on the existing WSDL and the WS
> implementation that uses the new generated WSDL.
>
> How can I set Axis to use always the existing WSDL and not using the
> generated WSDL. The problem is the WS client communicates with some other WS
> implementation that use this existing WSDL.
>
> <xsd:simpleType name="char8" >
> <xsd:restriction base="xsd:string" >
> <xsd:maxLength value= "8"/>
> </xsd:restriction>
> </xsd:simpleType >
> to
>
> <complexType name="char8">
> <simpleContent>
> <extension/>
> </simpleContent>
> </complexType>
>
> Regards,
>
> Steve
>
Re: TypeMapping in Axis
Posted by sjtirtha <sj...@gmail.com>.
I look into Eclipse plugin, I use Axis 1.3. And I use WST 1.5.4 and JST
1.5.4.
I think the <wsdlFile> works in my case. I just assumed that the integration
problem between my WS implementation and WS client was because the different
between original WSDL and generated WSDL. That's why I asked how to use the
original WSDL. But I found out that that is not the problem.
Regards,
Steve
On 8/17/07, Lahiru Sandakith <sa...@gmail.com> wrote:
>
> Hi,
> Please tell us which version of the Axis/Axis2 runtime that you are using
> inside Eclipse WTP WS Framwork, plus what is the WTP verison that this issue
> raised. I believe you are using Axis as the runtime not Axis2 in side WTP.
> AFAIK in Axis
>
> you need to edit the deploy.wsdd.
>
> <wsdlFile>your.wsdl</wsdlFile>
>
> Then restarting the WS runtime should work.
>
> Thanks
>
> Lahiru
>
> On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
> >
> > Hi,
> >
> > I use Eclipse WTP to generate a java skeleton for a Web
> > Service implementation based on the existing WSDL.
> > After creating the java skeleton, I realized that Axis generated a new
> > WSDL that is possibly in run time by the servlet generated.
> > But this generated WSDL is not the same one with the existing WSDL that
> > I used to generate the java skeleton.
> >
> > For example, Axis changes the following datatype from a simpleType into
> > complexType. And when I see into the deploy.wsdd, axis map "char8" into
> > a simple String without restriction. It should cause a incompatibility
> > between the the WS Client that is built based on the existing WSDL and the
> > WS implementation that uses the new generated WSDL.
> >
> > How can I set Axis to use always the existing WSDL and not using the
> > generated WSDL. The problem is the WS client communicates with some other WS
> > implementation that use this existing WSDL.
> >
> > <xsd:simpleType name="char8" >
> > <xsd:restriction base="xsd:string" >
> > <xsd:maxLength value= "8"/>
> > </xsd:restriction>
> > </xsd:simpleType >
> > to
> >
> > <complexType name="char8">
> > <simpleContent>
> > <extension/>
> > </simpleContent>
> > </complexType>
> >
> > Regards,
> >
> > Steve
> >
>
>
>
> --
> Thanks
> Lahiru Sandakith
>
> http://sandakith.wordpress.com/
> GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: TypeMapping in Axis
Posted by Lahiru Sandakith <sa...@gmail.com>.
Hi,
Please tell us which version of the Axis/Axis2 runtime that you are using
inside Eclipse WTP WS Framwork, plus what is the WTP verison that this issue
raised. I believe you are using Axis as the runtime not Axis2 in side WTP.
AFAIK in Axis
you need to edit the deploy.wsdd.
<wsdlFile>your.wsdl</wsdlFile>
Then restarting the WS runtime should work.
Thanks
Lahiru
On 8/16/07, sjtirtha <sj...@gmail.com> wrote:
>
> Hi,
>
> I use Eclipse WTP to generate a java skeleton for a Web
> Service implementation based on the existing WSDL.
> After creating the java skeleton, I realized that Axis generated a new
> WSDL that is possibly in run time by the servlet generated.
> But this generated WSDL is not the same one with the existing WSDL that I
> used to generate the java skeleton.
>
> For example, Axis changes the following datatype from a simpleType into
> complexType. And when I see into the deploy.wsdd, axis map "char8" into a
> simple String without restriction. It should cause a incompatibility between
> the the WS Client that is built based on the existing WSDL and the WS
> implementation that uses the new generated WSDL.
>
> How can I set Axis to use always the existing WSDL and not using the
> generated WSDL. The problem is the WS client communicates with some other WS
> implementation that use this existing WSDL.
>
> <xsd:simpleType name="char8" >
> <xsd:restriction base="xsd:string" >
> <xsd:maxLength value= "8"/>
> </xsd:restriction>
> </xsd:simpleType >
> to
>
> <complexType name="char8">
> <simpleContent>
> <extension/>
> </simpleContent>
> </complexType>
>
> Regards,
>
> Steve
>
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F