Deployment cycle goes into an infinite loop after editing faces-config.xml

[lowecg2004]

Just came across some strange behaviour relating to my Seam project.  I simply edited the file faces-config.xml, after which my project went into an infinite deployment cycle of my app.  I finally tracked this behaviour down to the presence of a file that had been subsequently generated, presumably by Eclipse/JBoss tools, called resources/WEB-INF/.faces-config.xml.jsfdia.  After deleting this file, cleaning my local JBoss dev server and project all was well again.

Just thought I'd share this in case someone else comes across it.

Not sure of the relevance of any of these, but I'm using:
Eclipse 3.4, Seam Tools for Eclipse 3.0.1.GA, Seam 2.1.2 and JBoss 5.1.0.GA

Cheers,

Chris.

[clerum]

I'm guessing this is related.

Infinite loop of redeployments (JBoss 5.x) of project from seam-gen

Seam applications continuously redeploy in AS-5.1.0

EAR undeploys in JBAS 5.1.0GA

It would appear that JBoss 5.1 (or 5.0) isn't suitable for production...or development for matter. But it sounds like these issues will be fixed in 5.1.x

[lowecg2004]

Those are definitely related, thanks for the pointers.  With so many JBoss components potentially involved it was hard to know where to look...

Until this hiccup, AS-5.1.0 had been stable for me.

[clerum]

I agree that 5.1 is generally stable. It just appears to be something with the deployer. To Jboss' credit they were very helpful in figuring out what it was and getting the fix into the trunk.

[tony.herstell1]

I use MyEclipse and I too had this problem.

I found that if I edit one of the seam/jsf config files in the past then I would have to manually stop and re-start the server to make it take effect (note 99.9% of time I am using exploded deployment for rapid development).

Now with latest seam and JBoss 5.1, then the server reloads the seam app and this is when it all goes pear shaped (I don't know if this is Seam or Jboss 5.1).

Anyhow; I have to undeploy app and redeploy app to get rid of the problem.

So as workaround; I stop the server BEFORE saving any changes to these files as it's quicker that sitting there wondering if I will go into infinite loop (as sometimes it works and sometimes not).

I would prefer to manually re-start server when I want these files to take effect than have this problem but then I suppose I have worked that way for a couple of years so am used to knowing what file changes require a server stop/start to see the effect (normally pages.xml, faces.config, messages.properties or bascailyl any file other than a java source file).

Thanks for useful post as it saved me trying to find problem with my code.

May be useful added to JBoss 5.1 and Seam page.

[asiandub]

Thanks for saving my weekend!

[cosmo]

Thanks a lot. For a moment I thought my JBoss AS gone nuts as I didn't know that file
that seems so inoffensive could make such a damage.

[istockler]

This post also saved me a few unproductive hours, thanks! If you are editing faces-config.xml you can do it by using the eclipse built-in Xml editor, just right click and Open With in eclipse. The faces-config editor that comes with WTP also seems not to generate the offending file.