Tuesday, April 27, 2010

ESB Dispatch failed with error Cannot get part 'rootId'

Issue ::
You register an Oracle ESB with some SOAP services and while trying to run the esb, you get the error ::

xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">


xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
xmlns="">env:ESBMessageProcessingFailed
xmlns="">ESB Dispatch failed with error Cannot get part 'rootId'. Part was not found in message; nested exception is: org.collaxa.thirdparty.apache.wsif.WSIFException: Cannot get part 'rootId'. Part was not found in message




Solution:

ESB by default generates ESB WSDL(Java Binding) and SOAP WSDL, By Default ESB WSDL will be invoked for better performance, We have a parameter called "includeESBBinding" to switch Off ESB WSDL, So that we can force to use SOAP based WSDL. So, All you have to do is to force to use SOAP Based WSDL by addding the parameter "includeESBBinding=false" in the Service Definition.

setting includeESBBinding=false on the invoked routing service

1 comments:

Anonymous said...

Genial post and this fill someone in on helped me alot in my college assignement. Gratefulness you for your information.