This is my first post. You'll have to pardon me for a little while since I'm
a relative Seam newb.
I'm working on getting set up with the Seam SVN repo, and following the
However, the repo most likely needs permissions to check out, permissions
that I don't have ;) That in itself is not really a problem, but there are
no anonymous authentication credentials listed on the site - perhaps,
something that could improve the experience for interested devs.
If someone could provide them to me, I'll check out the sources and update
the Wiki to provide anonymous credentials (if that's alright.)
Lincoln Baxter, III
"Keep it Simple"
I have (finally) made some progress in hot reloading EJB 3.0 components
(local interface and impl class) in initial testing using the latest build
of JRebel with JBoss 4.2.3.GA and Seam 2.2.0.GA:
JRebel 3.0-M2-SNAPSHOT (201002121625)
*What is the plan for incremental deployment (and specifically EJB 3.x
components) in Seam 3? And perhaps this question also applies to Weld
container b/c it is going to be the container for Seam 3.*
When I ran my test, I ran it with the following default config in the
booking app's component.xml:
<core:init jndi-pattern="@jndiPattern@" debug="true"
My intention was to set debug="false" but I forgot to do that. I'm not sure
exactly what happens when you have the Seam special classloader activated as
well as JRebel for the EJB JAR via rebel.xml. Not sure which takes
precedence, etc. but it works anyways.
I'm thinking the best scenario for fastest dev/build/test cycles is to use
an exploded EAR/WAR and copy facelet (.xhtml) changes (or .css, .js, .html,
etc) to the exploded directory on JBoss and use JRebel for .class file
Does anybody see any downsides/problems with this strategy for achieving
maximum incremental deployment for all possible files in a Seam app?
What about the pages.xml file incremental deployment if you set
debug="false" in <core:init/>?
I'm trying to understand if using debug="true" will have negative affects
with JRebel 3?
I just read this interesting article on fork/join frmwk by Ted Neward:
I'm wondering if there are any plans to use or recommend Seam 3 developers
to use the fork/join frmwk in Seam 3 if Seam 3 will run on JDK 7. I'm
guessing the final release dates for OpenJDK and Seam 3 may possibly be
around the same time (some time after June this year?)
Will Seam 3 be compatible with Java 7?