[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3047) The version of the JVM impacts which version of mvel*.jar should be included.
1:01 p.m.
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: Thirdparty Change
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
2:08 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (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=all ]
Pete Muir updated JBSEAM-3047:
------------------------------
Issue Type: Task (was: Thirdparty Change)
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
11 p.m.
New subject: [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
6:48 a.m.
New subject: [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_12414541 ]
Earl Baugh commented on JBSEAM-3047:
------------------------------------
Actually that does not match with my experience. With the1.4 version running with the 1.6
JVM I encountered issues related to MVEL, which went away by my updating to the 1.6
release of MVEL. I will try to re-create them and post them, but at least with the 1.4
version in the 1.6 JVM this was an issue for me.
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
7:22 a.m.
New subject: [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_12414551 ]
Pete Muir commented on JBSEAM-3047:
-----------------------------------
Seam currently includes mvel14.jar (as specified by Drools).
Assuming Mike is correct, then there is no problem.
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
7:30 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (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=all ]
Pete Muir closed JBSEAM-3047.
-----------------------------
Fix Version/s: 2.1.0.BETA1
Resolution: Partially Completed
Assignee: Pete Muir
Updated the docs to include a tip telling you that you may want to change the mvel jar
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
2:46 p.m.
New subject: [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_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
4:25 p.m.
New subject: [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_12414692 ]
Earl Baugh commented on JBSEAM-3047:
------------------------------------
I was able to re-create the error:
The stack trace is :
org.mvel.CompileException: can not resolve identifier: 'declr'
at org.mvel.ASTNode.getReducedValue(ASTNode.java:315)
at org.mvel.ast.PropertyASTNode.getReducedValue(PropertyASTNode.java:29)
at
org.mvel.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:115)
at org.mvel.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:63)
at org.mvel.TemplateInterpreter.execute(TemplateInterpreter.java:428)
at org.mvel.TemplateInterpreter.parse(TemplateInterpreter.java:320)
at
org.drools.rule.builder.dialect.java.AbstractJavaBuilder.generatTemplates(AbstractJavaBuilder.java:110)
at
org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:95)
at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:426)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:284)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:158)
at com.allconnect.viper.rules.RulesFlowProcessor.readRule(RulesFlowProcessor.java:100)
at com.allconnect.viper.rules.RulesFlowProcessor.main(RulesFlowProcessor.java:29)
Which after some digging lead me to :
http://www.nabble.com/having-a-little-problem-when-using-LHS-variable-in-...
And I knew that I should have had a consistent version of Drools, given it all came
packaged together with the Seam download.
I noticed on this the specific JVM listed in the build, and then found the posting
(http://mvel.codehaus.org/Downloading+MVEL) with the
recommendation for the version vs the JVM.
Further digging yielded the 1.6 release. Now I dug thru some archives here, and it's
not clear which version of mvel was in the Seam release (there is no Manifest in the jar
that i have...) So, it is possible that the version I downloaded also upgraded the
version of mvel, which may have been the real problem. I was able to realize that it was
Seam 2.0.0GA which had the issue, and it's resolved in the Seam 2.0.2GA release. I
verified that I can still break the rules with the earlier Seam distribution and it works
properly either with the mval 1.6 compiled version (which is 1.2.23) or the latest from
the current Seam 2.0.2GA release. So, in either case it looks like it's resolved.
The rules are simply ones that do something like this:
rule "CallOpeningWelcome3" ruleflow-group "Welcome"
when
$agent: AgentBean( firstName != null, lastName != null ) &&
$call : IncomingCallBean (extensionCalled == $agent.extension )
then
System.out.println("Welcome to Allconnect, my name is "+$agent.getFirstName()
+ " " +$agent.getLastName() +" and I am here to assist you with your
move.");
end
Where the RHS refers to something from the LHS.
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
5883
days inactive
5884
days old
7 comments
3 participants
participants (3)
-
Christopher Brock (JIRA) -
Earl Baugh (JIRA)
-
Pete Muir (JIRA)