[JBoss JIRA] Created: (SEAMXML-36) princess-rescue example does not work on glassfish 3.1
by Marek Schmidt (JIRA)
princess-rescue example does not work on glassfish 3.1
------------------------------------------------------
Key: SEAMXML-36
URL: https://issues.jboss.org/browse/SEAMXML-36
Project: Seam Config
Issue Type: Bug
Affects Versions: 3.0.0.CR1
Environment: glassfish 3.1
Reporter: Marek Schmidt
Fix For: 3.0.0.Final
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
14 years, 11 months
[JBoss JIRA] Created: (SEAMXML-40) Problem when parsing seam-beans.xml in seam-booking on WebSphere v8
by Denis Forveille (JIRA)
Problem when parsing seam-beans.xml in seam-booking on WebSphere v8
-------------------------------------------------------------------
Key: SEAMXML-40
URL: https://issues.jboss.org/browse/SEAMXML-40
Project: Seam Config
Issue Type: Bug
Affects Versions: 3.0.0.CR4
Environment: WebSphere v8 beta
Reporter: Denis Forveille
I receive this exception when I trfy to start the seam booking app (in CR3) on WebSphere v8
java.lang.Exception: Could not resolve node specializes in namespace urn:java:seam:core at file:/data/ws/ws_seam3/Test2Web/WebContent/WEB-INF/classes/META-INF/seam-beans.xml:28
at org.jboss.seam.config.xml.bootstrap.XmlConfigExtension.beforeBeanDiscovery(XmlConfigExtension.java:135)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:276)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (SEAMXML-39) princess-rescue - fails to deploy on GlassFish
by Jozef Hartinger (JIRA)
princess-rescue - fails to deploy on GlassFish
----------------------------------------------
Key: SEAMXML-39
URL: https://issues.jboss.org/browse/SEAMXML-39
Project: Seam Config
Issue Type: Bug
Affects Versions: 3.0.0.CR4
Environment: GlassFish 3.1 + latest Weld SNAPSHOT
Reporter: Jozef Hartinger
Priority: Critical
Fix For: 3.0.0.Final
The application deploys without a problem. On an initial load, the application fails with the following exception.
[#|2011-03-24T09:32:41.382+0100|SEVERE|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=108;_ThreadName=Thread-1;|WebModule[/princess-rescue]PWC1322: Error invoking requestDestroyed method on ServletRequestListener org.jboss.weld.environment.servlet.Listener
java.lang.NullPointerException
at org.jboss.weld.context.AbstractBoundContext.deactivate(AbstractBoundContext.java:81)
at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:115)
at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestDestroyed(ForwardingServletListener.java:42)
at org.apache.catalina.core.StandardContext.fireRequestDestroyedEvent(StandardContext.java:4588)
at org.apache.catalina.core.StandardHostValve.postInvoke(StandardHostValve.java:243)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:328)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
|#]
[#|2011-03-24T09:32:41.597+0100|WARNING|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=109;_ThreadName=Thread-1;|StandardWrapperValve[Faces Servlet]: PWC1406: Servlet.service() for servlet Faces Servlet threw exception
java.lang.IllegalStateException: Context is already active
at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:311)
at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:110)
at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:84)
at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:113)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:409)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
|#]
[#|2011-03-24T09:32:41.627+0100|SEVERE|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=109;_ThreadName=Thread-1;|WebModule[/princess-rescue]PWC1322: Error invoking requestDestroyed method on ServletRequestListener org.jboss.weld.environment.servlet.Listener
java.lang.NullPointerException
at org.jboss.weld.context.AbstractBoundContext.deactivate(AbstractBoundContext.java:81)
at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:115)
at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestDestroyed(ForwardingServletListener.java:42)
at org.apache.catalina.core.StandardContext.fireRequestDestroyedEvent(StandardContext.java:4588)
at org.apache.catalina.core.StandardHostValve.postInvoke(StandardHostValve.java:243)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:328)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Updated: (JBSEAM-4802) SEAM Entity creator uses Integer for @Version - results in NullPointerException on update
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-4802?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBSEAM-4802:
----------------------------------------
Description:
When creating entities from scratch, the seam-gen new entity will generate code with the the following:
@Version
private Integer version;
This construct unfortunately results in new records being created with NULL in the version column. On subsequent updates this then results in NullPointerException.
Changing Integer to int solves the problem.
was:
When creating entities from scratch, the "Create SEAM Entity" wizard will generate code with the the following:
@Version
private Integer version;
This construct unfortunately results in new records being created with NULL in the version column. On subsequent updates this then results in NullPointerException.
Changing Integer to int solves the problem.
> SEAM Entity creator uses Integer for @Version - results in NullPointerException on update
> -----------------------------------------------------------------------------------------
>
> Key: JBSEAM-4802
> URL: https://issues.jboss.org/browse/JBSEAM-4802
> Project: Seam 2
> Issue Type: Bug
> Components: Tools
> Environment: JBDS4
> Reporter: Peter Larsen
>
> When creating entities from scratch, the seam-gen new entity will generate code with the the following:
> @Version
> private Integer version;
> This construct unfortunately results in new records being created with NULL in the version column. On subsequent updates this then results in NullPointerException.
> Changing Integer to int solves the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (SEAMFACES-124) Create section that explains how to setup JSF
by Dan Allen (JIRA)
Create section that explains how to setup JSF
---------------------------------------------
Key: SEAMFACES-124
URL: https://issues.jboss.org/browse/SEAMFACES-124
Project: Seam Faces
Issue Type: Feature Request
Components: Documentation
Affects Versions: 3.0.0.Final
Reporter: Dan Allen
Priority: Minor
Fix For: 3.0.1
A section titled "How to setup JSF in a Java EE 6 webapp" would be good for the refguide, because it's funny how poorly this is documented.
to activate jsf, you need one of three things
1. seam-faces jar (that sets up jsf for you)
2. if not #1, you need empty faces-config.xml (root element only, can't be blank)
3. if not #1 or #2, you need web.xml w/ the Faces Servlet defined
mention the schema versions required, such as the one for faces-config.xml and web.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months