-
1. Re: QueueConnectionFactory and TopicConnectionFactory implem
timfox Dec 5, 2006 1:25 PM (in response to todd.nash)The connection factory is org.jboss.jms.client.JBossConnectionFactory and as you can see it implements all connection factory interfaces.
It would have to, or we wouldn't pass JMS 1.1 compliance.public class JBossConnectionFactory implements ConnectionFactory, QueueConnectionFactory, TopicConnectionFactory, XAConnectionFactory, XAQueueConnectionFactory, XATopicConnectionFactory,
-
2. Re: QueueConnectionFactory and TopicConnectionFactory implem
todd.nash Dec 5, 2006 1:38 PM (in response to todd.nash)How do specify that in the connection-factories-service.xml file?
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.destination:service=ConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer
<depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=socket
/ConnectionFactory
jms/eRegQueueConnectionFactory -
3. Re: QueueConnectionFactory and TopicConnectionFactory implem
timfox Dec 5, 2006 1:42 PM (in response to todd.nash)You don't need to.
All connection factories implement all required interfaces. -
4. Re: QueueConnectionFactory and TopicConnectionFactory implem
todd.nash Dec 5, 2006 1:51 PM (in response to todd.nash)Then I am not doing something right because when I do this:
Context initial = getInitialContext();
QueueConnectionFactory cf = (QueueConnectionFactory) initial.lookup("jms/eRegQueueConnectionFactory");
I get a ClassCastException.
When I check the class it is an instance of ConnectionFactory. -
5. Re: QueueConnectionFactory and TopicConnectionFactory implem
timfox Dec 5, 2006 1:54 PM (in response to todd.nash)Please post the full exception
-
6. Re: QueueConnectionFactory and TopicConnectionFactory implem
todd.nash Dec 5, 2006 3:31 PM (in response to todd.nash)Tim,
I have been experimenting with a simple case compiled against the jboss-j2ee .jar with some success.
I am beginning to believe the problem lies in the fact we are compiling against a 1.3 j2ee jar and trying to deploy on a different version of the jar.
Before I burden you any more with this, I will build out my test case a bit more.
Thanks