I'm currently developing a Seam app and because I had no experience with JBoss AS I decided to pick Tomcat 6 along with Embedded JBoss. I also used Ant instead of anything Eclipse-based (or similar). I had a hard time configuring Tomcat so it would run "stable". I frequently run into a deploy/undeploy issue when using the Catalina Ant tasks:
There are usually a dozen other JAR files (and exceptions thrown) involved. What's really annoying is that there's always the Seam JAR jboss-seam.jar left in the webapp dir when the above happens, which again requires me to restart the server.
Now I'm wondering: Did I make the wrong choice (server and dev tools)?
Not only do the Ant tasks require me to redeploy to local Tomcat for even character that I change, but they also don't work 100% - at least for me. I have some other technologies involved in my project, like JPA (Hibernate) and JSF/Facelets, so would I probably be better of by using JBoss AS? Is that more stable? Are my tools too ancient? I really could use some state-of-the-art advice as I picked Tomcat and Ant because these were the only ones I've used in the past.
Tim Holloway wrote:Actually, Tomcat does not embed JBoss, but JBoss does run an embedded copy of Tomcat.
... Tomcat itself doesn't know what to do with JBoss datasource definitions.
Hmm interesting comments. The latter is probably the cause of my logs files telling me something about a non-JTA persistence context (JTA didn't seem to work). This is just another reason to ditch Tomcat entirely when doing JBoss/Seam web dev.
subject: Tomcat, Seam, and Ant tasks: not fully undeployed - bad toolset combination?