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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote:
>
> > Not yet. Where does the wsdl come from ?
> > Could you paste your configuration file ?
> >
> > Cheers,
> > Guillaume Nodet
> >
> > On 5/17/06, Eric Dofonsou <[EMAIL PROTECTED]>
> > wrote:
> > > Did you get a chance to look at this ?
> > >
> > > Now that I've finished the SOAP fault message
> > issue. I
> > > can check it out ?
> > >
> > > --- Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > >
> > > > I will fix that as soon as our svn server is up
> > > > again.
> > > >
> > > > Cheers,
> > > > Guillaume Nodet
> > > >
> > > > On 5/10/06, Eric Dofonsou <[EMAIL PROTECTED]>
> > > > wrote:
> > > > >
> > > > > Okay here is my scenario :
> > > > > I'am hosting a web service trought the BUS :
> > > > >
> > > > > Stub client -> BUS HTTP Consumer -> BUS Http
> > > > Provider
> > > > > -> Web Service on JBoss
> > > > >
> > > > > This works fine when we are generating the
> > stub in
> > > > > Java with wsimport.  However when we try to
> > > > generate
> > > > > the stub in C#.  We get the following  error :
> > > > >
> > > > > ---
> > > > > Unabe to import binding
> > 'MyWebServicePortBinding'
> > > > from
> > > > > namespace 'http://mynamespce.com'
> > > > > ----
> > > > >
> > > > > We've traced this to be because the following
> > tag
> > > > > which is empty  on Jboss is no longer included
> > > > when
> > > > > exposed throught the  BUS :
> > > > > ---
> > > > > Error: Unable to import binding
> > > > > 'MyWebServicePortBinding' from name
> > > > >
> > > > > space 'http://my.namespace.services.com/'.
> > > > >
> > > > >   - Unable to import operation 'myOperation'.
> > > > >
> > > > >   - The operation binding 'delete' from
> > namespace
> > > > > 'http://my.namespace.services.com/' had
> > invalid
> > > > > syntax.  Missing soap:-Operation binding.
> > > > > ---
> > > > >
> > > > > Could this be because we are using a
> > WSLDescriptor
> > > > > object to regenerate the WSDL in the BUS ?  Is
> > > > there a
> > > > > workaround for this ?
> > > > > ----
> > > > > <soap peration soapAction=""/>
> > > > > ---
> > > > >
> > > > >
> > __________________________________________________
> > > > > Do You Yahoo!?
> > > > > Tired of spam?  Yahoo! Mail has the best spam
> > > > protection around
> > > > > http://mail.yahoo.com
> > > > >
> > > >
> > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> > >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>


--
Cheers,
Guillaume Nodet



--
Cheers,
Guillaume Nodet

Reply via email to