-
1. Re: Seam Topic Subscription only works with JBoss Libraries?
samdoyle Jan 22, 2008 7:42 PM (in response to samdoyle)Anyone?
Thanks, S.D. -
2. Re: Seam Topic Subscription only works with JBoss Libraries?
samdoyle Jan 22, 2008 8:35 PM (in response to samdoyle)So looking at the SubscriptionRegistry code it appears that it is possible to override the default connection provider which results in the UIL2ConnectionFactory being used. Is there some specific configuration option I need to use to make this work with GlassFish?
Thanks, S.D. -
3. Re: Seam Topic Subscription only works with JBoss Libraries?
norman.richards Jan 23, 2008 10:59 AM (in response to samdoyle)I don't know if this helps, but here's an article that talks about configuring JMS on GlassFish. http://today.java.net/pub/a/today/2008/01/22/jms-messaging-using-glassfish.html
My superficial reading of this suggests that you need to configure a connection factory per application and then use those JNDI names. -
4. Re: Seam Topic Subscription only works with JBoss Libraries?
samdoyle Jan 23, 2008 11:53 AM (in response to samdoyle)Thanks Norman,
Open MQ is the default built in provider for GlassFish which I have used several times. I was wondering if there was any significance to the UIL2ConnectionFactory just beyond the name. As I said there appears to be a way to override the default in the the SubscriptionRegistry since basically defaults to UIL2ConnectionFactory if a connection provider is not set. Since this is possible I was wondering if there was some configuration option. I guess I can blatantly try creating a connection factory with the name UIL2ConnectionFactory and see if that works.
S.D. -
5. Re: Seam Topic Subscription only works with JBoss Libraries?
norman.richards Jan 23, 2008 11:59 AM (in response to samdoyle)It is only a JNDI name. We default to the name used in JBoss, with the expectations that if you are using another server you can configure the JNDI names in components.xml.
-
6. Re: Seam Topic Subscription only works with JBoss Libraries?
samdoyle Jan 23, 2008 3:19 PM (in response to samdoyle)Ah thanks Norman, I assume this is where this entry comes into play?
<component name="topicPublisher" class="org.jboss.seam.jms.ManagedTopicPublisher"> <property name="topicJndiName">topic/chatroomTopic</property> </component>
The only thing I have set in my components.xml is the jndi-pattern<core:init jndi-pattern="java:comp/env/testapp/#{ejbName}/local" debug="true"/>
Thanks, S.D. -
7. Re: Seam Topic Subscription only works with JBoss Libraries?
shane.bryzak Jan 23, 2008 6:04 PM (in response to samdoyle)Set the connectionProvider property for the subscriptionRegistry component to the class name of the JMSConnectionProvider implementation you want to use. Look at JBossConnectionProvider for an example implementation. All of these classes are in the org.jboss.seam.remoting.messaging package.
-
8. Re: Seam Topic Subscription only works with JBoss Libraries?
samdoyle Jan 23, 2008 8:44 PM (in response to samdoyle)Thanks Shane, I'll take a look.
S.D. -
9. Re: Seam Topic Subscription only works with JBoss Libraries?
norman.richards Jan 23, 2008 9:08 PM (in response to samdoyle)Yes, sorry. I should have remembered there was something extra messy you needed besides XML. We had to make changes to those classes to add support for the new JBoss Messaging project instead of the current JBossMQ support that is there now.
Shane - is there really no way to push all this configuration out to XML? It seems like we ought to be able to do a bit more than we are. -
10. Re: Seam Topic Subscription only works with JBoss Libraries?
shane.bryzak Jan 24, 2008 4:36 AM (in response to samdoyle)Well it mostly is XML except for the JMSConnectionProvider implementation. Perhaps Jay could provide some implementations for other app servers in light of the work he is currently doing. Perhaps we can even auto-wire them as Seam components and have the correct one auto-installed based on the app server that the application is deployed in.