JBoss AS 5.0.1 already contains JBoss Messaging.
And for adding new services, there are two variations:
First, code up your serivce and place the JAR file in the common/lib directory. Then:
a) If the service is JMX-based, place a *-service.xml file in the deploy directory to instantiate and configure your MBean(s)
b) If the service is POJO-based, place a *-jboss-beans.xml file in the deploy directory to instantiate and configure your POJO(s)
Hi Peter, thanks for the replies.
I thought JBoss Messaging(JMS) was only included fo the 'default' server configuration in JBoss 5.0.1. I am running the 'web' server configuration. Is the messaging service also available in the 'web' configuration?
Ah, my mind completely skipped over the part where you wrote that you were using the "web" configuration.
I have never done this but your suggestion is a good start. Also inlcude the server/default/deployers/messaging-definitions-jboss-beans.xml file. Another thing you could do is to download JBoss Messaging and examine the steps it uses to install itself into AS 4.2.x. The steps will not be exactly the same, but they should tell you what else you need. Briefly glancing over those steps it looks like you will have to add the JMS-related security domains to server/web/conf/login-config.xml.
Of course, the recommend practice is to use a configuration that has everyhting (deafult) and remove the stuff your don't want, but you are already asking about that in another thread so you appear to be tackling hte issue from both sides.
Thanks Peter, I'll follow the steps you noted. Yes I am trying to tackle the issue from both ends. Trying to get to a configuration that takes minimal time to start up, but has everything we need.