Re: [jsr-314-open] [jsf2next] PROJECT_STAGE system property configuration
Lincoln Baxter, III wrote:
However, I really think that access through a
*-Djavax.faces.ProjectStage=Development* system property is simple,
and understandable. It doesn't take much work to figure out how to use
it, much less potentially confusing than configuring JNDI and it's
mapping in web.xml. It makes IDE integration simple... you don't even
need IDE plug-in support because you just add it as a JVM argument to
your server's launch configuration; lots of tools do that. (Ant,
Maven, JavaRebel, Grails, for example.)
The text guys are happy, too, since they do everything from the
command line anyway.
The system property proposal has come up a number of times now. Seems
like everybody is in agreement that this is needed.
I think we should keep this in our minds, even if a way to use JNDI
in
a plug-in-friendly way is found. Did we decide if this was too big to
be included in the MR?
I don't remember hearing any decision on this, but my feeling is that we
should get this in for the MR if at all possible. One other reason to
get this in now... MyFaces has already exposed their own system property
for this: org.apache.myfaces.PROJECT_STAGE. Mojarra could of course do
the same, but we would all be better served with a standard property.
BTW, just a reminder - the spec issue for this is here:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=499
Can we add this to the MR list?
Andy