jsolderitsch wrote: > > > gnodet wrote: >> >> Could you be more precise ? >> The jetty container will start only if you deploy an service unit >> on the http component, or if you configure it in the servicemix.xml. >> >> For RPC/Document problem, you are right. You may hit issues >> using RPC, depending on what you are trying to achieve. >> >>> > Cheers, >>> > Guillaume Nodet >>> > >>> > >>> >>> One of my colleagues here suggested that perhaps the HTTP BC does not >>> like >>> the fact that my SOAP/WSDL is RPC style rather than document style. >>> Apparently none of the ServiceMix HTTP examples use RPC and are all in >>> the >>> document style. >>> >>> Should that be an issue in this context? >>> >>> >>> Jim >>> >>> -- >> -- >> Cheers, >> Guillaume Nodet >> >> > > I am deploying a service unit on the http component -- it is part of my > service assembly which also includes an eip component. > > On 3.0M2, deploying the exact same assembly causes the jetty container to > start when servicemix starts up. So startup behavior is certainly > different with the snapshots. > > The embedded su's in my service assembly have no code -- just xbeans for > the http component and the eip component -- could that be an issue? > > What syntax can I use in servicemix.xml to force the jetty container to > start -- I don't recall seeing any examples. > > As to the RPC vs. Document issue, I am just using a web service that > someone else wrote that uses RPC. What I am trying to achieve is just a > round trip: from my consumer endpoint through the bus to my provider > endpoint which should be able to process the SOAP request, generate a SOAP > response and then have the response returned back through the consumer > endpoint to my test harness (the oxygen XML tool's SOAP analyzer which > issues the original SOAP request). > > This seems like it ought to be a trial matter for ServiceMix. > > Maybe I am wrong. > > Jim > >
Once I solved my jetty startup problem (see jetty failure thread in Dev forum that I started), I did get my roundtrip example to work with two servicemix endpoints, one acting as a consumer and the other as a provider. So like others have reported, there are fixes in the snapshot releases that improve the developer experience in working with http and eip. The example that did not work in 3.0M2 now works in the August 31 snapshot and presumably in earlier snapshots as well. For my simple test case, the SOAP style (RPC vs. Document) did not cause any issues, at least for the level of integration I was trying to achieve. For the snapshot releases, be aware of the servicemix-shared installer zip which is a dependency for many (all?) of the other servicemix installer components. This was the cause of my jetty not starting complaint -- I needed to install it along with the ones I used with the milestone release. Jim -- View this message in context: http://www.nabble.com/Using-http-and-eip-installer-zips-together-with-SOAP-tf2187193.html#a6091771 Sent from the ServiceMix - User forum at Nabble.com.
