No, there is a soap=true on the servicemix-http component which I initially thought would turn this off, but it doesn't seem to...
I guess I'll have to see what I can work out, I don't care about the proxy wrapping the message as a jbi, I just need the servicemix-http NOT to send it out, wrapped in the jbi stuff. On 10/2/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > > Hi Ryan, > IIRC,I am afraid you can't turn off this for JBI binding. > > But if you don't want to use JBI binding for cxf bc & se inside > servicemix, > I believe you can do it by means of hacking the code a bit. > > Comment out > endpoint.setBindingUri( > org.apache.cxf.binding.jbi.JBIConstants.NS_JBI_BINDING); > in public void validate() of CxfSeEndpoint.java > > and comment out > cf.setBindingId(org.apache.cxf.binding.jbi.JBIConstants.NS_JBI_BINDING); > in private Object createProxy() of CxfSeProxyFactoryBean.java > You need build libs from source your self > By this way you should have get soap binding of message. I have no debug > enviroment by hand so I am not sure this can run successfully for you, but > in theory, it should work. > > Maybe we need a property something like soap=true to let customer to > specify > it in the xbean.xml > Best Regards > > Freeman > > On 10/3/07, Ryan Moquin <[EMAIL PROTECTED]> wrote: > > > > Sure, no problem. I hate to keep bugging but I'm really sunk at the > > moment. Do you happen to know how to turn off this parameter on SOAP > > messages that are sent from CXF components in CXF? > > > > JbiConstants.USE_JBI_WRAPPER > > > > If I use the cxf proxy to servicemix-http provider then my message gets > > wrapped in a jbi wrapper. I think if I could turn that off, I'd be ok > and > > out of my panic. I'm currently searching the source to see if anything > > turns up, but it is checked in the JBI interceptors of servicemix.. so > I'm > > not sure how it originates.... > > > > Any ideas? > > > > On 10/2/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > > > > > > Hi Ryan, > > > > > > In this case, you really need a cxf bc provider, which is not there > now. > > > Would you please fill a jira and I will do it as soon as I am back > from > > > vacation. > > > > > > Best Regards > > > > > > Freeman > > > > > > > > > > > > > > > On 10/3/07, Ryan Moquin <[EMAIL PROTECTED]> wrote: > > > > > > > > I had decided to go a different route to get from my CXF service, > > > through > > > > a > > > > CXF proxy to an external web service. I have a CXFProxy that sends a > > > > message > > > > to my registered http:endpoint that is a provider. This appears to > > > work, > > > > and forward a soap request to a 3rd party URL, but it appears that > > it's > > > > trying to actually send a jbi message to the third party > service. I'm > > > > guessing this means I would need to use the CxfBcProvider, but I > > haven't > > > > been able to figure out how to configure it so that it will forward > my > > > > request to a third party web service. Are there any examples using > > > it? I > > > > didn't see any unit tests. > > > > > > > > > >
