Tibco EMS SOAP/JMS integration

[pi...@comcast.net]

I am currently working on a project where we are attempting to call a service via SOAP/JMS using Tibco EMS queues.

I am not currently using WSIF, but I am investigating it as a candidate for future releases.  In the meantime, I am using JAXB to create the SOAP message and a manually-coded JMS transport layer to get the message into the appropriate queue.

When we attempted to send the SOAP messages in a JMS TextMessage class, Tibco generated an error on the service end, stating that Tibco only supports BytesMessage and StreamMessage for SOAP/JMS.

Looking in the WSIFJMSDestination class, it appears that WSIF currently only sends TextMessage or ObjectMessage message types.  Is this correct, or am I missing something?

Thanks,

Meghan

Re: Tibco EMS SOAP/JMS integration

[Aleksander Slominski <as...@cs.indiana.edu>]

pietila.meghan@comcast.net wrote:

>I am currently working on a project where we are attempting to call a service via SOAP/JMS using Tibco EMS queues.
>
>I am not currently using WSIF, but I am investigating it as a candidate for future releases.  In the meantime, I am using JAXB to create the SOAP message and a manually-coded JMS transport layer to get the message into the appropriate queue.
>
>When we attempted to send the SOAP messages in a JMS TextMessage class, Tibco generated an error on the service end, stating that Tibco only supports BytesMessage and StreamMessage for SOAP/JMS.
>
>Looking in the WSIFJMSDestination class, it appears that WSIF currently only sends TextMessage or ObjectMessage message types.  Is this correct, or am I missing something?
>  
>
AFAIR it is correct.

i think you will need to modify source code of WSIF if you can not 
modify TIBCO to accept TextMessages ;-)

alek

-- 
The best way to predict the future is to invent it - Alan Kay