I am using the JBoss Tools to deploy a seam application to a JBoss server from within eclipse. I am consistently seeing a strange behavior. Every time the .xhtml files are changed the seam application is auto-deployed as expected. However, the entity manager instance is becoming null and I am forced forced to restart the seam application by removing it and adding it through the eclipse server view. The whole process is taking more time than I can afford. Is there a workaround to this problem?
+1
A:
If you change a xhtml file only that single file should be copied and the entitymanager should not be affected. Are you refreshing the browser ? Triggering some specific action on that page ?
Max Rydahl Andersen
2009-10-31 18:29:45
whoops - that should have been a comment not a answer.
Max Rydahl Andersen
2009-10-31 18:30:07
I am changing the .xhtml. Waiting for Jboss to publish it. and refreshing the browser. Yet I keep getting the EntityManager is null exception.
hbagchi
2009-11-02 07:06:12
+1
A:
I'm guessing you use JBoss 5.1.0 server? If yes, there are a bunch of problems with this server while working with Seam especially in version 2.2.0. You may also read about general problems with deployment to JBoss5 container.
The other thing you must remeber is to set debug mode for Seam and development mode for facelets. Whitout this two configurations hot deployment won't work.
cetnar
2009-11-07 08:47:16
A:
How does one set debug mode for Seam and development mode for Facelets?
Todd Trimmer
2009-12-14 18:24:46