Ok, let me try and gues what the question is asking, and attempt an answer:
If you are sending messages via an XASession, and the XASession's XAResource instance has been enlisted in a global tx, then the messages will actually be sent when the XAResource receives a "commit" from the transaction manager.
This will occur either when you call commit() on a UserTransaction, if you are using a UserTransaction, or if you are in a managed environment and are using container managed transactions (CMT), e.g. you are in an ejb method which where a transaction was started when the method began, and is committed when the method exits.
It can also occur if you have manually enlisted the XAResource in a JTA gloabl tx which you have created and manually called commit on.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968700#3968700
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968700
It is actually:
boolean byte (is BigString)
short size if (short String) or long size if (Big String)
bytes for Strings...
it should be integer, but I'm already using long (if big strings)
If you use StringUtil.. use
StringUtil.saveString(dataOutput,String)
and
StringUtil.readString(dataInput,null); (I was supposed to create an overload here, but null will work here)
If you want/need to move the class to some common project, I'm fine with that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968690#3968690
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968690
Alex wrote : Is there a need to have a standalone installer for JBoss Messaging or is it ok to just add a "Standalone JBoss Messaging" profile to the JEMS installer?
For the time being, Messaging cannot exist without the Microkernel backbone, so just adding a "Standalone JBoss Messaging" profile to the JEMS installer would suffice.
However, with MC integration, Messaging will be become truly standalone, so we will need a separated installer.
Let's not worry about this right now, let's start with the "Standalone Messaging" profile.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968683#3968683
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968683
Alex Pinkin wrote :
| JEMS installer currently has a "JMS server" profile which is based on jbossmq. It currently includes jmx microkernel, logging, hsqldb, jndi, jaas, jta, and jbossmq services.
|
| So my understanding is that we need to add "JBoss Messaging" profile to the installer. Since user can only select one profile, JBoss Messaging and current jbossmq-based "JMS Server" will be mutually exclusive.
|
| Is there a need to have a standalone installer for JBoss Messaging or is it ok to just add a "Standalone JBoss Messaging" profile to the JEMS installer?
|
| Which version of JBoss Messaging?
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968680#3968680
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968680