Resolution:
Description:
============
Exception thrown  -

    There is a binding error associated with activity. JMS Queue Requestor
    BWENGINE-100031 Job-26000 Error in [Test/SendJMSPayload.process/JMS Queue Requestor]
    Output data invalid
    caused by: org.xml.sax.SAXException: validation error: unexpected text   ({com.tibco.xml.validation}COMPLEX_E_UNEXPECTED_TEXT)
    at /jms1:ActivityOutput[1]/Body[1] com.tibco.xml.validation.exception.j: unexpected text

Environment:
==========
   o All
   o BusinessEvents 3.0.1    

Cause:
=====
The cause for the exception is " BusinessEvents(BE) uses the Serializer of the request-event’s default destination
to serialize the reply event to JMS message, not the reply-event’s destination Serializer"

Resolution:
=========
Check the MessageSerializer of Request Event's destination. Make sure the
that the MessageSerializer of that destination is TextMessageSerializer.


Attachments:
==========
Find the attached project "JMSQRequestorTest_FromSupport.zip" for your reference for the usage
of the above mentioned behavior.

P.S. In the attached project if you change the MessageSerializer of 'RequestIn' Event's destination to "BytesMessageSerializer"
     and send the message to BE using JMS Queue Requestor process, you can see the above mentioned exception.
    
    

References:
==========
Please refer to section "Internal Use of JMSReplyTo Header Property for Request-Response Scenario" of Chapter 2
of BusinessEvents User Guide.