[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3047) The version of the JVM impacts which version of mvel*.jar should be included.
[ http://jira.jboss.com/jira/browse/JBSEAM-3047?page=comments#action_12414505 ]
Christopher Brock commented on JBSEAM-3047:
-------------------------------------------
Let's be clear though: each MVEL version does not have any forward-compat problems.
If you are using the 1.4 version, it will work FINE on 1.5 and 1.6. And the 1.5 version
will work FINE on 1.5 and 1.6, etc. But there is no backwards compatibility from say, 1.5
to 1.4.
The differences are strictly performance/optimization related due both bytecode and JDK
changes throughout the 3 java versions. But there is no problem with forward
compatibility.
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
Priority: Minor
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