enableOrderingGroup() not available inside ejb3 Bean an JmsX

[mclu]

Hi!

Any hint on this?

I testest OrderingGroup on 1.4.5 (build 7766) with a client like this:

Connection connection = getConnection();
 Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
 JBossMessageProducer sender = (JBossMessageProducer) session.createProducer(queue);
 sender.enableOrderingGroup("Group1");

The Connection Factory is fetched using

Hashtable<String, String> env = new Hashtable<String, String>();
 env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
 env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
 env.put(Context.PROVIDER_URL, "localhost:22099");

 InitialContext ic = new InitialContext(env);
 cf = (ConnectionFactory) ic.lookup("ConnectionFactory");
 queue = (Queue) ic.lookup("/queue/testQueue");
 ic.close();

It works perfect.
Now I want to migrate this to my ejb3 beans which sends messages but uses transactions.
I am using:

@Resource(mappedName="java:/JmsXA")
private ConnectionFactory cf;

...

Connection connection = cf.createConnection();
connection.start();

Session session = connection.createSession(true, Session.SESSION_TRANSACTED);
 JBossMessageProducer sender = (JBossMessageProducer) session.createProducer(queue);
 sender.enableOrderingGroup("Group1");

This gives a class cast exception because createProducer returns
org.jboss.resource.adapter.jms.JmsMessageProducer and not JBossMessageProducer. The JBossMessageProducer is part of JmsMessageProducer but I can not get it.
I want to use more than one ordering group so it would be nice to be able to set it via the producer.

Any hint how I can handle it with transaction support?
At pdf Userguide page 21 it says regarding JmsXA
"JMS XA Resource adapter, use this to get transacted JMS in beans"

[gaohoward]

Hi Markus,

JmsMessageProducer is JCA wrapper of MessagingProducer. I think you can post a request to JCA forum.

Howard

[mclu]

Hi Howard!

I know! But that is not the question.
I think the wrapper should not provide other methods than the JMS Spec says. Maybe there should be a way to get the delegate.

But from the JBM Usage perspective.
Is there a way to use orderinggroup the programatic way with JBM enlist in the ongoing transaction?

What if I use the XAConnectionFactory iso JmsXA?
Any other ideas?

[gaohoward]

Yes you can use the XAConnectionFactory and use JTA stuff to enlist the resources into the transaction.

Howard