A JBoss with EJB3 and JBossWS deployers removed? How do they clash with some of our legacy applications? why don't you use Tomcat then?
You misunderstand. My company's standard application platform is JBoss 4.2, with EJ3 and JBossWS deployers removed. This was done because some existing applications on this platform do not play nice with JBoss's EJB3 and WS stacks. I now want to deploy Seam apps on this company standard platform, and I don't want to put EJB3 and JBossWS back in to do it.
I believe out of the box it won't work like that.
You need to alter how you deploy it and your deployment descriptors as well.
You will also have to decide whether to use JPA or Hibernate for your persistence
Check out page 363 of the seam docs. they talk briefly about it.
And i believe the hibernate example on the JBoss Seam download has examples on deploying with just hibernate to various environments as war's.
Thanks the the tip. I'll have a look at that example.
Kenny MacLeod wrote on Jul 31, 2008 17:22:
Now we'd like to start using Seam. We were hoping to use Seam without resorting to EJB3, which is something the docs claim is perfectly possible. However, out-of-the-box, Seam 2.0.2.SP1 will not deploy within the EJB3-less server, due to the ejb-jar.xml in the META-INF directory of the JAR file.
You can remove ejb-jar.xml from META-INF/ in jboss-seam.jar - it's not needed in a JBoss 4.2 deployment (it was needed for a particular rev of embedded jboss).
Is this even practical? Can the Seam runtime deploy and run without EJB3 present, if the Seam application itself makes no reference to EJB3?
Definitely should be, try the above and report back how you get on.
So far so good - removing ejb-jar.xml from jboss-seam.jar allows the Seam runtime to initialise without the EJB3 deployer being present. Very promising, hopefully the application development will go as smoothly.
Thanks for that.