Hi,
I'm currently facing a problem with the behaviour of the Jms Adapter.
Whenever a JMS message is put in the queue and that message is not XML valid, the Jms Adapter (consumer) throw the exception "DOM Parsing Exception in translator Exception".
That's fine, I understand that the message was not well formed. But what is not fine is that the underlying BPEL is not instanciated : meaning I can't handle the exception properly.
Is there a way to force the Jms Adapter not to crash on the DOM Parsing for the BPEL to be instanciated (and then being able to handle the exception there) ?
Or is there a way to handle the error thrown by the Jms Adapter itself ? How ?
I think I do have a workaround to this if there is no better option (if both above questions cannot be answered) but I would rather not implement it since it will involve some extra steps / complexity.
> It would be to check the "native format opaque schema" option and then use a java embedded to decode the base64 into a string for eventually parsing it.
regards,
mathieu