[
https://issues.jboss.org/browse/SEAMFORGE-221?page=com.atlassian.jira.plu...
]
Michael Schuetz edited comment on SEAMFORGE-221 at 6/16/11 7:46 AM:
--------------------------------------------------------------------
Cheers, deployment succeeds now.
After deploying manually, i tried
http://localhost:9990/{projectname}/faces/scaffold/{entity}/view.xhtml without success. Is
URL correct?
Deployed application ist not listed here:
http://localhost:9999/console/
Yes, i know this is not a forum - just would promote this question as i can't find any
hints for that.
Would appreciate documentation for deploying against as7:
https://docs.jboss.org/author/display/SEAMFORGE/Reference+Guide
thanks
was (Author: michaelschuetz):
Cheears, deployment succeeded now.
After deploying manually, i tried
http://localhost:9990/{projectname}/faces/scaffold/{entity}/view.xhtml without success. Is
URL correct?
Deployed application ist not listed here:
http://localhost:9999/console/
Would appreciate documentation for deploying against as7:
https://docs.jboss.org/author/display/SEAMFORGE/Reference+Guide
thanks
ClassNotFoundException when Deploying against AS7
-------------------------------------------------
Key: SEAMFORGE-221
URL:
https://issues.jboss.org/browse/SEAMFORGE-221
Project: Seam Forge
Issue Type: Bug
Environment: mac os, Boss AS 7.0.0.Beta3, forge-1.0.0.Alpha4
Reporter: Michael Schuetz
created simple project, one entity and scaffold and got exception during deploying
manually against AS/:
3:08:16,720 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) Starting
deployment of "xyz.war"
23:08:16,758 WARN [org.jboss.vfs] (MSC service thread 1-1) VFS was unable to set the
URLStreamHandlerFactory. This will have unpredictable results
23:08:16,833 WARN [org.jboss.as.server.deployment.module] (MSC service thread 1-1)
META-INF directory /content/xyz.war/WEB-INF/classes/META-INF ignored as it is not a valid
location for META-INF
23:08:17,376 INFO [org.jboss.jpa] (MSC service thread 1-14) read persistence.xml for
forge-default
23:08:17,453 INFO [org.jboss.weld] (MSC service thread 1-4) Processing CDI deployment:
xyz.war
23:08:17,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001:
Failed to start service jboss.deployment.unit."xyz.war".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."xyz.war".INSTALL: Failed to process phase INSTALL of
deployment "xyz.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.lang.NoClassDefFoundError: org/springframework/context/MessageSource
at java.lang.Class.getDeclaredFields0(Native Method) [:1.6.0_24]
at java.lang.Class.privateGetDeclaredFields(Class.java:2291) [:1.6.0_24]
at java.lang.Class.getDeclaredFields(Class.java:1743) [:1.6.0_24]
at
org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:53)
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:65)
at
org.jboss.as.ee.component.AbstractComponentDescription.prepareComponentConfiguration(AbstractComponentDescription.java:392)
at
org.jboss.as.ee.component.AbstractComponentDescription.createComponentConfiguration(AbstractComponentDescription.java:363)
at
org.jboss.as.ee.component.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:104)
at
org.jboss.as.ee.component.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:67)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
Caused by: java.lang.ClassNotFoundException: org.springframework.context.MessageSource
from [Module "deployment.xyz.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184)
[jboss-modules.jar:1.0.0.Beta17]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357)
[jboss-modules.jar:1.0.0.Beta17]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329)
[jboss-modules.jar:1.0.0.Beta17]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306)
[jboss-modules.jar:1.0.0.Beta17]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100)
[jboss-modules.jar:1.0.0.Beta17]
... 14 more
23:08:17,858 INFO [org.jboss.as.server] (MSC service thread 1-14) Service status report
New missing/unsatisfied dependencies:
service jboss.deployment.unit."xyz.war".beanmanager (missing)
service jboss.naming.context.java.comp.xyz.xyz.CustomerBean (missing)
service jboss.naming.context.java.module.xyz.xyz (missing)
Services which failed to start:
service jboss.deployment.unit."xyz.war".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."xyz.war".INSTALL: Failed to process phase INSTALL of
deployment "xyz.war"
23:08:17,874 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) Stopped
deployment xyz.war in 13ms
23:08:17,874 INFO [org.jboss.as.server] (MSC service thread 1-11) Service status report
Newly corrected services:
service jboss.deployment.unit."xyz.war".beanmanager (no longer required)
service jboss.naming.context.java.comp.xyz.xyz.CustomerBean (no longer required)
service jboss.naming.context.java.module.xyz.xyz (no longer required)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira