The bug referred to by trickyvail also affects 4.2 (and most other J2EE App
Servers). It is unavoidable (unless you're using JRockit I think - it doesn't
have a PermGen space), but can be mitigated by setting your JVM memory settings
as per Chapter 2.1 of the Seam ref.
This guy also has a
trickyvail wrote : Yes, running exploded will greatly decrease your build
cycle.
|
| If you are running JBoss 4.0.5.GA please be aware of this bug:
|
http://wiki.jboss.org/wiki/Wiki.jsp?page=OutOfMemoryExceptionWhenRedeploying
Ah I have noticed this on GlassFish V2 as well. I wasn't
anonymous wrote : I really don't want to restart the container every time i
change a *xhtml file
You should run you application from an exploded folder. For my AuthApplication
I have a folder named AuthApplication.ear
Inside there is META-INF, AuthEJB.jar (exploded folder), AuthWebApp.war
Yes, running exploded will greatly decrease your build cycle.
If you are running JBoss 4.0.5.GA please be aware of this bug:
http://wiki.jboss.org/wiki/Wiki.jsp?page=OutOfMemoryExceptionWhenRedeploying
View the original post :
Which version of Jboss AS do you recommend? I have free choise, because im
currently starting to deal with Application Servers. (Should i try 5.0.0Beta2
or is it too unstable?)
I have worked with Tomcat5.5 before.
Do you have any tutorial which explains how i can setup my environment?
The AS
Depends on whether you want to use Seam 1.2.1.GA or 2.0.0.BETA1.
Seam 1.2.1.GA is the current stable release and works with jboss-4.0.5.GA.
Seam 2.0.0.BETA1 is the next version of seam and works with jboss-4.2.0.GA
(maybe 4.2.1.GA - anyone?).
I've not run into any problems with Seam
