[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3323) JPA example on Tomcat 6.X throws a IllegalStateException: Cannot load WEB-INF/classes/org/jboss/seam/example/jpa/Hotel.class
by Jay Balunas (JIRA)
JPA example on Tomcat 6.X throws a IllegalStateException: Cannot load WEB-INF/classes/org/jboss/seam/example/jpa/Hotel.class
----------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3323
URL: https://jira.jboss.org/jira/browse/JBSEAM-3323
Project: Seam
Issue Type: Bug
Components: Examples, Platform interoperability
Affects Versions: 2.1.0.BETA1
Reporter: Jay Balunas
Fix For: 2.1.0.BETA2
When deploying the JPA example without embedded I see the exception below.
I have added the hsql.jar file to tomcat, and deployed the war from the "dist-tomcat6" directory. I do not believe it is related, but the instructions in the readme say to deploy the war in "dist-jboss" which does not exist. This is probably a typo. Just to be sure I did attempt to deploy the war in the "dist-jboss" but it failed with other errors because it does not package all the right jars.
SEVERE: 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: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
org.apache.catalina.loader.StandardClassLoader@12a54f9
(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:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1215)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
at java.lang.Thread.run(Thread.java:595)
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3329) security validation error in jbtools generated project for rule-based-permission-resolver element
by Jay Balunas (JIRA)
security validation error in jbtools generated project for rule-based-permission-resolver element
-------------------------------------------------------------------------------------------------
Key: JBSEAM-3329
URL: https://jira.jboss.org/jira/browse/JBSEAM-3329
Project: Seam
Issue Type: Bug
Components: Security, Tools
Affects Versions: 2.1.0.BETA1
Reporter: Jay Balunas
Fix For: 2.1.0.BETA2
I have created a seam runtime from 2.1.0.BETA1, and used it to generate a EAR and WAR projects. In each the components.xml is showing an error in the jboss tools.
The projects seems to compile, deploy, and execute fine. This may just be a missing element, that does not effect runtime.
The error is "cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'security:rule-based-permission-resolver'." and shows on the "<security:rule-based-permission-resolver security-rules="#{securityRules}"/>" line of the components.xml.
I checked the "security-2.1.xsd" both online and locally in the distribution (just in case it needed updating online), but this element "rule-based-permission-resolver" is not there.
because this does not seem to cause a runtime problem this is only a major.
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3340) StatusMessages: addition of ConfigRedirectHandler messages is broken
by Wolfgang Schwendt (JIRA)
StatusMessages: addition of ConfigRedirectHandler messages is broken
--------------------------------------------------------------------
Key: JBSEAM-3340
URL: https://jira.jboss.org/jira/browse/JBSEAM-3340
Project: Seam
Issue Type: Bug
Environment: Seam 2.1.0 Rev 8823
Reporter: Wolfgang Schwendt
XML schema Pages-2.1.xsd allows the specification of an error message for any declared exception handler:
Example:
<exception class="org.jboss.seam.framework.EntityNotFoundException">
<end-conversation/>
<redirect view-id="/error.xhtml">
<message>#{messages['notFoundMsg']}</message>
</redirect>
</exception>
Right now as of Seam 2.1.0 Rev 8823, however, the error message is not added to the FacesContext, whereas with previous versions of Seam the functionality worked fine. org.jboss.seam.exception.RedirectHandler is not the problem. The bug is in org.jboss.seam.international.StatusMessages.
StatusMessages.add(Severity severity, String messageTemplate, Object... params) calls StatusMessages.add(severity, null, null, messageTemplate, null, params), setting the key-Parameter (resourceBundleKey) to null.
The implementation of StatusMessages.add(Severity severity, String key, String detailKey, String messageTemplate, String messageDetailTemplate, final Object... params) checks whether the key is empty.
if (!Strings.isEmpty(key)) ...
But because the supplied key is null, the error message is never added to the FacesContext! Further, there is another bug in the logic which calls the message interpolation.
--
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
17 years, 7 months