In our project we use JBOSS + Seam + JSF facelets and use Maven to build.
The problem is exploded deployment doesnt work for us and to see every static .xhtml change we need to compile every single class in the project.
Is there any general step-by-step process that will help me achieve this using Jboss.
We use JBoss 5.0. When deploying the Application EAR in the JBoss server location, it gets deployed as .ear file (NOT a folder)..meaning exploded deployment not working. This makes the UI work very slow. I googled on this, but cud not find a solution. The command for exploded deployment is mvn install -Premote-exploded-deploy but it doesn't do the job for me. It wud be great if anyone can help me with this, it consumes a lot of development time.
The reason i asked you about the specific version of JBoss AS, is because there have been some known issues with hot deployments in some minor versions of JBoss AS-5. So which *specific* version of JBoss AS 5 are you using? There's no JBoss AS 5.0.
Himalay Majumdar wrote:
When deploying the Application EAR in the JBoss server location, it gets deployed as .ear file (NOT a folder)..meaning exploded deployment not working. This makes the UI work very slow. I googled on this, but cud not find a solution. The command for exploded deployment is mvn install -Premote-exploded-deploy
Looks like a Maven question to me, rather than JBoss. And what exactly does, "not working" mean? So you are trying to figure out how to create a exploded deployment out of your application from Maven? If yes, then let us know, we'll move this to a better forum.
Joined: Sep 28, 2008
To be specific we are using JBoss 5.0.1.
After a .xhtml change, a mere page refresh does not reflect the changes, as it used to happen when I worked on Webshpere or Weblogic.
Atleast if I can have exploded deployment, I can change the particular .xhtml file directly from the exploded directory to see the changes right away, but the exploded deployment doesn't work either.
Himalay Majumdar wrote:
... but the exploded deployment doesn't work either.
Keeping aside Maven for a while, why not just manually explode the application and deploy it? Or if you are still interested in doing it through Maven, then you will have to provide the exact details of how you are trying to do this with Maven and what exactly "doesn't work" mean.