StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20059214
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-18T22:23:38.387
FavoriteCount
0
LastActivityDate
2013-11-18T22:23:38.387
LastEditDate
LastEditorUserId
0
OwnerUserId
1040886
ParentId
20010400
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Okay so I figured this out. The jms config in axis2.xml should be: <pre><code> <transportReceiver name="ibmMsgSightJMS" class="org.apache.axis2.transport.jms.JMSListener"> <parameter name="myTopicConnectionFactory"> <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">file:/C:/path/to/wso2/repository/conf/jndi</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">connFactory1</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter> </parameter> <parameter name="myQueueConnectionFactory"> <parameter name="java.naming.factory.initial">com.sun.jndi.fscontext.RefFSContextFactory</parameter> <parameter name="java.naming.provider.url">file:/C:/path/to/wso2/repository/conf/jndi</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">connFactory1</parameter> <parameter name="transport.jms.ConnectionFactoryType">queue</parameter> </parameter> <parameter name="default"> <parameter name="java.naming.factory.initial">com.sun.jndi.fscontext.RefFSContextFactory</parameter> <parameter name="java.naming.provider.url">file:/C:/path/to/wso2/repository/conf/jndi</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">connFactory1</parameter> <parameter name="transport.jms.ConnectionFactoryType">topic</parameter> </parameter> </transportReceiver> </code></pre> And I have a jndi properties file named .bindings with the following: <pre><code>connFactory1/ClassName=com.ibm.ima.jms.impl.ImaConnectionFactory connFactory1/FactoryName=com.ibm.ima.jms.impl.ImaConnectionFactory connFactory1/RefAddr/0/Encoding=String connFactory1/RefAddr/0/Type=Port connFactory1/RefAddr/0/Content=16102 connFactory1/RefAddr/1/Encoding=String connFactory1/RefAddr/1/Type=Server connFactory1/RefAddr/1/Content=192.168.154.128 connFactory1/RefAddr/2/Encoding=String connFactory1/RefAddr/2/Content=common connFactory1/RefAddr/2/Type=ObjectType RequestTopic/ClassName=com.ibm.ima.jms.impl.ImaTopic RequestTopic/FactoryName=com.ibm.ima.jms.impl.ImaTopic RequestTopic/RefAddr/0/Encoding=String RequestTopic/RefAddr/0/Type=Name RequestTopic/RefAddr/0/Content=testRequestTopic ResponseTopic/ClassName=com.ibm.ima.jms.impl.ImaTopic ResponseTopic/FactoryName=com.ibm.ima.jms.impl.ImaTopic ResponseTopic/RefAddr/0/Encoding=String ResponseTopic/RefAddr/0/Type=Name ResponseTopic/RefAddr/0/Content=testResponseTopic </code></pre> Also, don't forget to put the ImaJmsClient.jar inside components/lib. I am still having issues where every service is creating topics/queues, and because they are not defined in .bindings, the server is puking. I have worked around this by removing the jms transport protocol on every data service and jar service.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConfigure WSO2 ESB JMS Transport with IBM Messagesight
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChris Ridmann
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConfigure WSO2 ESB JMS Transport with IBM Messagesight
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.