Great you were right, thx a lot.
Will trie again and keep you inform on the status of the project.
gnodet wrote:
>
> Wecome back, Eric !
>
> I have the following stuff in your test
> HttpEndpoint provider = new HttpEndpoint();
> provider.setService(new QName("urn:provider", "http"));
> provider.setEndpoint("provider");
> //provider.setTargetService(new QName("urn:test", "echo"));
> //provider.setTargetEndpoint("echo");
> provider.setLocationURI("http://localhost:8080/";);
> provider.setRoleAsString("provider");
> provider.setSoap(true);
> provider.setSoapVersion("1.1");
> //provider.setWsdlResource(new
> ClassPathResource("Retailer.wsdl"));
> provider.setDefaultMep(URI.create("
> http://www.w3.org/2004/08/wsdl/in-out";));
> provider.setSoap(false);
>
> So the soap attribute is first set to true, and later to false ;)
>
> On 8/23/06, Eric Dofonsou <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hello,
>> I've had a few discussion with Guillaume on WSi Compliance and Servicemix
>> for SOAP based endpoints.
>> I've build a project to test services for WSi compliance however like it
>> was
>> mention in the message below it fails, and I get an error about a missing
>> soap header found on a non-soap header (see below). I was told that it
>> might be beacuse I have soap set as false which is not the case.
>>
>> I can upload a tar.gz of my project for eclipse if it can be of any
>> assistance.
>>
>> ------------------------
>>
>> :WARN: EXCEPTION
>> javax.servlet.ServletException: Failed to process request:
>> java.lang.Exception: java.lang.IllegalStateException: SOAP headers found
>> on
>> non-soap message
>> at
>> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java
>> :79)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at org.mortbay.jetty.servlet.ServletHolder.handle(
>> ServletHolder.java:442)
>> at org.mortbay.jetty.servlet.ServletHandler.handle(
>> ServletHandler.java:357)
>> at org.mortbay.jetty.handler.ContextHandler.handle(
>> ContextHandler.java:615)
>> at
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(
>> ContextHandlerCollection.java:150)
>> at
>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
>> :123)
>> at org.mortbay.jetty.handler.HandlerWrapper.handle(
>> HandlerWrapper.java:141)
>> at org.mortbay.jetty.Server.handle(Server.java:272)
>> at org.mortbay.jetty.HttpConnection.handlerRequest(
>> HttpConnection.java:396)
>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
>> :305)
>> at
>> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
>> :270)
>> at
>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java
>> :475)
>>
>> -----------------------
>> PREVIOUS EMAILS
>>
>> Just had a look at the project. This is a good start, thx !
>> It seems the problem comes from the fact that you have a
>> provider.setSoap(false)
>> in the WSITest.java. This implies that the provider will not send the
>> soap
>> envelope
>> which (I think) is not the intended behavior. Thus, an exception is
>> thrown
>> because
>> some soap headers are configured on the exchange.
>>
>> If possible, i 'd like to have such discussions on the dev mailing list
>> :)
>>
>> Cheers,
>> Guillaume Nodet
>>
>> On 6/26/06, Eric Dofonsou <[EMAIL PROTECTED]> wrote:
>>
>> Hello Guillaume
>>
>> I've build project for the WSI compliance testing.
>> Right now all it does is build an HTTP server that
>> respond to the two WSI compliance request. The
>> request are send via the bus. If you tried to run the
>> project, you will see that the secound request
>> (request-submitorder.xml) failes. Thats is the error
>> I was talking to you about with the soap header issue.
>>
>> - I did not add WSI monitoring programe yet.
>>
>> I've included a tar.gz of my project as an
>> attachement. I tried the new build this morning but
>> it failed to compile the eclipse project file.
>>
>>
>> PS : Sorry for the late feedback on this, but I was
>> away from work for the past 3 week.
>>
>>
>>
>> --- Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>>
>> > Yes please.
>> >
>> > Cheers,
>> > Guillaume Nodet
>> >
>> > On 5/29/06, Eric Dofonsou < [EMAIL PROTECTED]>
>> > wrote:
>> > >
>> > > Great do you want me to open a Jira for this ?
>> > >
>> > > --- Guillaume Nodet < [EMAIL PROTECTED]> wrote:
>> > >
>> > > > Given that the import is relative to the main
>> > wsdl,
>> > > > I think this is a bug.
>> > > > I will take a look at this.
>> > > >
>> > > > Cheers,
>> > > > Guillaume Nodet
>> > > >
>> > > > On 5/29/06, Eric Dofonsou <[EMAIL PROTECTED]>
>> > > > wrote:
>> > > > >
>> > > > > Hello,
>> > > > >
>> > > > > I've got a quick question for you on how
>> > > > > servicemix-http loads WSDL with import
>> > statements.
>> > > > > I'am trying to load the following WSDL :
>> > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> >
>> --
>> View this message in context:
>> http://www.nabble.com/WSi-issues-tf2154100.html#a5950256
>> Sent from the ServiceMix - Dev forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context:
http://www.nabble.com/WSi-issues-tf2154100.html#a5982834
Sent from the ServiceMix - Dev forum at Nabble.com.
