Right before listing valid values, it says "ignored if the session is transacted.", so any value is legal in that case. The person writing the example probably though that Session.SESSION_TRANSACTED was more clear than null.
On 5/20/2011 11:17 AM, IBeaumont wrote: > I'm looking at the Vendor.java sample that comes with ActiveMQ. > > It does... > connection.createSession(true, Session.SESSION_TRANSACTED); > > Reading the docs... > http://download.oracle.com/javaee/1.4/api/javax/jms/Connection.html#createSession%28boolean,%20int%29 > > that isn't a valid value for create session. Valid values are: > Session.AUTO_ACKNOWLEDGE, Session.CLIENT_ACKNOWLEDGE, > Session.DUPS_OK_ACKNOWLEDGE > > Looking at the defined values... > public static final int AUTO_ACKNOWLEDGE 1 > public static final int CLIENT_ACKNOWLEDGE 2 > public static final int DUPS_OK_ACKNOWLEDGE 3 > public static final int SESSION_TRANSACTED 0 > > it is therefore passing an invalid value of zero to the createSession. > > So is the sample wrong, and therefore also ActiveMQ wrong for accepting it? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Session-SESSION-TRANSACTED-in-example-code-wrong-tp3539083p3539083.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
