[
http://jira.jboss.com/jira/browse/JBSEAM-2936?page=comments#action_12411481 ]
Jay Balunas commented on JBSEAM-2936:
-------------------------------------
From email (judy guglielmin):
As to the mvel.jar (that's what it is referred to in <seam distr
path>/seam-gen/icefaces/build-scripts/deployed-jars-ear.list (or war.list)
I see that the non-ICEfaces one was changed (in seam-gen/build-scripts) but the mirror of
that in the icefaces directory was not. Is it too late for me to change it (I think I
have privilege for that directory?). When I last checked they were both the same, but I
guess the non-ICEfaces one was changed since then.
Both lists (ear and war) should reflect the change from mvel.jar to mvel14.jar and the
proper jar will be copied into the generated application's library. Previously both
mvel.jar and mvel14.jar were copied.
Icefaces seam-gen build scripts need to be updated for mvel.jar
changes
-----------------------------------------------------------------------
Key: JBSEAM-2936
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2936
Project: Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 2.0.2.CR2
Reporter: Jay Balunas
Assigned To: judy guglielmin
Fix For: 2.0.2.GA
Attachments: icefaces-access-error-server.log
Icefaces seam-gen ear application is showing a seam debug/error page. See the attached
file for full stack trace.
The error's root cause appears to be: "NoClassDefFoundError:
org/mvel/integration/impl/LocalVariableResolverFactory". Because this is similiar to
an error you can get if using jars that have had testing modifications made I have have
done the following (always clearing both the JBoss deployment and project for each step):
- cleaned and rebuilt 2.0.2.CR2 dist then recreated project - No change
- copied original 2.0.2.CR2 dist for backup then cleaned the tagged source code -
cleared my .m2 cache - and rebuilt the whole dist.
- recreated the icefaces app
- got the same error.
I also tested seam gen with EAR and WAR projects that did not use icefaces and there were
no issues.
--
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