[
https://issues.jboss.org/browse/SEAMCONFIG-12?page=com.atlassian.jira.plu...
]
Jason Porter moved SEAMXML-36 to SEAMCONFIG-12:
-----------------------------------------------
Project: Seam Config (fixed) (was: Seam Config)
Key: SEAMCONFIG-12 (was: SEAMXML-36)
Workflow: Seam Workflow (was: GIT Pull Request workflow )
Affects Version/s: (was: 3.0.0.CR1)
Fix Version/s: (was: 3.0.0.Final)
princess-rescue example does not work on glassfish 3.1
------------------------------------------------------
Key: SEAMCONFIG-12
URL:
https://issues.jboss.org/browse/SEAMCONFIG-12
Project: Seam Config (fixed)
Issue Type: Bug
Environment: glassfish 3.1
Reporter: Marek Schmidt
Assignee: Stuart Douglas
The princess-rescue example does not work on Glassfish 3.1 with the default profile, it
appear to deploy fine, but any request produces the HTTP 500 Error,
The workaround is to remove
<listener>
<listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>
</listener>
from src/main/webapp/WEB-INF/web.xml
and to package without the default "jetty" profile ( -P-jetty )
A working "glassfish" profile should be created to enable running ftests on
glassfish3.1
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira