This worked for me (by the way, I am not using an MDB, if you are you will need a few more things). I copied server/default as server/minmsg. Then I removed a lot of stuff. Here is the final deployers directory:
And here is the deploy directory:
You might be able to remove even a few more things and have it work but like I said the above works for me.
I used what you posted as starting point. Then, because we also require a clustered JMS set up i had to work back from an "all" config. Then because the developers need jmx-console access i had to add in JbossWS!
So, i wound up with:
Now I'm CERTAIN i still have too much due to the JBossWS need (could not get it to start without ejb3.deployer). My guess is now i need to look into what services are getting called via the xml files.
But in production i wouldn't have JBossWS anyway for the JMS solution.
But this has been helpful and your info gave the me what i needed to get to this stage!
Thanks so much!
Course i mean jbossweb not ws!
You need jbossweb because of jmx-console - it is a web application. As an alternative, you might try using twiddle. Or look into using JConsole (there are some forum posts, and I think even a wiki page on that). Then you can remove jmx-console, jbossweb, and the associated components.