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 Lorenzo Carnevale <lo...@innovery.it> on 2009/09/07 18:13:36 UTC

[AXIS2] 'Unable to generate WSDL 1.1 for this service'

Hello everybody.
I followed one of Sosnoski's tutorials on IBM website to create Secure w.s. with Rampart.

In Services.xml, I have the following tag:

     <parameter name="useOriginalwsdl">true</parameter>

I am deploying my web service as an aar service in an axis2 standalone server, 
and I have the error "Unable to generate WSDL 1.1 for this service" when I try to access the WS.

Please notice that:
1) I don't care if the WSDL is 1.1 or 2.0
2) I don't want to use, if possible, a 'generated' wsdl: the original wsdl is prettier (and if I declare useOriginalwsdl = false, the generated WSDL provides 3 end points (!) without apparent reason)

I have seen solutions suggesting to put the .wsdl file in the META-INF folder, but working with a .aar I have no such folder.

Thanks to all
         Lorenzo

Re: [AXIS2] 'Unable to generate WSDL 1.1 for this service'

Posted by Lorenzo Carnevale <lo...@innovery.it>.

Thanks, it solves the problem.
  ----- Original Message ----- 
  From: Keith Chapman 
  To: axis-user@ws.apache.org 
  Sent: Wednesday, September 09, 2009 4:17 AM
  Subject: Re: [AXIS2] 'Unable to generate WSDL 1.1 for this service'


  You need to have a folder call META-INF in ur aar file and place the wsdl file in that. Also the service name in the wsdl should be the same as the servicename you used in the services.xml.

  Thanks,
  Keith.


  On Mon, Sep 7, 2009 at 12:13 PM, Lorenzo Carnevale <lo...@innovery.it> wrote:

    Hello everybody.
    I followed one of Sosnoski's tutorials on IBM website to create Secure w.s. with Rampart.

    In Services.xml, I have the following tag:

         <parameter name="useOriginalwsdl">true</parameter>

    I am deploying my web service as an aar service in an axis2 standalone server, 
    and I have the error "Unable to generate WSDL 1.1 for this service" when I try to access the WS.

    Please notice that:
    1) I don't care if the WSDL is 1.1 or 2.0
    2) I don't want to use, if possible, a 'generated' wsdl: the original wsdl is prettier (and if I declare useOriginalwsdl = false, the generated WSDL provides 3 end points (!) without apparent reason)

    I have seen solutions suggesting to put the .wsdl file in the META-INF folder, but working with a .aar I have no such folder.

    Thanks to all
             Lorenzo










  -- 
  Thanks,
  Keith.

  Keith Chapman
  blog: http://www.keith-chapman.org

Re: [AXIS2] 'Unable to generate WSDL 1.1 for this service'

Posted by Keith Chapman <ke...@gmail.com>.

You need to have a folder call META-INF in ur aar file and place the wsdl
file in that. Also the service name in the wsdl should be the same as the
servicename you used in the services.xml.

Thanks,
Keith.

On Mon, Sep 7, 2009 at 12:13 PM, Lorenzo Carnevale <
lorenzo.carnevale@innovery.it> wrote:

>  Hello everybody.
> I followed one of Sosnoski's tutorials on IBM website to create Secure w.s.
> with Rampart.
>
> In Services.xml, I have the following tag:
>
>      <parameter name="useOriginalwsdl">true</parameter>
> I am deploying my web service as an aar service in an axis2 standalone
> server,
> and I have the error "Unable to generate WSDL 1.1 for this service" when I
> try to access the WS.
>
> Please notice that:
> 1) I don't care if the WSDL is 1.1 or 2.0
> 2) I don't want to use, if possible, a 'generated' wsdl: the original wsdl
> is prettier (and if I declare *useOriginalwsdl = false, *the generated
> WSDL provides 3 end points (!) without apparent reason)
>
> I have seen solutions suggesting to put the .wsdl file in the META-INF
> folder, but working with a .aar I have no such folder.
>
> Thanks to all
>          Lorenzo
>
>
>
>
>
>
>
>



-- 
Thanks,
Keith.

Keith Chapman
blog: http://www.keith-chapman.org