Yes, you should try to raise this problem on OpenESB forums.
I don't think this is required by the spec, so maybe change their
behavior ... I will follow the thread and join if needed.
On 1/11/07, jlo_gestalt <[EMAIL PROTECTED]> wrote:
I made a change to AsyncBaseLifeCycle to log the exception and then log the
message:
catch (Exception e) {
logger.error("Error processing exchange, exception is", e);
logger.error("Error processing exchange" + exchange);
This is probably a good idea to duplicate elsewhere.
Anyways the HTTP Request gets to the HTTP BC and the HTTP BC sends the
request to the EIP component. However when the EIP attempts to send the
Message to our Component, guess what. Are good ol' buddy
javax.jbi.messaging.MessagingException: Operation name required to send
message exchange. EIP doesn't set the operation and consequenlty OpenESB
throws an exception just like the HTTP BC did before I set the
defaultOperation value.
How can we fix this long term? Do we need to discuss with OpenESB and
RonTenHove to overcome this?
--
View this message in context:
http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8278082
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/
