[
http://jira.jboss.com/jira/browse/JBSEAM-3047?page=comments#action_12414644 ]
Earl Baugh commented on JBSEAM-3047:
------------------------------------
I have converted back to the distributed mvel jar, and when I can re-produce the exception
I will post it. I spent a few minutes attempt this AM trying to reproduce it, and was
unsuccessful (it may have been that I've updated my Seam distribution twice since this
error has occurred..). The file which had the exception logged got rolled over (with the
log4j config we have in development). At the time this exception occurred, the results
after a couple of hours of Googling, was that there were some issues with parsing that
were somehow 1.4 vs 1.6 specific, and that the answer I discovered indicated that moving
to the same version, but compiled on the same JVM as I deploy to, was the correct
solution. I will continue to see if I can find a copy of hte log, and also attempt to
reproduce again and post a test case.
The version of the JVM impacts which version of mvel*.jar should be
included.
-----------------------------------------------------------------------------
Key: JBSEAM-3047
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3047
Project: Seam
Issue Type: Task
Affects Versions: 2.0.2.GA
Environment: Seam and Java 1.4, 1.5 or 1.6
Reporter: Earl Baugh
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.1.0.BETA1
As described on the MVEL web site, MVEL has some "compiler specific" issues.
You can experience some odd behavior without the correct mvel*.jar that matches the JVM
you are utilizing. The set up scripts should take this into consideration and/or the Seam
package should include something to tell the developer that a different version may be
required based on the JVM selected.
See :
http://mvel.codehaus.org/Downloading+MVEL for the different versions.
They also state: "... if you are deploying to a specific environment, it is
recommended you choose the build which matches your JRE version_"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira