加快Jboss Seam调试周期的诀窍(Tricks to speed up Jboss Seam debug cycle)

加快Jboss Seam调试周期的诀窍(Tricks to speed up Jboss Seam debug cycle)

我们在eclipse中部署和调试Jboss Seam 2.0 EAR应用程序，在Jboss AS 4.2.2上启动它。 现在我们需要在每次更改消息包，pages.xml，components.xml或模型时重新启动它，这最多需要45秒。

是否可以在热部署中包含上述文件，以及提升启动速度的选项有哪些？

对于参考框架，我们使用英特尔四核6600或更高版本，至少4GB内存。

编辑：除了热部署消息包，pages.xml，components.xml等，我正在寻找提高启动速度（即45秒）的方法。

We deploy and debug a Jboss Seam 2.0 EAR app from within eclipse, booting it on Jboss AS 4.2.2. Right now we need to reboot it every time we change the message bundle, pages.xml, components.xml, or the model, which takes up to 45 seconds.

Is it possible to include aforementioned files in hot deployment, and what are the options for boosting boot speeds?

For a frame of reference, we work on Intel quad core 6600's or better, with at least 4GB of ram.

Edit: I'm looking for ways to improve both boot speed (thats the 45 seconds) besides hot deploying message bundle, pages.xml, components.xml etc.

最满意答案

这对于Seam来说已成为一个突出的问题： https ： //jira.jboss.org/jira/browse/EJBTHREE-1096

这不是一个技巧 - 更多的工作方法 - 但我将所有的UI代码（页面处理程序等）都作为POJO，以便它们可以轻松地进行热部署。 我在SLSB / SFSB中放置了更严肃的业务逻辑，并对它们进行了彻底的单元测试，希望通过UI测试应用程序时，我的部署更少。

目前，pages.xml 可以热部署。 我已经阅读了一些重新加载消息包的解决方案，但它从来没有让我感到困扰，需要进一步调查。

This has been an outstanding issue for Seam for ages now : https://jira.jboss.org/jira/browse/EJBTHREE-1096

It's not a trick - more a method of working - but I have all of my UI code (page handlers etc) as POJOs so that they can be easily hot-deployed. Any more serious business logic I put in SLSB/SFSB and unit test them thoroughly so hopefully I have fewer deploys when testing the application via the UI.

Currently pages.xml can be hot deployed. I've read some solutions for reloading the message bundle but it's never bothered me enough to warrant further investigation.