[seam-issues] [JBoss JIRA] (JBSEAM-4918) Cannot deploy Seam project generated in JBDS - other problems
[
https://issues.jboss.org/browse/JBSEAM-4918?page=com.atlassian.jira.plugi...
]
Daniel Hinojosa commented on JBSEAM-4918:
-----------------------------------------
The ear works when I run it an external browser...but this message comes up in JBT.
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jdt.internal.compiler.env.INameEnvironment from [Module
"deployment.seewhatisee-ear.ear:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
... 77 more
{noformat}
Cannot deploy Seam project generated in JBDS - other problems
-------------------------------------------------------------
Key: JBSEAM-4918
URL: https://issues.jboss.org/browse/JBSEAM-4918
Project: Seam 2
Issue Type: Bug
Components: Tools
Affects Versions: 2.3.0.BETA1, 2.3.0.BETA2
Environment: JBDS 5.0 Beta1, Seam 2.3.0.Beta1, JBoss AS7.1.0.Final
Reporter: Tomas Remes
Assignee: Daniel Hinojosa
Labels: seam-gen
Fix For: 2.3.0.CR1
There are some next following problems when trying to deploy Seam project war generated
in JBDS. First is the war missing WEB-INF/lib/dom4j.jar, which produces
java.lang.ClassNotFoundException: org.dom4j.DocumentException. Second is that there
probably shouldn't be any com.sun.facelets.FaceletViewHandler configuration in
faces-config.xml, because it causes java.lang.ClassNotFoundException:
com.sun.facelets.FaceletViewHandler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira