For non soap endpoints, you can try setting the defaultOperation attribute on the endpoint. This should fix your immediate problem.
However, I don't think this behavior is written in the spec. Maybe OpenEsb is not liberal enough ;-) On 1/10/07, jlo_gestalt <[EMAIL PROTECTED]> wrote:
We use both SOAP endpoints and non-SOAP endpoints. In this particular test case it is not a SOAP endpoint. Yes I agreed this is a big problem for the other components. That is what makes this thread so important. The liberal implementation by ServiceMix of the JBI spec might cause the intent of "pluggable JBI Components." By reading the spec and supporting documents online you would think this is one of the most important features of JBI: the ability to take a component and install it in any JBI container. Much like the flexibility we have with web applications and being able to deploy a WAR, with minor modifications, in Tomcat, Weblogic, JBoss, etc. Looking forward to your response. -- View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8260442 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
