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 D P <de...@gmail.com> on 2007/03/21 17:00:48 UTC
Axis 2 v1.1.1: disabling auto generated WSDL file
Hello all,
When a client queries the service wsdl at http://../../serviceName?wsdl, I
would like the service to return the wsdl which I packaged in the .aar file,
_not_ an auto generated wsdl. I came across a possible solution here:
http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
1. It appears though there are some issues with the solution. Does anyone
know if this works for sure?
2. After implementing the solution in my services.xml file, i noticed 2
things:
a.) i've refactored out some schema into an xsd file, and import it to
multiple wsdls. A copy of the xsd file is packaged with each wsdl and the
code to import the xsd uses schemaLocation="foo.xsd". But when I look at
the wsdl file at http://../../serviceName?wsdl, the schemaLocation element
value is now schemaLocation="serviceName?xsd=xsd0". Why is this happening?
b) When I look at the wsdl file at http://../../serviceName?wsdl, i notice
that wsdl:portType/wsdl:operation/wsdl:input and
wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
original wsdl I packaged with the .aar does not. Why is this happening?
Any feedback would be appreciated.
Re: Axis 2 v1.1.1: disabling auto generated WSDL file
Posted by D P <de...@gmail.com>.
Sorry everyone, I discovered I made a mistake with the services.xml file.
Please consider my question resolved.
On 3/22/07, D P <de...@gmail.com> wrote:
>
> Thanks for all your replies.
>
> Krishna: I followed your directions, and changed the case of the
> parameter. However, I'm still observing the items I noted in #2 of my
> original email. Also, I noticed that Axis2 has also removed the "parts"
> attribute in my soap12:body and soap:body elements.
>
> Amila: I'm sorry, but I don't quite follow your response. Are you saying
> that the issue in general is known, or the specific observations I made in
> #2 of my email is known?
>
>
> On 3/22/07, Amila Suriarachchi <am...@gmail.com> wrote:
> >
> >
> >
> > On 3/21/07, D P < developerperson@gmail.com> wrote:
> > >
> > > Hello all,
> > > When a client queries the service wsdl at
> > > http://../../serviceName?wsdl, I would like the service to return the wsdl
> > > which I packaged in the .aar file, _not_ an auto generated wsdl. I came
> > > across a possible solution here:
> > > http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
> > > 1. It appears though there are some issues with the solution. Does
> > > anyone know if this works for sure?
> > >
> > > 2. After implementing the solution in my services.xml file, i noticed
> > > 2 things:
> > > a.) i've refactored out some schema into an xsd file, and import it to
> > > multiple wsdls. A copy of the xsd file is packaged with each wsdl and the
> > > code to import the xsd uses schemaLocation=" foo.xsd". But when I
> > > look at the wsdl file at http://../../serviceName?wsdl, the schemaLocation
> > > element value is now schemaLocation="serviceName?xsd=xsd0". Why is this
> > > happening?
> > >
> > > b) When I look at the wsdl file at http://../../serviceName?wsdl, i
> > > notice that wsdl:portType/wsdl:operation/wsdl:input and
> > > wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
> > > original wsdl I packaged with the .aar does not. Why is this happening?
> >
> >
> > I think this is a known issue.
> > In Axis2 we use the WSDL11ToAxisServiceBuilder to build the Axis
> > Service from the wsdl file. The first step it does is it process the
> > imports.
> > i.e . It iterates through all the imported wsdls and put all the
> > imports to the service wsdl. Then when serializing the wsdl4jDefinition it
> > serializes this changed wsdl4j object. So it contains both original imports
> > (I removed this recently) and the imported elements.
> > please log a jira.
> >
> > Any feedback would be appreciated.
> > >
> >
> >
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
>
>
>
Re: Axis 2 v1.1.1: disabling auto generated WSDL file
Posted by D P <de...@gmail.com>.
Thanks for all your replies.
Krishna: I followed your directions, and changed the case of the parameter.
However, I'm still observing the items I noted in #2 of my original email.
Also, I noticed that Axis2 has also removed the "parts" attribute in my
soap12:body and soap:body elements.
Amila: I'm sorry, but I don't quite follow your response. Are you saying
that the issue in general is known, or the specific observations I made in
#2 of my email is known?
On 3/22/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
>
>
> On 3/21/07, D P <de...@gmail.com> wrote:
> >
> > Hello all,
> > When a client queries the service wsdl at http://../../serviceName?wsdl,
> > I would like the service to return the wsdl which I packaged in the .aar
> > file, _not_ an auto generated wsdl. I came across a possible solution here:
> > http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
> > 1. It appears though there are some issues with the solution. Does
> > anyone know if this works for sure?
> >
> > 2. After implementing the solution in my services.xml file, i noticed 2
> > things:
> > a.) i've refactored out some schema into an xsd file, and import it to
> > multiple wsdls. A copy of the xsd file is packaged with each wsdl and the
> > code to import the xsd uses schemaLocation=" foo.xsd". But when I look
> > at the wsdl file at http://../../serviceName?wsdl, the schemaLocation
> > element value is now schemaLocation="serviceName?xsd=xsd0". Why is this
> > happening?
> >
> > b) When I look at the wsdl file at http://../../serviceName?wsdl, i
> > notice that wsdl:portType/wsdl:operation/wsdl:input and
> > wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
> > original wsdl I packaged with the .aar does not. Why is this happening?
>
>
> I think this is a known issue.
> In Axis2 we use the WSDL11ToAxisServiceBuilder to build the Axis Service
> from the wsdl file. The first step it does is it process the imports.
> i.e. It iterates through all the imported wsdls and put all the imports
> to the service wsdl. Then when serializing the wsdl4jDefinition it
> serializes this changed wsdl4j object. So it contains both original imports
> (I removed this recently) and the imported elements.
> please log a jira.
>
> Any feedback would be appreciated.
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
Re: Axis 2 v1.1.1: disabling auto generated WSDL file
Posted by Amila Suriarachchi <am...@gmail.com>.
On 3/21/07, D P <de...@gmail.com> wrote:
>
> Hello all,
> When a client queries the service wsdl at http://../../serviceName?wsdl, I
> would like the service to return the wsdl which I packaged in the .aar file,
> _not_ an auto generated wsdl. I came across a possible solution here:
> http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
> 1. It appears though there are some issues with the solution. Does
> anyone know if this works for sure?
>
> 2. After implementing the solution in my services.xml file, i noticed 2
> things:
> a.) i've refactored out some schema into an xsd file, and import it to
> multiple wsdls. A copy of the xsd file is packaged with each wsdl and the
> code to import the xsd uses schemaLocation=" foo.xsd". But when I look at
> the wsdl file at http://../../serviceName?wsdl, the schemaLocation element
> value is now schemaLocation="serviceName?xsd=xsd0". Why is this happening?
>
> b) When I look at the wsdl file at http://../../serviceName?wsdl, i notice
> that wsdl:portType/wsdl:operation/wsdl:input and
> wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
> original wsdl I packaged with the .aar does not. Why is this happening?
I think this is a known issue.
In Axis2 we use the WSDL11ToAxisServiceBuilder to build the Axis Service
from the wsdl file. The first step it does is it process the imports.
i.e. It iterates through all the imported wsdls and put all the imports to
the service wsdl. Then when serializing the wsdl4jDefinition it serializes
this changed wsdl4j object. So it contains both original imports (I removed
this recently) and the imported elements.
please log a jira.
Any feedback would be appreciated.
>
--
Amila Suriarachchi,
WSO2 Inc.
RE: Axis 2 v1.1.1: disabling auto generated WSDL file
Posted by Vibhor_Sharma <vs...@gryphonnetworks.com>.
Does it really work?
I tried setting the param in my service.xml file and still see the one
generated by axis engine? I do not see my own WSDL.
<serviceGroup>
<service name="CertifyChannel">
<module ref="logging"/>
<module ref="rampart"/>
<parameter name="useOriginalWSDL">true</parameter>
Is there some other place I have to substitute this value??
-Vibhor
________________________________
From: D P [mailto:developerperson@gmail.com]
Sent: Wednesday, March 21, 2007 12:01 PM
To: axis-user@ws.apache.org
Subject: Axis 2 v1.1.1: disabling auto generated WSDL file
Hello all,
When a client queries the service wsdl at http://../../serviceName?wsdl,
I would like the service to return the wsdl which I packaged in the .aar
file, _not_ an auto generated wsdl. I came across a possible solution
here: http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
1. It appears though there are some issues with the solution. Does
anyone know if this works for sure?
2. After implementing the solution in my services.xml file, i noticed 2
things:
a.) i've refactored out some schema into an xsd file, and import it to
multiple wsdls. A copy of the xsd file is packaged with each wsdl and
the code to import the xsd uses schemaLocation=" foo.xsd". But when I
look at the wsdl file at http://../../serviceName?wsdl, the
schemaLocation element value is now
schemaLocation="serviceName?xsd=xsd0". Why is this happening?
b) When I look at the wsdl file at http://../../serviceName?wsdl, i
notice that wsdl:portType/wsdl:operation/wsdl:input and
wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
original wsdl I packaged with the .aar does not. Why is this happening?
Any feedback would be appreciated.