[ https://jira.jboss.org/jira/browse/JBSEAM-3323?page=com.atlassian.jira.pl... ] Jay Balunas updated JBSEAM-3323: -------------------------------- Summary: JPA example on Tomcat 6.X and glassfish throws a IllegalStateException: Cannot load WEB-INF/classes/org/jboss/seam/example/jpa/Hotel.class (was: JPA example on Tomcat 6.X throws a IllegalStateException: Cannot load WEB-INF/classes/org/jboss/seam/example/jpa/Hotel.class) Glassfish has this issue as well - below is the exception that it throws. [#|2008-08-26T09:40:49.794-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=Thread-25;_RequestID=4522727b-9181-4f03-9463-8f6b9b4e8587;|WebModule[/jboss-seam-jpa]PWC1275: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.IllegalStateException: Cannot load WEB-INF/classes/org/jboss/seam/example/jpa/Hotel.class from WebappClassLoader delegate: true repositories: /WEB-INF/classes/ ----------> Parent Classloader: EJBClassLoader : urlSet = [] doneCalled = false Parent -> java.net.URLClassLoader@8dcd5d (using getResourceAsStream() returned null) at org.jboss.seam.deployment.AbstractDeploymentHandler.getClassFile(AbstractDeploymentHandler.java:41) at org.jboss.seam.deployment.ComponentDeploymentHandler.handle(ComponentDeploymentHandler.java:57) at org.jboss.seam.deployment.DeploymentStrategy.handle(DeploymentStrategy.java:177) at org.jboss.seam.deployment.AbstractScanner.handleItem(AbstractScanner.java:30) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:141) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137) at org.jboss.seam.deployment.URLScanner.scanDirectories(URLScanner.java:40) at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:107) at org.jboss.seam.init.Initialization.create(Initialization.java:113) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523) at org.apache.catalina.core.StandardContext.start(StandardContext.java:5184) at com.sun.enterprise.web.WebModule.start(WebModule.java:326) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222) at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182) at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278) at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:974) at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:961) at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:464) at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176) at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308) at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226) at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298) at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635) at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:744) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358) at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90) at $Proxy1.invoke(Unknown Source) at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304) at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174) at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:145) at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:537) at java.lang.Thread.run(Thread.java:595) |#] [#|2008-08-26T09:40:49.795-0500|SEVERE|sun-appserver9.1|org.apache.catalina.core.StandardContext|_ThreadID=17;_ThreadName=Thread-25;_RequestID=4522727b-9181-4f03-9463-8f6b9b4e8587;|PWC1306: Startup of context /jboss-seam-jpa failed due to previous errors|#] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3323?page=com.atlassian.jira.pl... ] Pete Muir closed JBSEAM-3323. ----------------------------- Resolution: Done Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3323?page=com.atlassian.jira.pl... ] Yannick Lazzari commented on JBSEAM-3323: ----------------------------------------- I did a diff between the sources of BETA1 and the nightly build of September 11th and if what I found is the fix for this problem, I think there still might be some issues. First of all, I see that it's now hardcoded to exclude the folders "WEB-INF/classes/*" and "/WEB-INF/classes/*" when scanning the war root. Doesn't that effectively prevent to have any Seam components deployed in those folders because they're going to be skipped in the whole scanning process? I guess the workaround would be to always have your components in an archive in the WEB-INF/lib folder but I don't understand the limitation. Plus, I wanted to try the Wicket integration and I had the same problem with the classes that are deployed in the "WEB-INF/wicket" folder. Should that folder be added to the list of excluded folders as well? Maybe the solution would be to refactor the way the AbstractDeploymentHandler turns filenames into class names (static method filenameToClassname). Instead of ignoring the folders, we could simply remove the "WEB-INF/classes", "/WEB-INF/classes" or "WEB-INF/wicket" prefix from the file name before turning it into a class name. I'm using Glassfish too by the way. Is this an application server specific problem? I guess I could write my own deployment handler and find a way to override Seam's default ComponentDeploymentHandler but I'm sure other people could benefit from this. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira