On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote:

With a nightly or recent build try:

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

Okay, I tried this and I get no love from Axis2.

I've got the WSDL in place:

   $ jar -tf services/pbqs.aar  | grep wsdl
   META-INF/pbqs.wsdl

And the parameter set:

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

But I'm being told:

   Unable to generate WSDL for this service

       Either user has not dropped the wsdl into META-INF or
operations use message
       receivers other than RPC.

There is absolutely nothing printed to my catalina.out to indicate
what the problem might be.

FWIW, all of my messageReceivers are set to be
org.apache.axis2.rpc.receivers.RPCMessageReceiver.

Any guesses as to what's going on?

In case it helps...

   $ md5sum axis2.war
   32f4327ec0dbc733a007327deca40d64  axis2.war

-dan





Or wait for the upcomming release in about a week or so.

HTH,
Robert

On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> I'm a bit stumped here. I've been scouring documentation, articles,
> commentaries and the like for two days, so now I'm going to pester you
> fine folks. :-)
>
> I am generating a wsdl at build time and inserting into the WEB-INF
> directory in my .aar file like so:
>
>     $ jar -tf services/pbqs.aar  | grep wsdl
>     META-INF/PBQS.wsdl
>
> (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I
> couldn't find one.)
>
> But when I issue the "?wsdl" command against my service (running under
> Tomcat, in case it matters), the WSDL I get back is most definitely
> *not* the one I had generated. Any ideas on why this might be? This
> worked fine under Axis1.x, but I cannot for the life of me get it to
> work under Axis2.
>
> In case you're inclined to respond with "Just use the
> automagically-generated WSDL", well, I'd rather not at this point. For
> reasons I'd rather not go into, having a WSDL that describes the
> service *as it was built* would be beneficial to me (and the
> developers at my company who may need to deploy an older version of
> the service for some reason).
>
> I'd also much prefer to *not* go from WSDL->Java--starting with Java and
> generating a WSDL is far less tedious.
>
> -dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to