You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Eric Dofonsou <ew...@yahoo.com> on 2006/05/10 16:44:52 UTC
Bug in generating C# Stub from WSDL.
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
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
Sorry, i had the fix locally but it has not been checked in.
This should be ok now.
Please update from svn and give it a try.
Cheers,
Guillaume Nodet
On 5/17/06, Guillaume Nodet <gn...@gmail.com> wrote:
> I have just made a test and I do have the
> <wsdlsoap:operation soapAction=""/>
> element inside the binding operations.
>
> Could you check the generated wsdl with your web browser and post it ?
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou <ew...@yahoo.com> wrote:
> > The WSDL comes from JBoss.
> >
> > Here is the servicemix config file :
> > -------
> > <?xml version="1.0"?>
> > <beans
> > xmlns:sm="http://servicemix.apache.org/config/1.0"
> >
> > xmlns:http="http://servicemix.apache.org/http/1.0"
> >
> > xmlns:demo="http://ws.location.services.cardinal.com/">
> >
> > <classpath>
> > <location>.</location>
> > </classpath>
> >
> > <bean id="propertyConfigurer"
> > class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> > <property name="location"
> > value="classpath:connection.properties"/>
> > </bean>
> >
> > <sm:container id="jbi" useMBeanServer="true"
> > createMBeanServer="true"
> > dumpStats="true"
> > statsInterval="10">
> >
> > <sm:activationSpecs>
> > <sm:activationSpec>
> > <sm:component>
> > <http:component>
> > <http:endpoints>
> > <http:endpoint
> > service="demo:PhysicalLocationService"
> > endpoint="PhysicalLocationServiceWSPort"
> > role="provider"
> > locationURI="${http.provider.uri}"
> >
> > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> > soapVersion="1.1"
> > soap="true" />
> > </http:endpoints>
> > </http:component>
> > </sm:component>
> > </sm:activationSpec>
> >
> > <sm:activationSpec>
> > <sm:component>
> > <http:component>
> > <http:endpoints>
> > <http:endpoint
> > service="demo:PhysicalLocationService"
> > endpoint="PhysicalLocationServiceWSPort"
> > role="consumer"
> > locationURI="${http.consumer.uri}"
> > wsdlResource="${http.provider.uri.wsdl}"
> >
> > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> > soapVersion="1.1"
> > soap="true" />
> > </http:endpoints>
> > </http:component>
> > </sm:component>
> > </sm:activationSpec>
> > </sm:activationSpecs>
> > </sm:container>
> > </beans>
> > ---------
> >
> > --- Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > > Not yet. Where does the wsdl come from ?
> > > Could you paste your configuration file ?
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > > 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 <gn...@gmail.com> wrote:
> > > >
> > > > > I will fix that as soon as our svn server is up
> > > > > again.
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> > > > > 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
> >
>
>
> --
> Cheers,
> Guillaume Nodet
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
I have just made a test and I do have the
<wsdlsoap:operation soapAction=""/>
element inside the binding operations.
Could you check the generated wsdl with your web browser and post it ?
Cheers,
Guillaume Nodet
On 5/17/06, Eric Dofonsou <ew...@yahoo.com> wrote:
> The WSDL comes from JBoss.
>
> Here is the servicemix config file :
> -------
> <?xml version="1.0"?>
> <beans
> xmlns:sm="http://servicemix.apache.org/config/1.0"
>
> xmlns:http="http://servicemix.apache.org/http/1.0"
>
> xmlns:demo="http://ws.location.services.cardinal.com/">
>
> <classpath>
> <location>.</location>
> </classpath>
>
> <bean id="propertyConfigurer"
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="location"
> value="classpath:connection.properties"/>
> </bean>
>
> <sm:container id="jbi" useMBeanServer="true"
> createMBeanServer="true"
> dumpStats="true"
> statsInterval="10">
>
> <sm:activationSpecs>
> <sm:activationSpec>
> <sm:component>
> <http:component>
> <http:endpoints>
> <http:endpoint
> service="demo:PhysicalLocationService"
> endpoint="PhysicalLocationServiceWSPort"
> role="provider"
> locationURI="${http.provider.uri}"
>
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> soapVersion="1.1"
> soap="true" />
> </http:endpoints>
> </http:component>
> </sm:component>
> </sm:activationSpec>
>
> <sm:activationSpec>
> <sm:component>
> <http:component>
> <http:endpoints>
> <http:endpoint
> service="demo:PhysicalLocationService"
> endpoint="PhysicalLocationServiceWSPort"
> role="consumer"
> locationURI="${http.consumer.uri}"
> wsdlResource="${http.provider.uri.wsdl}"
>
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
> soapVersion="1.1"
> soap="true" />
> </http:endpoints>
> </http:component>
> </sm:component>
> </sm:activationSpec>
> </sm:activationSpecs>
> </sm:container>
> </beans>
> ---------
>
> --- Guillaume Nodet <gn...@gmail.com> wrote:
>
> > Not yet. Where does the wsdl come from ?
> > Could you paste your configuration file ?
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > 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 <gn...@gmail.com> wrote:
> > >
> > > > I will fix that as soon as our svn server is up
> > > > again.
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> > > > 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
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
Okay
I'am issing the <faultstring /> attribute
--- Eric Dofonsou <ew...@yahoo.com> wrote:
>
>
> Unfortunately this is not working I'am getting an
> error exception but it's not the exception generated
> from my stub :
> javax.xml.ws.soap.SOAPFaultException
> at
>
com.sun.xml.ws.encoding.soap.ClientEncoderDecoder.toMessageInfo(ClientEncoderDecoder.java:84)
> at
>
com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.toMessageInfo(SOAPXMLDecoder.java:209)
> at
>
com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:538)
> at
>
com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:258)
> at
>
com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
> at
>
com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
> at
>
com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
> at
>
com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
> at $Proxy20.createCareUnit(Unknown Source)
> at Test.createCareUnitWithException(Test.java:33)
> at Test.main(Test.java:21)
>
> My BI exception should be something like "Invlide
> provider" exception.
>
> Anyway I will do some futher investigation on this.
>
>
>
> --- Guillaume Nodet <gn...@gmail.com> wrote:
>
> > Commited !
> > Now, fault data is extracted by the provider and
> the
> > fault detail content is
> > set as the content of the jbi fault.
> > The fault is reconstructed by the provider by
> using
> > properties (code,
> > reason, etc..) set by the provider.
> >
> > Report back if you have any problems.
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/18/06, Guillaume Nodet <gn...@gmail.com>
> > wrote:
> > >
> > > I'm working on enhancements and i'm very close
> to
> > finish ...
> > > You will be notified when the jira issue change.
> > >
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/18/06, Eric Dofonsou <ew...@yahoo.com>
> > wrote:
> > > >
> > > > Thx everything seems to be working now.
> > > >
> > > > Could you please let me know when you apply
> the
> > patch
> > > > for the Jira : SM-433.
> > > >
> > > >
> > > >
> > > > --- Guillaume Nodet <gn...@gmail.com> wrote:
> > > >
> > > > > Have you tried to compile with maven 2 ?
> > > > > Else you can find snapshot builds at
> > > > >
> > > > >
> > > >
> > > >
> >
>
http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/18/06, Eric Dofonsou <
> > ewrickspm@yahoo.com>
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hello I did not manage to build the latest
> > verion
> > > > > of
> > > > > > the code,
> > > > > > I checked out the latest versino from SVN
> > and
> > > > > build
> > > > > > failed.
> > > > > >
> > > > > > I also tried to download a snapshot from :
> > > > > >
> > > > >
> > > >
> >
>
http://people.apache.org/repository/incubator-servicemix/distributions/
> > > > > > But that too failed (besides the snapshots
> > are
> > > > > old).
> > > > > > Do you have any idea where I can get a
> > working
> > > > > buidl
> > > > > > to test ?
> > > > > >
> > > > > >
> > > > > > --- Guillaume Nodet < gnodet@gmail.com>
> > wrote:
> > > > > >
> > > > > > > Recompile servicemix-soap also (the
> > function is
> > > > > in
> > > > > > > this module).
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Guillaume Nodet
> > > > > > >
> > > > > > > On 5/17/06, Eric Dofonsou
> > <ew...@yahoo.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > fetch the latest code from SVN,
> > > > > > > > unable to compile. THe following
> > funcitno is
> > > > > > > missing
> > > > > > > > from HttpEndpoint :
> > > > > > > >
> > > > > > > > httpEp.activateDynamic();
> > > > > > > > return httpEp;
> > > > > > > >
> > > > > > > > I will try the snapshot ...
> > > > > > > >
> > > > > > > > --- Guillaume Nodet <
> gnodet@gmail.com>
> > wrote:
> > > > > > > >
> > > > > > > > > But if you use the fix i have just
> > checked
> > > > > in,
> > > > > > > you
> > > > > > > > > should have the soap
> > > > > > > > > binding informations...
> > > > > > > > > I'm currently uploading new
> snapshots
> > > > > (hopefully
> > > > > > > it
> > > > > > > > > will work)...
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Guillaume Nodet
> > > > > > > > >
> > > > > > > > > On 5/17/06, Eric Dofonsou <
> > > > > ewrickspm@yahoo.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > We are not going not going trhout
> a
> > JSR
> > > > > 181
> > > > > > > > > endpoint
> > > > > > > > > > we are using a HTTP endponits as
> > both
> > > > > provider
> > > > > > > and
> > > > > > > > > > consumer :
> > > > > > > > > >
> > > > > > > > > > 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.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --- Guillaume Nodet <
> > gnodet@gmail.com>
> > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Sorry, but I think I have missed
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
Unfortunately this is not working I'am getting an
error exception but it's not the exception generated
from my stub :
javax.xml.ws.soap.SOAPFaultException
at
com.sun.xml.ws.encoding.soap.ClientEncoderDecoder.toMessageInfo(ClientEncoderDecoder.java:84)
at
com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.toMessageInfo(SOAPXMLDecoder.java:209)
at
com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:538)
at
com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:258)
at
com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
at
com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
at
com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
at
com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
at $Proxy20.createCareUnit(Unknown Source)
at Test.createCareUnitWithException(Test.java:33)
at Test.main(Test.java:21)
My BI exception should be something like "Invlide
provider" exception.
Anyway I will do some futher investigation on this.
--- Guillaume Nodet <gn...@gmail.com> wrote:
> Commited !
> Now, fault data is extracted by the provider and the
> fault detail content is
> set as the content of the jbi fault.
> The fault is reconstructed by the provider by using
> properties (code,
> reason, etc..) set by the provider.
>
> Report back if you have any problems.
>
> Cheers,
> Guillaume Nodet
>
> On 5/18/06, Guillaume Nodet <gn...@gmail.com>
> wrote:
> >
> > I'm working on enhancements and i'm very close to
> finish ...
> > You will be notified when the jira issue change.
> >
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/18/06, Eric Dofonsou <ew...@yahoo.com>
> wrote:
> > >
> > > Thx everything seems to be working now.
> > >
> > > Could you please let me know when you apply the
> patch
> > > for the Jira : SM-433.
> > >
> > >
> > >
> > > --- Guillaume Nodet <gn...@gmail.com> wrote:
> > >
> > > > Have you tried to compile with maven 2 ?
> > > > Else you can find snapshot builds at
> > > >
> > > >
> > >
> > >
>
http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/18/06, Eric Dofonsou <
> ewrickspm@yahoo.com>
> > > > wrote:
> > > > >
> > > > >
> > > > >
> > > > > Hello I did not manage to build the latest
> verion
> > > > of
> > > > > the code,
> > > > > I checked out the latest versino from SVN
> and
> > > > build
> > > > > failed.
> > > > >
> > > > > I also tried to download a snapshot from :
> > > > >
> > > >
> > >
>
http://people.apache.org/repository/incubator-servicemix/distributions/
> > > > > But that too failed (besides the snapshots
> are
> > > > old).
> > > > > Do you have any idea where I can get a
> working
> > > > buidl
> > > > > to test ?
> > > > >
> > > > >
> > > > > --- Guillaume Nodet < gnodet@gmail.com>
> wrote:
> > > > >
> > > > > > Recompile servicemix-soap also (the
> function is
> > > > in
> > > > > > this module).
> > > > > >
> > > > > > Cheers,
> > > > > > Guillaume Nodet
> > > > > >
> > > > > > On 5/17/06, Eric Dofonsou
> <ew...@yahoo.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > fetch the latest code from SVN,
> > > > > > > unable to compile. THe following
> funcitno is
> > > > > > missing
> > > > > > > from HttpEndpoint :
> > > > > > >
> > > > > > > httpEp.activateDynamic();
> > > > > > > return httpEp;
> > > > > > >
> > > > > > > I will try the snapshot ...
> > > > > > >
> > > > > > > --- Guillaume Nodet < gnodet@gmail.com>
> wrote:
> > > > > > >
> > > > > > > > But if you use the fix i have just
> checked
> > > > in,
> > > > > > you
> > > > > > > > should have the soap
> > > > > > > > binding informations...
> > > > > > > > I'm currently uploading new snapshots
> > > > (hopefully
> > > > > > it
> > > > > > > > will work)...
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Guillaume Nodet
> > > > > > > >
> > > > > > > > On 5/17/06, Eric Dofonsou <
> > > > ewrickspm@yahoo.com>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > We are not going not going trhout a
> JSR
> > > > 181
> > > > > > > > endpoint
> > > > > > > > > we are using a HTTP endponits as
> both
> > > > provider
> > > > > > and
> > > > > > > > > consumer :
> > > > > > > > >
> > > > > > > > > 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.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- Guillaume Nodet <
> gnodet@gmail.com>
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > Sorry, but I think I have missed
> > > > something.
> > > > > > > > > > The wsdl generated by the jsr181
> > > > component
> > > > > > can
> > > > > > > > not
> > > > > > > > > > be used as is because all
> > > > > > > > > > binding informations are missing.
> > > > > > > > > > However if you put a
> servicemix-http
> > > > > > component
> > > > > > > > in
> > > > > > > > > > front, it should add all
> > > > > > > > > > the needed binding infos.
> > > > > > > > > > The main reason is that the jsr181
> > > > service
> > > > > > is
> > > > > > > > > > exposed in the jbi bus, not
> > > > > > > > > > over http.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Guillaume Nodet
> > > > > > > > > >
> > > > > > > > > > On 5/17/06, Eric Dofonsou <
> > > > > > ewrickspm@yahoo.com>
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > 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=""/>
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
Commited !
Now, fault data is extracted by the provider and the fault detail content is
set as the content of the jbi fault.
The fault is reconstructed by the provider by using properties (code,
reason, etc..) set by the provider.
Report back if you have any problems.
Cheers,
Guillaume Nodet
On 5/18/06, Guillaume Nodet <gn...@gmail.com> wrote:
>
> I'm working on enhancements and i'm very close to finish ...
> You will be notified when the jira issue change.
>
>
> Cheers,
> Guillaume Nodet
>
> On 5/18/06, Eric Dofonsou <ew...@yahoo.com> wrote:
> >
> > Thx everything seems to be working now.
> >
> > Could you please let me know when you apply the patch
> > for the Jira : SM-433.
> >
> >
> >
> > --- Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > > Have you tried to compile with maven 2 ?
> > > Else you can find snapshot builds at
> > >
> > >
> >
> > http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/18/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > > wrote:
> > > >
> > > >
> > > >
> > > > Hello I did not manage to build the latest verion
> > > of
> > > > the code,
> > > > I checked out the latest versino from SVN and
> > > build
> > > > failed.
> > > >
> > > > I also tried to download a snapshot from :
> > > >
> > >
> > http://people.apache.org/repository/incubator-servicemix/distributions/
> > > > But that too failed (besides the snapshots are
> > > old).
> > > > Do you have any idea where I can get a working
> > > buidl
> > > > to test ?
> > > >
> > > >
> > > > --- Guillaume Nodet < gnodet@gmail.com> wrote:
> > > >
> > > > > Recompile servicemix-soap also (the function is
> > > in
> > > > > this module).
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > > > > wrote:
> > > > > >
> > > > > > fetch the latest code from SVN,
> > > > > > unable to compile. THe following funcitno is
> > > > > missing
> > > > > > from HttpEndpoint :
> > > > > >
> > > > > > httpEp.activateDynamic();
> > > > > > return httpEp;
> > > > > >
> > > > > > I will try the snapshot ...
> > > > > >
> > > > > > --- Guillaume Nodet < gnodet@gmail.com> wrote:
> > > > > >
> > > > > > > But if you use the fix i have just checked
> > > in,
> > > > > you
> > > > > > > should have the soap
> > > > > > > binding informations...
> > > > > > > I'm currently uploading new snapshots
> > > (hopefully
> > > > > it
> > > > > > > will work)...
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Guillaume Nodet
> > > > > > >
> > > > > > > On 5/17/06, Eric Dofonsou <
> > > ewrickspm@yahoo.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > We are not going not going trhout a JSR
> > > 181
> > > > > > > endpoint
> > > > > > > > we are using a HTTP endponits as both
> > > provider
> > > > > and
> > > > > > > > consumer :
> > > > > > > >
> > > > > > > > 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.
> > > > > > > >
> > > > > > > >
> > > > > > > > --- Guillaume Nodet < gnodet@gmail.com>
> > > wrote:
> > > > > > > >
> > > > > > > > > Sorry, but I think I have missed
> > > something.
> > > > > > > > > The wsdl generated by the jsr181
> > > component
> > > > > can
> > > > > > > not
> > > > > > > > > be used as is because all
> > > > > > > > > binding informations are missing.
> > > > > > > > > However if you put a servicemix-http
> > > > > component
> > > > > > > in
> > > > > > > > > front, it should add all
> > > > > > > > > the needed binding infos.
> > > > > > > > > The main reason is that the jsr181
> > > service
> > > > > is
> > > > > > > > > exposed in the jbi bus, not
> > > > > > > > > over http.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Guillaume Nodet
> > > > > > > > >
> > > > > > > > > On 5/17/06, Eric Dofonsou <
> > > > > ewrickspm@yahoo.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > 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
> > >
> > === message truncated ===
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
I'm working on enhancements and i'm very close to finish ...
You will be notified when the jira issue change.
Cheers,
Guillaume Nodet
On 5/18/06, Eric Dofonsou <ew...@yahoo.com> wrote:
>
> Thx everything seems to be working now.
>
> Could you please let me know when you apply the patch
> for the Jira : SM-433.
>
>
>
> --- Guillaume Nodet <gn...@gmail.com> wrote:
>
> > Have you tried to compile with maven 2 ?
> > Else you can find snapshot builds at
> >
> >
>
> http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/18/06, Eric Dofonsou <ew...@yahoo.com>
> > wrote:
> > >
> > >
> > >
> > > Hello I did not manage to build the latest verion
> > of
> > > the code,
> > > I checked out the latest versino from SVN and
> > build
> > > failed.
> > >
> > > I also tried to download a snapshot from :
> > >
> >
> http://people.apache.org/repository/incubator-servicemix/distributions/
> > > But that too failed (besides the snapshots are
> > old).
> > > Do you have any idea where I can get a working
> > buidl
> > > to test ?
> > >
> > >
> > > --- Guillaume Nodet <gn...@gmail.com> wrote:
> > >
> > > > Recompile servicemix-soap also (the function is
> > in
> > > > this module).
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > > > wrote:
> > > > >
> > > > > fetch the latest code from SVN,
> > > > > unable to compile. THe following funcitno is
> > > > missing
> > > > > from HttpEndpoint :
> > > > >
> > > > > httpEp.activateDynamic();
> > > > > return httpEp;
> > > > >
> > > > > I will try the snapshot ...
> > > > >
> > > > > --- Guillaume Nodet <gn...@gmail.com> wrote:
> > > > >
> > > > > > But if you use the fix i have just checked
> > in,
> > > > you
> > > > > > should have the soap
> > > > > > binding informations...
> > > > > > I'm currently uploading new snapshots
> > (hopefully
> > > > it
> > > > > > will work)...
> > > > > >
> > > > > > Cheers,
> > > > > > Guillaume Nodet
> > > > > >
> > > > > > On 5/17/06, Eric Dofonsou <
> > ewrickspm@yahoo.com>
> > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > > We are not going not going trhout a JSR
> > 181
> > > > > > endpoint
> > > > > > > we are using a HTTP endponits as both
> > provider
> > > > and
> > > > > > > consumer :
> > > > > > >
> > > > > > > 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.
> > > > > > >
> > > > > > >
> > > > > > > --- Guillaume Nodet < gnodet@gmail.com>
> > wrote:
> > > > > > >
> > > > > > > > Sorry, but I think I have missed
> > something.
> > > > > > > > The wsdl generated by the jsr181
> > component
> > > > can
> > > > > > not
> > > > > > > > be used as is because all
> > > > > > > > binding informations are missing.
> > > > > > > > However if you put a servicemix-http
> > > > component
> > > > > > in
> > > > > > > > front, it should add all
> > > > > > > > the needed binding infos.
> > > > > > > > The main reason is that the jsr181
> > service
> > > > is
> > > > > > > > exposed in the jbi bus, not
> > > > > > > > over http.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Guillaume Nodet
> > > > > > > >
> > > > > > > > On 5/17/06, Eric Dofonsou <
> > > > ewrickspm@yahoo.com>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 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
> >
> === message truncated ===
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
Thx everything seems to be working now.
Could you please let me know when you apply the patch
for the Jira : SM-433.
--- Guillaume Nodet <gn...@gmail.com> wrote:
> Have you tried to compile with maven 2 ?
> Else you can find snapshot builds at
>
>
http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
>
> Cheers,
> Guillaume Nodet
>
> On 5/18/06, Eric Dofonsou <ew...@yahoo.com>
> wrote:
> >
> >
> >
> > Hello I did not manage to build the latest verion
> of
> > the code,
> > I checked out the latest versino from SVN and
> build
> > failed.
> >
> > I also tried to download a snapshot from :
> >
>
http://people.apache.org/repository/incubator-servicemix/distributions/
> > But that too failed (besides the snapshots are
> old).
> > Do you have any idea where I can get a working
> buidl
> > to test ?
> >
> >
> > --- Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > > Recompile servicemix-soap also (the function is
> in
> > > this module).
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > > wrote:
> > > >
> > > > fetch the latest code from SVN,
> > > > unable to compile. THe following funcitno is
> > > missing
> > > > from HttpEndpoint :
> > > >
> > > > httpEp.activateDynamic();
> > > > return httpEp;
> > > >
> > > > I will try the snapshot ...
> > > >
> > > > --- Guillaume Nodet <gn...@gmail.com> wrote:
> > > >
> > > > > But if you use the fix i have just checked
> in,
> > > you
> > > > > should have the soap
> > > > > binding informations...
> > > > > I'm currently uploading new snapshots
> (hopefully
> > > it
> > > > > will work)...
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/17/06, Eric Dofonsou <
> ewrickspm@yahoo.com>
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > > We are not going not going trhout a JSR
> 181
> > > > > endpoint
> > > > > > we are using a HTTP endponits as both
> provider
> > > and
> > > > > > consumer :
> > > > > >
> > > > > > 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.
> > > > > >
> > > > > >
> > > > > > --- Guillaume Nodet < gnodet@gmail.com>
> wrote:
> > > > > >
> > > > > > > Sorry, but I think I have missed
> something.
> > > > > > > The wsdl generated by the jsr181
> component
> > > can
> > > > > not
> > > > > > > be used as is because all
> > > > > > > binding informations are missing.
> > > > > > > However if you put a servicemix-http
> > > component
> > > > > in
> > > > > > > front, it should add all
> > > > > > > the needed binding infos.
> > > > > > > The main reason is that the jsr181
> service
> > > is
> > > > > > > exposed in the jbi bus, not
> > > > > > > over http.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Guillaume Nodet
> > > > > > >
> > > > > > > On 5/17/06, Eric Dofonsou <
> > > ewrickspm@yahoo.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > 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
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
Have you tried to compile with maven 2 ?
Else you can find snapshot builds at
http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
Cheers,
Guillaume Nodet
On 5/18/06, Eric Dofonsou <ew...@yahoo.com> wrote:
>
>
>
> Hello I did not manage to build the latest verion of
> the code,
> I checked out the latest versino from SVN and build
> failed.
>
> I also tried to download a snapshot from :
> http://people.apache.org/repository/incubator-servicemix/distributions/
> But that too failed (besides the snapshots are old).
> Do you have any idea where I can get a working buidl
> to test ?
>
>
> --- Guillaume Nodet <gn...@gmail.com> wrote:
>
> > Recompile servicemix-soap also (the function is in
> > this module).
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > wrote:
> > >
> > > fetch the latest code from SVN,
> > > unable to compile. THe following funcitno is
> > missing
> > > from HttpEndpoint :
> > >
> > > httpEp.activateDynamic();
> > > return httpEp;
> > >
> > > I will try the snapshot ...
> > >
> > > --- Guillaume Nodet <gn...@gmail.com> wrote:
> > >
> > > > But if you use the fix i have just checked in,
> > you
> > > > should have the soap
> > > > binding informations...
> > > > I'm currently uploading new snapshots (hopefully
> > it
> > > > will work)...
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > > > wrote:
> > > > >
> > > > >
> > > > > We are not going not going trhout a JSR 181
> > > > endpoint
> > > > > we are using a HTTP endponits as both provider
> > and
> > > > > consumer :
> > > > >
> > > > > 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.
> > > > >
> > > > >
> > > > > --- Guillaume Nodet < gnodet@gmail.com> wrote:
> > > > >
> > > > > > Sorry, but I think I have missed something.
> > > > > > The wsdl generated by the jsr181 component
> > can
> > > > not
> > > > > > be used as is because all
> > > > > > binding informations are missing.
> > > > > > However if you put a servicemix-http
> > component
> > > > in
> > > > > > front, it should add all
> > > > > > the needed binding infos.
> > > > > > The main reason is that the jsr181 service
> > is
> > > > > > exposed in the jbi bus, not
> > > > > > over http.
> > > > > >
> > > > > > Cheers,
> > > > > > Guillaume Nodet
> > > > > >
> > > > > > On 5/17/06, Eric Dofonsou <
> > ewrickspm@yahoo.com>
> > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > > 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 < gnodet@gmail.com>
> > wrote:
> > > > > > >
> > > > > > > > Not yet. Where does the wsdl come from ?
> > > > > > > > Could you paste your configuration file
> > ?
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Guillaume Nodet
> > > > > > > >
> > > > > > > > On 5/17/06, Eric Dofonsou <
> > > > ewrickspm@yahoo.com>
> > > > > > > > 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 <gnodet@gmail.com
> > >
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > I will fix that as soon as our svn
> > > > server is
> > > > > > up
> > > > > > > > > > again.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Guillaume Nodet
> > > > > > > > > >
> > > > > > > > > > On 5/10/06, Eric Dofonsou
> > > > > > <ew...@yahoo.com>
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Okay here is my scenario :
> > > > > > > > > > > I'am hosting a web service trought
> > the
> > > > BUS
> > > > > > :
> > > > > > > > > > >
> > > > > > > > > > > Stub client -> BUS HTTP Consumer
> > ->
> > > > BUS
> >
> === message truncated ===
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
Hello I did not manage to build the latest verion of
the code,
I checked out the latest versino from SVN and build
failed.
I also tried to download a snapshot from :
http://people.apache.org/repository/incubator-servicemix/distributions/
But that too failed (besides the snapshots are old).
Do you have any idea where I can get a working buidl
to test ?
--- Guillaume Nodet <gn...@gmail.com> wrote:
> Recompile servicemix-soap also (the function is in
> this module).
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> wrote:
> >
> > fetch the latest code from SVN,
> > unable to compile. THe following funcitno is
> missing
> > from HttpEndpoint :
> >
> > httpEp.activateDynamic();
> > return httpEp;
> >
> > I will try the snapshot ...
> >
> > --- Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > > But if you use the fix i have just checked in,
> you
> > > should have the soap
> > > binding informations...
> > > I'm currently uploading new snapshots (hopefully
> it
> > > will work)...
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > > wrote:
> > > >
> > > >
> > > > We are not going not going trhout a JSR 181
> > > endpoint
> > > > we are using a HTTP endponits as both provider
> and
> > > > consumer :
> > > >
> > > > 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.
> > > >
> > > >
> > > > --- Guillaume Nodet < gnodet@gmail.com> wrote:
> > > >
> > > > > Sorry, but I think I have missed something.
> > > > > The wsdl generated by the jsr181 component
> can
> > > not
> > > > > be used as is because all
> > > > > binding informations are missing.
> > > > > However if you put a servicemix-http
> component
> > > in
> > > > > front, it should add all
> > > > > the needed binding infos.
> > > > > The main reason is that the jsr181 service
> is
> > > > > exposed in the jbi bus, not
> > > > > over http.
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/17/06, Eric Dofonsou <
> ewrickspm@yahoo.com>
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > > 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 < gnodet@gmail.com>
> wrote:
> > > > > >
> > > > > > > Not yet. Where does the wsdl come from ?
> > > > > > > Could you paste your configuration file
> ?
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Guillaume Nodet
> > > > > > >
> > > > > > > On 5/17/06, Eric Dofonsou <
> > > ewrickspm@yahoo.com>
> > > > > > > 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 <gnodet@gmail.com
> >
> > > wrote:
> > > > > > > >
> > > > > > > > > I will fix that as soon as our svn
> > > server is
> > > > > up
> > > > > > > > > again.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Guillaume Nodet
> > > > > > > > >
> > > > > > > > > On 5/10/06, Eric Dofonsou
> > > > > <ew...@yahoo.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Okay here is my scenario :
> > > > > > > > > > I'am hosting a web service trought
> the
> > > BUS
> > > > > :
> > > > > > > > > >
> > > > > > > > > > Stub client -> BUS HTTP Consumer
> ->
> > > BUS
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
Recompile servicemix-soap also (the function is in this module).
Cheers,
Guillaume Nodet
On 5/17/06, Eric Dofonsou <ew...@yahoo.com> wrote:
>
> fetch the latest code from SVN,
> unable to compile. THe following funcitno is missing
> from HttpEndpoint :
>
> httpEp.activateDynamic();
> return httpEp;
>
> I will try the snapshot ...
>
> --- Guillaume Nodet <gn...@gmail.com> wrote:
>
> > But if you use the fix i have just checked in, you
> > should have the soap
> > binding informations...
> > I'm currently uploading new snapshots (hopefully it
> > will work)...
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > wrote:
> > >
> > >
> > > We are not going not going trhout a JSR 181
> > endpoint
> > > we are using a HTTP endponits as both provider and
> > > consumer :
> > >
> > > 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.
> > >
> > >
> > > --- Guillaume Nodet < gnodet@gmail.com> wrote:
> > >
> > > > Sorry, but I think I have missed something.
> > > > The wsdl generated by the jsr181 component can
> > not
> > > > be used as is because all
> > > > binding informations are missing.
> > > > However if you put a servicemix-http component
> > in
> > > > front, it should add all
> > > > the needed binding infos.
> > > > The main reason is that the jsr181 service is
> > > > exposed in the jbi bus, not
> > > > over http.
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > > > wrote:
> > > > >
> > > > >
> > > > > 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 < gnodet@gmail.com> wrote:
> > > > >
> > > > > > Not yet. Where does the wsdl come from ?
> > > > > > Could you paste your configuration file ?
> > > > > >
> > > > > > Cheers,
> > > > > > Guillaume Nodet
> > > > > >
> > > > > > On 5/17/06, Eric Dofonsou <
> > ewrickspm@yahoo.com>
> > > > > > 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 <gnodet@gmail.com >
> > wrote:
> > > > > > >
> > > > > > > > I will fix that as soon as our svn
> > server is
> > > > up
> > > > > > > > again.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Guillaume Nodet
> > > > > > > >
> > > > > > > > On 5/10/06, Eric Dofonsou
> > > > <ew...@yahoo.com>
> > > > > > > > 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
> >
> === message truncated ===
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
fetch the latest code from SVN,
unable to compile. THe following funcitno is missing
from HttpEndpoint :
httpEp.activateDynamic();
return httpEp;
I will try the snapshot ...
--- Guillaume Nodet <gn...@gmail.com> wrote:
> But if you use the fix i have just checked in, you
> should have the soap
> binding informations...
> I'm currently uploading new snapshots (hopefully it
> will work)...
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> wrote:
> >
> >
> > We are not going not going trhout a JSR 181
> endpoint
> > we are using a HTTP endponits as both provider and
> > consumer :
> >
> > 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.
> >
> >
> > --- Guillaume Nodet < gnodet@gmail.com> wrote:
> >
> > > Sorry, but I think I have missed something.
> > > The wsdl generated by the jsr181 component can
> not
> > > be used as is because all
> > > binding informations are missing.
> > > However if you put a servicemix-http component
> in
> > > front, it should add all
> > > the needed binding infos.
> > > The main reason is that the jsr181 service is
> > > exposed in the jbi bus, not
> > > over http.
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > > wrote:
> > > >
> > > >
> > > > 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 < gnodet@gmail.com> wrote:
> > > >
> > > > > Not yet. Where does the wsdl come from ?
> > > > > Could you paste your configuration file ?
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/17/06, Eric Dofonsou <
> ewrickspm@yahoo.com>
> > > > > 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 <gnodet@gmail.com >
> wrote:
> > > > > >
> > > > > > > I will fix that as soon as our svn
> server is
> > > up
> > > > > > > again.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Guillaume Nodet
> > > > > > >
> > > > > > > On 5/10/06, Eric Dofonsou
> > > <ew...@yahoo.com>
> > > > > > > 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
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
But if you use the fix i have just checked in, you should have the soap
binding informations...
I'm currently uploading new snapshots (hopefully it will work)...
Cheers,
Guillaume Nodet
On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com> wrote:
>
>
> We are not going not going trhout a JSR 181 endpoint
> we are using a HTTP endponits as both provider and
> consumer :
>
> 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.
>
>
> --- Guillaume Nodet < gnodet@gmail.com> wrote:
>
> > Sorry, but I think I have missed something.
> > The wsdl generated by the jsr181 component can not
> > be used as is because all
> > binding informations are missing.
> > However if you put a servicemix-http component in
> > front, it should add all
> > the needed binding infos.
> > The main reason is that the jsr181 service is
> > exposed in the jbi bus, not
> > over http.
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > wrote:
> > >
> > >
> > > 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 < gnodet@gmail.com> wrote:
> > >
> > > > Not yet. Where does the wsdl come from ?
> > > > Could you paste your configuration file ?
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/17/06, Eric Dofonsou < ewrickspm@yahoo.com>
> > > > 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 <gnodet@gmail.com > wrote:
> > > > >
> > > > > > I will fix that as soon as our svn server is
> > up
> > > > > > again.
> > > > > >
> > > > > > Cheers,
> > > > > > Guillaume Nodet
> > > > > >
> > > > > > On 5/10/06, Eric Dofonsou
> > <ew...@yahoo.com>
> > > > > > 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
> > >
> >
> >
> >
> > --
> >
> === message truncated ===
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
We are not going not going trhout a JSR 181 endpoint
we are using a HTTP endponits as both provider and
consumer :
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.
--- Guillaume Nodet <gn...@gmail.com> wrote:
> Sorry, but I think I have missed something.
> The wsdl generated by the jsr181 component can not
> be used as is because all
> binding informations are missing.
> However if you put a servicemix-http component in
> front, it should add all
> the needed binding infos.
> The main reason is that the jsr181 service is
> exposed in the jbi bus, not
> over http.
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> wrote:
> >
> >
> > 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 <gn...@gmail.com> wrote:
> >
> > > Not yet. Where does the wsdl come from ?
> > > Could you paste your configuration file ?
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > > 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 <gn...@gmail.com> wrote:
> > > >
> > > > > I will fix that as soon as our svn server is
> up
> > > > > again.
> > > > >
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > >
> > > > > On 5/10/06, Eric Dofonsou
> <ew...@yahoo.com>
> > > > > 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
> >
>
>
>
> --
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
Sorry, but I think I have missed something.
The wsdl generated by the jsr181 component can not be used as is because all
binding informations are missing.
However if you put a servicemix-http component in front, it should add all
the needed binding infos.
The main reason is that the jsr181 service is exposed in the jbi bus, not
over http.
Cheers,
Guillaume Nodet
On 5/17/06, Eric Dofonsou <ew...@yahoo.com> wrote:
>
>
> 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 <gn...@gmail.com> wrote:
>
> > Not yet. Where does the wsdl come from ?
> > Could you paste your configuration file ?
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> > 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 <gn...@gmail.com> wrote:
> > >
> > > > I will fix that as soon as our svn server is up
> > > > again.
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> > > > 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
>
--
Cheers,
Guillaume Nodet
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
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 <gn...@gmail.com> wrote:
> Not yet. Where does the wsdl come from ?
> Could you paste your configuration file ?
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> 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 <gn...@gmail.com> wrote:
> >
> > > I will fix that as soon as our svn server is up
> > > again.
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> > > 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
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
The WSDL comes from JBoss.
Here is the servicemix config file :
-------
<?xml version="1.0"?>
<beans
xmlns:sm="http://servicemix.apache.org/config/1.0"
xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:demo="http://ws.location.services.cardinal.com/">
<classpath>
<location>.</location>
</classpath>
<bean id="propertyConfigurer"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="location"
value="classpath:connection.properties"/>
</bean>
<sm:container id="jbi" useMBeanServer="true"
createMBeanServer="true"
dumpStats="true"
statsInterval="10">
<sm:activationSpecs>
<sm:activationSpec>
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint
service="demo:PhysicalLocationService"
endpoint="PhysicalLocationServiceWSPort"
role="provider"
locationURI="${http.provider.uri}"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true" />
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
<sm:activationSpec>
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint
service="demo:PhysicalLocationService"
endpoint="PhysicalLocationServiceWSPort"
role="consumer"
locationURI="${http.consumer.uri}"
wsdlResource="${http.provider.uri.wsdl}"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
soapVersion="1.1"
soap="true" />
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:container>
</beans>
---------
--- Guillaume Nodet <gn...@gmail.com> wrote:
> Not yet. Where does the wsdl come from ?
> Could you paste your configuration file ?
>
> Cheers,
> Guillaume Nodet
>
> On 5/17/06, Eric Dofonsou <ew...@yahoo.com>
> 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 <gn...@gmail.com> wrote:
> >
> > > I will fix that as soon as our svn server is up
> > > again.
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> > > 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
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
Not yet. Where does the wsdl come from ?
Could you paste your configuration file ?
Cheers,
Guillaume Nodet
On 5/17/06, Eric Dofonsou <ew...@yahoo.com> 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 <gn...@gmail.com> wrote:
>
> > I will fix that as soon as our svn server is up
> > again.
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> > 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
Re: Bug in generating C# Stub from WSDL.
Posted by Eric Dofonsou <ew...@yahoo.com>.
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 <gn...@gmail.com> wrote:
> I will fix that as soon as our svn server is up
> again.
>
> Cheers,
> Guillaume Nodet
>
> On 5/10/06, Eric Dofonsou <ew...@yahoo.com>
> 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
Re: Bug in generating C# Stub from WSDL.
Posted by Guillaume Nodet <gn...@gmail.com>.
I will fix that as soon as our svn server is up again.
Cheers,
Guillaume Nodet
On 5/10/06, Eric Dofonsou <ew...@yahoo.com> 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
>