Okay so here is what I found :
the jsr110 for handling WSDL seems to be ignoring soap
action tags when it's empty :
Here is an snipet of what I get from Jboss for a
binding :
----------
<operation name="listRoots">
<soap:operation soapAction=""/>
-
<input>
<soap:body use="literal"/>
</input>
-
<output>
<soap:body use="literal"/>
</output>
-
<fault name="IllegalArgumentException">
<soap:fault use="literal"
name="IllegalArgumentException"/>
</fault>
-
<fault name="ServiceFailureException">
<soap:fault use="literal"
name="ServiceFailureException"/>
</fault>
</operation>
----------
Here is what I get from the WSDL generated by the BUS
for the web service :
----------
<operation name="listRoots">
<input message="tns:listRoots"/>
<output message="tns:listRootsResponse"/>
<fault name="IllegalArgumentException"
message="tns:IllegalArgumentException"/>
<fault name="ServiceFailureException"
message="tns:ServiceFailureException"/>
</operation>
----------
as you can see the <soap:operation /> tag is not
present in the bus version of the WSDL this seems to
be the reason why C# cannot generate the stub. I
think that to be cross platform the WSDL needs to
include that tag even if it's emtpy.
Anybody here knows how to force the WSDL generated by
the jaxa.wsdl package to include all tags even empty
ones ?
--- Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> Not yet. Where does the wsdl come from ?
> Could you paste your configuration file ?
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou <[EMAIL PROTECTED]>
> wrote:
> > Did you get a chance to look at this ?
> >
> > Now that I've finished the SOAP fault message
> issue. I
> > can check it out ?
> >
> > --- Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> >
> > > I will fix that as soon as our svn server is up
> > > again.
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/10/06, Eric Dofonsou <[EMAIL PROTECTED]>
> > > wrote:
> > > >
> > > > Okay here is my scenario :
> > > > I'am hosting a web service trought the BUS :
> > > >
> > > > Stub client -> BUS HTTP Consumer -> BUS Http
> > > Provider
> > > > -> Web Service on JBoss
> > > >
> > > > This works fine when we are generating the
> stub in
> > > > Java with wsimport. However when we try to
> > > generate
> > > > the stub in C#. We get the following error :
> > > >
> > > > ---
> > > > Unabe to import binding
> 'MyWebServicePortBinding'
> > > from
> > > > namespace 'http://mynamespce.com'
> > > > ----
> > > >
> > > > We've traced this to be because the following
> tag
> > > > which is empty on Jboss is no longer included
> > > when
> > > > exposed throught the BUS :
> > > > ---
> > > > Error: Unable to import binding
> > > > 'MyWebServicePortBinding' from name
> > > >
> > > > space 'http://my.namespace.services.com/'.
> > > >
> > > > - Unable to import operation 'myOperation'.
> > > >
> > > > - The operation binding 'delete' from
> namespace
> > > > 'http://my.namespace.services.com/' had
> invalid
> > > > syntax. Missing soap:-Operation binding.
> > > > ---
> > > >
> > > > Could this be because we are using a
> WSLDescriptor
> > > > object to regenerate the WSDL in the BUS ? Is
> > > there a
> > > > workaround for this ?
> > > > ----
> > > > <soap peration soapAction=""/>
> > > > ---
> > > >
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam? Yahoo! Mail has the best spam
> > > protection around
> > > > http://mail.yahoo.com
> > > >
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
>
>
> --
> Cheers,
> Guillaume Nodet
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
