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 Rainer Menzner <rm...@L1id.com> on 2006/11/02 16:39:56 UTC

[AXIS2] Can I mix up my axis2 system / WSDL handling? Please help.

Hi,

unil a few hours ago, I had a trivial service for which axis2
auto-generated a WSDL. This does no longer work for some reason.
I constantly keep the Message:

<error>
<description>Unable 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>


My service *uses* rpc receivers, my services.xml looks like

<service>
<description>
First service, which echoes a string passed in.
</description>
<parameter name="ServiceClass">my.ws.EchoService</parameter>
<operation name="myEcho">
<messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
</operation>
</service>

I also have an example of a handwritten wsdl which worked (according to 
the issue and
the solutions brought up by Matthew Hannay recently. If I query this 
service, it also does
not show any wsdl, neither my handwritten nor an auto-generated one. It 
insists on the error
message above.

Can someone give me a hint about this? I'm not aware that I changed 
anything in the axis2
configuration this day, but it seems I somehow mixed up my system.


Thanks in advance,
-Rainer



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [AXIS2] Can I mix up my axis2 system / WSDL handling? Please help.

Posted by Rainer Menzner <rm...@L1id.com>.
Hi Thilina,

I've created two issues (1595 and 1596) in JIRA as you suggested.

-Rainer

Thilina Gunarathne schrieb:
> Hi Rainer,
> I just checked by switching ON/OFF rest switches and it works... So
> better mention exactly in JIRA, which switch you turned on to get it
> working...
>
> ~Thilina
>
> On 11/3/06, Thilina Gunarathne <cs...@gmail.com> wrote:
>> Hi Rainer,
>> > Axis2 1.1 RC2 installation went flawless so far. But I had to enable
>> > rest explicitly in
>> > order to get access to the Axis2 server page. Maybe this should be
>> fixed
>> > so that
>> > this important page is available without further setup.
>>
>> Please log a JIRA... Thanx for finding this out..
>>
>>
>> > Furthermore, I noticed, that redeployment of a service does not always
>> > produce a
>> > clean status in the tomcat container. For example, after renaming a
>> > service method,
>> > axis2 service overview showed both the obsolete name and the new name.
>> > For myself, I now concluded to better restart tomcat in order to get a
>> > well-defined
>> > status.
>> A separate Jira for this would be nice too...
>>
>> Thanx,
>> Thilina
>>
>>
>> >
>> > Thanks and best regards,
>> > -Rainer
>> >
>> >
>> > Davanum Srinivas schrieb:
>> > > Please try the RC2 build on a fresh tomcat instance and let us
>> know if
>> > > you still have problems when you deploy the aar.
>> > >
>> > > thanks,
>> > > dims
>> > >
>> > > On 11/2/06, Rainer Menzner <rm...@l1id.com> wrote:
>> > >> Hi,
>> > >>
>> > >> unil a few hours ago, I had a trivial service for which axis2
>> > >> auto-generated a WSDL. This does no longer work for some reason.
>> > >> I constantly keep the Message:
>> > >>
>> > >> <error>
>> > >> <description>Unable 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>
>> > >>
>> > >>
>> > >> My service *uses* rpc receivers, my services.xml looks like
>> > >>
>> > >> <service>
>> > >> <description>
>> > >> First service, which echoes a string passed in.
>> > >> </description>
>> > >> <parameter name="ServiceClass">my.ws.EchoService</parameter>
>> > >> <operation name="myEcho">
>> > >> <messageReceiver
>> > >> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>> > >> </operation>
>> > >> </service>
>> > >>
>> > >> I also have an example of a handwritten wsdl which worked
>> (according to
>> > >> the issue and
>> > >> the solutions brought up by Matthew Hannay recently. If I query
>> this
>> > >> service, it also does
>> > >> not show any wsdl, neither my handwritten nor an auto-generated
>> one. It
>> > >> insists on the error
>> > >> message above.
>> > >>
>> > >> Can someone give me a hint about this? I'm not aware that I changed
>> > >> anything in the axis2
>> > >> configuration this day, but it seems I somehow mixed up my system.
>> > >>
>> > >>
>> > >> Thanks in advance,
>> > >> -Rainer
>> > >>
>> > >>
>> > >>
>> > >>
>> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>> > --
>> >
>> > Dr. Rainer Menzner
>> > Research & Development
>> >
>> > Identix
>> > an L-1 Identity Solutions Company (NYSE: ID)
>> >
>> > Mail Address:
>> > Viisage Technology AG
>> > Universitaetsstrasse 160
>> > D-44801 Bochum, Germany
>> >
>> > Phone: +49 (0)234 9787-41
>> > Fax: +49 (0)234 9787-77
>> > E-mail: rmenzner@L1id.com
>> >
>> > Visit our Website: www.L1id.com
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >
>>
>>
>> -- 
>> http://webservices.apache.org/~thilina/
>> http://thilinag.blogspot.com/
>>
>
>


-- 

Dr. Rainer Menzner
Research & Development

Identix
an L-1 Identity Solutions Company (NYSE: ID)

Mail Address:
Viisage Technology AG
Universitaetsstrasse 160
D-44801 Bochum, Germany

Phone:  +49 (0)234 9787-41
Fax:    +49 (0)234 9787-77
E-mail: rmenzner@L1id.com

Visit our Website: www.L1id.com



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [AXIS2] Can I mix up my axis2 system / WSDL handling? Please help.

Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi Rainer,
I just checked by switching ON/OFF rest switches and it works... So
better mention  exactly in JIRA, which switch you turned on to get it
working...

~Thilina

On 11/3/06, Thilina Gunarathne <cs...@gmail.com> wrote:
> Hi Rainer,
> > Axis2 1.1 RC2 installation went flawless so far. But I had to enable
> > rest explicitly in
> > order to get access to the Axis2 server page. Maybe this should be fixed
> > so that
> > this important page is available without further setup.
>
> Please log a JIRA... Thanx for finding this out..
>
>
> > Furthermore, I noticed, that redeployment of a service does not always
> > produce a
> > clean status in the tomcat container. For example, after renaming a
> > service method,
> > axis2 service overview showed both the obsolete name and the new name.
> > For myself, I now concluded to better restart tomcat in order to get a
> > well-defined
> > status.
> A separate Jira for this would be nice too...
>
> Thanx,
> Thilina
>
>
> >
> > Thanks and best regards,
> > -Rainer
> >
> >
> > Davanum Srinivas schrieb:
> > > Please try the RC2 build on a fresh tomcat instance and let us know if
> > > you still have problems when you deploy the aar.
> > >
> > > thanks,
> > > dims
> > >
> > > On 11/2/06, Rainer Menzner <rm...@l1id.com> wrote:
> > >> Hi,
> > >>
> > >> unil a few hours ago, I had a trivial service for which axis2
> > >> auto-generated a WSDL. This does no longer work for some reason.
> > >> I constantly keep the Message:
> > >>
> > >> <error>
> > >> <description>Unable 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>
> > >>
> > >>
> > >> My service *uses* rpc receivers, my services.xml looks like
> > >>
> > >> <service>
> > >> <description>
> > >> First service, which echoes a string passed in.
> > >> </description>
> > >> <parameter name="ServiceClass">my.ws.EchoService</parameter>
> > >> <operation name="myEcho">
> > >> <messageReceiver
> > >> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
> > >> </operation>
> > >> </service>
> > >>
> > >> I also have an example of a handwritten wsdl which worked (according to
> > >> the issue and
> > >> the solutions brought up by Matthew Hannay recently. If I query this
> > >> service, it also does
> > >> not show any wsdl, neither my handwritten nor an auto-generated one. It
> > >> insists on the error
> > >> message above.
> > >>
> > >> Can someone give me a hint about this? I'm not aware that I changed
> > >> anything in the axis2
> > >> configuration this day, but it seems I somehow mixed up my system.
> > >>
> > >>
> > >> Thanks in advance,
> > >> -Rainer
> > >>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: axis-user-help@ws.apache.org
> > >>
> > >>
> > >
> > >
> >
> >
> > --
> >
> > Dr. Rainer Menzner
> > Research & Development
> >
> > Identix
> > an L-1 Identity Solutions Company (NYSE: ID)
> >
> > Mail Address:
> > Viisage Technology AG
> > Universitaetsstrasse 160
> > D-44801 Bochum, Germany
> >
> > Phone:  +49 (0)234 9787-41
> > Fax:    +49 (0)234 9787-77
> > E-mail: rmenzner@L1id.com
> >
> > Visit our Website: www.L1id.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> http://webservices.apache.org/~thilina/
> http://thilinag.blogspot.com/
>


-- 
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [AXIS2] Can I mix up my axis2 system / WSDL handling? Please help.

Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi Rainer,
> Axis2 1.1 RC2 installation went flawless so far. But I had to enable
> rest explicitly in
> order to get access to the Axis2 server page. Maybe this should be fixed
> so that
> this important page is available without further setup.

Please log a JIRA... Thanx for finding this out..


> Furthermore, I noticed, that redeployment of a service does not always
> produce a
> clean status in the tomcat container. For example, after renaming a
> service method,
> axis2 service overview showed both the obsolete name and the new name.
> For myself, I now concluded to better restart tomcat in order to get a
> well-defined
> status.
A separate Jira for this would be nice too...

Thanx,
Thilina


>
> Thanks and best regards,
> -Rainer
>
>
> Davanum Srinivas schrieb:
> > Please try the RC2 build on a fresh tomcat instance and let us know if
> > you still have problems when you deploy the aar.
> >
> > thanks,
> > dims
> >
> > On 11/2/06, Rainer Menzner <rm...@l1id.com> wrote:
> >> Hi,
> >>
> >> unil a few hours ago, I had a trivial service for which axis2
> >> auto-generated a WSDL. This does no longer work for some reason.
> >> I constantly keep the Message:
> >>
> >> <error>
> >> <description>Unable 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>
> >>
> >>
> >> My service *uses* rpc receivers, my services.xml looks like
> >>
> >> <service>
> >> <description>
> >> First service, which echoes a string passed in.
> >> </description>
> >> <parameter name="ServiceClass">my.ws.EchoService</parameter>
> >> <operation name="myEcho">
> >> <messageReceiver
> >> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
> >> </operation>
> >> </service>
> >>
> >> I also have an example of a handwritten wsdl which worked (according to
> >> the issue and
> >> the solutions brought up by Matthew Hannay recently. If I query this
> >> service, it also does
> >> not show any wsdl, neither my handwritten nor an auto-generated one. It
> >> insists on the error
> >> message above.
> >>
> >> Can someone give me a hint about this? I'm not aware that I changed
> >> anything in the axis2
> >> configuration this day, but it seems I somehow mixed up my system.
> >>
> >>
> >> Thanks in advance,
> >> -Rainer
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
>
>
> --
>
> Dr. Rainer Menzner
> Research & Development
>
> Identix
> an L-1 Identity Solutions Company (NYSE: ID)
>
> Mail Address:
> Viisage Technology AG
> Universitaetsstrasse 160
> D-44801 Bochum, Germany
>
> Phone:  +49 (0)234 9787-41
> Fax:    +49 (0)234 9787-77
> E-mail: rmenzner@L1id.com
>
> Visit our Website: www.L1id.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [AXIS2] Can I mix up my axis2 system / WSDL handling? Please help.

Posted by Rainer Menzner <rm...@L1id.com>.
after installing Axis2 1.1 RC2 (and fixing a few consistency problems with
respect to the axis version used to build the client and the service) wsdl
generation now works as before.

Axis2 1.1 RC2 installation went flawless so far. But I had to enable
rest explicitly in
order to get access to the Axis2 server page. Maybe this should be fixed
so that
this important page is available without further setup.

Furthermore, I noticed, that redeployment of a service does not always
produce a
clean status in the tomcat container. For example, after renaming a
service method,
axis2 service overview showed both the obsolete name and the new name.
For myself, I now concluded to better restart tomcat in order to get a
well-defined
status.

Thanks and best regards,
-Rainer


Davanum Srinivas schrieb:
> Please try the RC2 build on a fresh tomcat instance and let us know if
> you still have problems when you deploy the aar.
>
> thanks,
> dims
>
> On 11/2/06, Rainer Menzner <rm...@l1id.com> wrote:
>> Hi,
>>
>> unil a few hours ago, I had a trivial service for which axis2
>> auto-generated a WSDL. This does no longer work for some reason.
>> I constantly keep the Message:
>>
>> <error>
>> <description>Unable 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>
>>
>>
>> My service *uses* rpc receivers, my services.xml looks like
>>
>> <service>
>> <description>
>> First service, which echoes a string passed in.
>> </description>
>> <parameter name="ServiceClass">my.ws.EchoService</parameter>
>> <operation name="myEcho">
>> <messageReceiver
>> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>> </operation>
>> </service>
>>
>> I also have an example of a handwritten wsdl which worked (according to
>> the issue and
>> the solutions brought up by Matthew Hannay recently. If I query this
>> service, it also does
>> not show any wsdl, neither my handwritten nor an auto-generated one. It
>> insists on the error
>> message above.
>>
>> Can someone give me a hint about this? I'm not aware that I changed
>> anything in the axis2
>> configuration this day, but it seems I somehow mixed up my system.
>>
>>
>> Thanks in advance,
>> -Rainer
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>


-- 

Dr. Rainer Menzner
Research & Development

Identix
an L-1 Identity Solutions Company (NYSE: ID)

Mail Address:
Viisage Technology AG
Universitaetsstrasse 160
D-44801 Bochum, Germany

Phone:  +49 (0)234 9787-41
Fax:    +49 (0)234 9787-77
E-mail: rmenzner@L1id.com

Visit our Website: www.L1id.com



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: [AXIS2] Can I mix up my axis2 system / WSDL handling? Please help.

Posted by Davanum Srinivas <da...@gmail.com>.
Please try the RC2 build on a fresh tomcat instance and let us know if
you still have problems when you deploy the aar.

thanks,
dims

On 11/2/06, Rainer Menzner <rm...@l1id.com> wrote:
> Hi,
>
> unil a few hours ago, I had a trivial service for which axis2
> auto-generated a WSDL. This does no longer work for some reason.
> I constantly keep the Message:
>
> <error>
> <description>Unable 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>
>
>
> My service *uses* rpc receivers, my services.xml looks like
>
> <service>
> <description>
> First service, which echoes a string passed in.
> </description>
> <parameter name="ServiceClass">my.ws.EchoService</parameter>
> <operation name="myEcho">
> <messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
> </operation>
> </service>
>
> I also have an example of a handwritten wsdl which worked (according to
> the issue and
> the solutions brought up by Matthew Hannay recently. If I query this
> service, it also does
> not show any wsdl, neither my handwritten nor an auto-generated one. It
> insists on the error
> message above.
>
> Can someone give me a hint about this? I'm not aware that I changed
> anything in the axis2
> configuration this day, but it seems I somehow mixed up my system.
>
>
> Thanks in advance,
> -Rainer
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org