This was a problem with openesb's bpel se not setting the namespace on the
operation in the exchange.
I fixed this with an in interceptor:
public void handleMessage(JBIMessage message) throws Fault {
Exchange ex = message.getExchange();
Endpoint ep = ex.get(Endpoint.class);
BindingInfo service = ep.getEndpointInfo().getBinding();
QName serviceName = service.getName();
QName operationName = message.getJbiExchange().getOperation();
if(operationName.getNamespaceURI()==null||"".equals(operationName.getNamespaceURI())){
message.getJbiExchange().setOperation(new
QName(serviceName.getNamespaceURI(),operationName.getLocalPart()));
}
}
depstei2 wrote:
>
> When the openesb se calls a cxfse parter link on the bus, the message
> exchange object has an endpoint, but the interface and servicename are
> null resulting in null pointer errors in the cxfse. Is there a way in
> servicemix to fix/alter the message exchange object so that servicemix can
> use it? What is the difference between calling something by
> servicename/endpoint instead of servicename/interface?
>
--
View this message in context:
http://www.nabble.com/Openesb-BPEL-SE-is-not-creating-an-exchange-that-servicemix-can-use-tf4939681s12049.html#a14161351
Sent from the ServiceMix - User mailing list archive at Nabble.com.
