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. On 8/30/06, jsolderitsch <[EMAIL PROTECTED]> wrote:
gnodet wrote: > > You hit a big that has been fixed some time ago. > You should try a more recent version (maybe one of > the snapshot distribution). > > On 8/30/06, jsolderitsch <[EMAIL PROTECTED]> wrote: > ... stuff > > > -- > 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? I am still looking for a hint of which ServiceMix snapshot fixes the bug Mr. Nodet mentions and has a working jetty capability. Apparently the snapshots from the last 2 days do not. Jim -- View this message in context: http://www.nabble.com/Using-http-and-eip-installer-zips-together-with-SOAP-tf2187193.html#a6068557 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
