#This file is used by the JNDI FSContext.
#Tue Jun 21 15:02:26 BST 2016
APTopic/ClassName=com.seebeyond.jms.client.STCTopic
connection/ClassName=com.seebeyond.jms.client.STCTopicConnectionFactory
...
Sorry for any confusion. Actually my standalone java code is called by the compute node in the message flow. I am not using the JMSOutput node in this case.
Thank you. You are right. Actually when I said the plain java class can publish the message using the same .binding file by casting the Seebeyond objects to MQ objects.