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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> > 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 <[EMAIL PROTECTED]> wrote: > > > > > Recompile servicemix-soap also (the function is > in > > > this module). > > > > > > Cheers, > > > Guillaume Nodet > > > > > > On 5/17/06, Eric Dofonsou <[EMAIL PROTECTED]> > > > 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 <[EMAIL PROTECTED]> 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 < > [EMAIL PROTECTED]> > > > > > 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 < [EMAIL PROTECTED]> > 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 < > > > [EMAIL PROTECTED]> > > > > > > > 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
