Seam 1.2.1.GA still uses jbossmq classes to create jms queues and topics.
Looks like the seam code has to be refactored to support JBoss Messaging.
especially the org\jboss\seam\jms classes.

Assigning this to Seam

How do I get the version of JBoss this is referring to?

That release of JBoss does not start up for me. It locks up at startup:

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /Users/orb/java/jboss-eap-4.3/jboss-as

  JAVA: java

  JAVA_OPTS: -Dprogram.name=run.sh -Xms1503m -Xmx1503m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

  CLASSPATH: /Users/orb/java/jboss-eap-4.3/jboss-as/bin/run.jar

=========================================================================

10:15:19,674 INFO [Server] Starting JBoss (MX MicroKernel)...
10:15:19,675 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200711291835)
10:15:19,676 INFO [Server] Home Dir: /Users/orb/java/jboss-eap-4.3/jboss-as
10:15:19,680 INFO [Server] Home URL: file:/Users/orb/java/jboss-eap-4.3/jboss-as/
10:15:19,681 INFO [Server] Patch URL: null
10:15:19,681 INFO [Server] Server Name: production
10:15:19,681 INFO [Server] Server Home Dir: /Users/orb/java/jboss-eap-4.3/jboss-as/server/production
10:15:19,681 INFO [Server] Server Home URL: file:/Users/orb/java/jboss-eap-4.3/jboss-as/server/production/
10:15:19,681 INFO [Server] Server Log Dir: /Users/orb/java/jboss-eap-4.3/jboss-as/server/production/log
10:15:19,681 INFO [Server] Server Temp Dir: /Users/orb/java/jboss-eap-4.3/jboss-as/server/production/tmp
10:15:19,682 INFO [Server] Root Deployment Filename: jboss-service.xml
10:15:19,919 INFO [ServerInfo] Java version: 1.5.0_13,Apple Inc.
10:15:19,919 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_13-119,Apple Inc.
10:15:19,919 INFO [ServerInfo] OS-System: Mac OS X 10.5.1,i386
10:15:20,204 INFO [Server] Core system initialized
10:15:22,601 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
10:15:22,603 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml

In addition to updating the topic MBean configuration, it looks like Seam remoting will require a JMSConnectionProvider to be written. It looks pretty straight forward, but you might want to verify with Shane.

You may also need additional configuration on the topic/queue publisher. I can't verify that without being able to run it.

Norman, by default, EAP starts up the 'production' config where console logging is limited. In this case, the server had already started, please confirm on the server log.

Gotcha. That explains why I couldn't find any trace of JBoss starting in server/default. :)

I've updated the JNDI names on the AP branch. Obviously this is a completely untested change. I have not made these changes changes to Seam 2. I wouldn't anticipate any problems, but you never can tell. It's you guys call.

Note that I couldn't completely test the example. JBoss messaging appears to use a multicast address that isn't valid on my machine. I assume this is not related to Seam, but I've never touched JBoss messaging before and can't be entirely certain just from looking at the log messages.

Thanks Norman for the quick fixes.

Jay, Can you checkout the latest seam src from Seam_1_2_1_AP branch and test this example with EAP 4.3?
We can then pass it on Release Engg for an official build.

I have verified that the chatroom example now works with EAP 4.3 on RHEL-5 with firefox 2.0.

In order for this to work JBPAPP-494 was created and patched.

JBoss-494 was found while testing the changes to this bug.