[JBoss JIRA] Created: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
8:13 p.m.
Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest
release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Pavol Pitonak
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 p.m.
New subject: [JBoss JIRA] Assigned: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Pavol Pitonak reassigned RFPL-1493:
-----------------------------------
Assignee: Ján Jamrich (was: Pavol Pitonak)
Unlike AS6, AS7 does not contain JSF 1.x jars. Investigate if AS7 is able to run JSF 1.x
applications.
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Pavol Pitonak edited comment on RFPL-1493 at 6/13/11 8:54 AM:
--------------------------------------------------------------
Unlike AS6, AS7 does not contain JSF 1.x jars. Investigate if AS7 is able to run JSF 1.x
applications. Try both JSF 1.x and 2.x of RichFaces demo.
was (Author: ppitonak):
Unlike AS6, AS7 does not contain JSF 1.x jars. Investigate if AS7 is able to run JSF
1.x applications.
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1493:
-----------------------------------
I have tried replace JSF module by jars with JSF 1.2, but still get error on deploy
telling that WEB-INF/classes/META-INF is not valid folder/structure.
According to http://community.jboss.org/wiki/JSFOnAS7, there is not direct support for
JSF1.2, and I was not able make existing RF3.x example working correctly
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:48 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Pavol Pitonak commented on RFPL-1493:
-------------------------------------
RichFaces 3.3.3.Final supports JSF2, do not run the demo with JSF 1.2.
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1493:
-----------------------------------
RichFaces demo (richfaces-demo) from 3.3.3.Final (built without any special profile, e.g.
with JSF1.2) failed on deploy to JBoss AS 7 (final) with following error:
15:24:40,093 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.deployment.unit."richfaces-demo.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."richfaces-demo.war".PARSE: Failed to process phase PARSE
of deployment "richfaces-demo.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_19]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_19]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_19]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse "/content/richfaces-demo.war/WEB-INF/jboss-web.xml"
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[6,2]
Message: Unexpected element 'class-loading' encountered
at
org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at
org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182)
at
org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 6 more
15:24:40,097 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2)
Deployment of "richfaces-demo.war" was rolled back with failure message
{"Failed services" =>
{"jboss.deployment.unit.\"richfaces-demo.war\".PARSE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"richfaces-demo.war\".PARSE: Failed to process phase
PARSE of deployment \"richfaces-demo.war\""}}
15:24:40,972 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped
deployment richfaces-demo.war in 874ms
15:24:40,974 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1)
{"Composite operation failed and was rolled back. Steps that failed:" =>
{"Operation step-2" => {"Failed services" =>
{"jboss.deployment.unit.\"richfaces-demo.war\".PARSE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"richfaces-demo.war\".PARSE: Failed to process phase
PARSE of deployment \"richfaces-demo.war\""}}}}
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1493:
-----------------------------------
Without jboss-web.xml (built without any special profiles, deploy to JBoss AS7) is
application deployed correctly, but following error appear when attempt access
richfaces-demo application (opening appropriate URL):
15:52:57,898 INFO [org.jboss.web] (MSC service thread 1-1) registering web context:
/richfaces-demo
15:52:57,962 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2)
Deployed "richfaces-demo.war"
15:53:22,503 SEVERE [org.ajax4jsf.webapp.BaseXMLFilter] (http--127.0.0.1-8080-3) Exception
in the filter chain: javax.servlet.ServletException: Illegal attempt to set ViewHandler
after a response has been rendered.
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:325)
[jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
[richfaces-impl-3.3.3.Final.jar:]
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jsp.index_jsp._jspService(index_jsp.java:60)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
[jboss-as-web-7.0.0.Final.jar:7.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_19]
Caused by: java.lang.IllegalStateException: Illegal attempt to set ViewHandler after a
response has been rendered.
at com.sun.faces.application.ApplicationImpl.setViewHandler(ApplicationImpl.java:563)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at org.jboss.seam.jsf.SeamApplication.setViewHandler(SeamApplication.java:376)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at
org.richfaces.ui.application.StateApplication.setViewHandler(StateApplication.java:464)
[richfaces-ui-3.3.3.Final.jar:]
at org.ajax4jsf.event.InitPhaseListener.beforePhase(InitPhaseListener.java:92)
[richfaces-impl-3.3.3.Final.jar:]
at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
[jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
... 46 more
15:53:22,506 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/richfaces-demo].[Faces
Servlet]] (http--127.0.0.1-8080-3) Servlet.service() for servlet Faces Servlet threw
exception: java.lang.IllegalStateException: Illegal attempt to set ViewHandler after a
response has been rendered.
at com.sun.faces.application.ApplicationImpl.setViewHandler(ApplicationImpl.java:563)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at org.jboss.seam.jsf.SeamApplication.setViewHandler(SeamApplication.java:376)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at
org.richfaces.ui.application.StateApplication.setViewHandler(StateApplication.java:464)
[richfaces-ui-3.3.3.Final.jar:]
at org.ajax4jsf.event.InitPhaseListener.beforePhase(InitPhaseListener.java:92)
[richfaces-impl-3.3.3.Final.jar:]
at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
[jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
[richfaces-impl-3.3.3.Final.jar:]
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jsp.index_jsp._jspService(index_jsp.java:60)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
[jboss-as-web-7.0.0.Final.jar:7.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_19]
15:53:22,519 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/richfaces-demo].[jsp]]
(http--127.0.0.1-8080-3) Servlet.service() for servlet jsp threw exception:
java.lang.IllegalStateException: Illegal attempt to set ViewHandler after a response has
been rendered.
at com.sun.faces.application.ApplicationImpl.setViewHandler(ApplicationImpl.java:563)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at org.jboss.seam.jsf.SeamApplication.setViewHandler(SeamApplication.java:376)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at
org.richfaces.ui.application.StateApplication.setViewHandler(StateApplication.java:464)
[richfaces-ui-3.3.3.Final.jar:]
at org.ajax4jsf.event.InitPhaseListener.beforePhase(InitPhaseListener.java:92)
[richfaces-impl-3.3.3.Final.jar:]
at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
[jsf-impl-2.0.4-b09-jbossorg-4.jar:2.0.4-b09-jbossorg-4]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
[jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
[richfaces-impl-3.3.3.Final.jar:]
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
[richfaces-impl-3.3.3.Final.jar:]
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
[org.jboss.seam-jboss-seam-2.2.0.GA.jar:]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jsp.index_jsp._jspService(index_jsp.java:60)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
[jboss-as-web-7.0.0.Final.jar:7.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_19]
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Jay Balunas commented on RFPL-1493:
-----------------------------------
Just last week we found out that AS7 did ship with Mojarra 1.2 support. This was a
surprise to me.
Please see
http://community.jboss.org/blogs/marek-novotny/2011/07/15/seam-2-jpa-exam...
for more details.
RichFaces 3.3.3.Final should work with JSF 2.0 as is, but it also must be verified with
this change for Mojarra 1.2
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1493:
-----------------------------------
Following instructions from Marek Novotny's blogpost it is possible (and quite easy)
to run RichFaces Live demo on JBoss AS7.
The required steps are:
1. remove jboss-web.xml from WEF-INF lib
2. add jboss-deployment-structure.xml with following configuration:
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="javax.faces.api" slot="main"/>
<module name="com.sun.jsf-impl" slot="main"/>
</exclusions>
<dependencies>
<module name="javax.faces.api" slot="1.2"/>
<module name="com.sun.jsf-impl" slot="1.2"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
Configuration is quite self-explaining since in javax.faces.api module are slots
"main" and "1.2" and for com.sun.jsf-impl the same.
Thanks for link, this way to switch JSF version is really useful. My bad that I didn't
learn how to manage slots in modules before I started with this JIRA, I had tried to
change impl in completely wrong way :(
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:45 p.m.
New subject: [JBoss JIRA] Resolved: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich resolved RFPL-1493.
-------------------------------
Resolution: Done
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 a.m.
New subject: [JBoss JIRA] Commented: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1493:
-----------------------------------
A bit more difficult was configuration RF-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RF-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RF-3.3.3.Final demo, build with Mojarra 1.2, then following steps
should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Pavol Pitonak edited comment on RFPL-1493 at 8/22/11 9:53 AM:
--------------------------------------------------------------
A bit more difficult was configuration RF-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RF-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RF-3.3.3.Final demo, build with Mojarra 1.2, then following steps
should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
5.) Add following option to WEB-INF/web.xml (this is mentioned in doc[1] as required for
MyFaces, but for AS7 you need do it as well)
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
was (Author: jjamrich):
A bit more difficult was configuration RF-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RF-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RF-3.3.3.Final demo, build with Mojarra 1.2, then following steps
should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [JBoss JIRA] (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Brian Leathem updated RFPL-1493:
--------------------------------
Forum Reference: http://community.jboss.org/message/637739
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 p.m.
New subject: [JBoss JIRA] (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Brian Leathem edited comment on RFPL-1493 at 11/23/11 5:52 PM:
---------------------------------------------------------------
A bit more difficult was configuration RichFaces-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RichFaces-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RichFaces-3.3.3.Final demo, build with Mojarra 1.2, then
following steps should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
5.) Add following option to WEB-INF/web.xml (this is mentioned in doc[1] as required for
MyFaces, but for AS7 you need do it as well)
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
was (Author: jjamrich):
A bit more difficult was configuration RichFaces-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RichFaces-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RF-3.3.3.Final demo, build with Mojarra 1.2, then following steps
should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
5.) Add following option to WEB-INF/web.xml (this is mentioned in doc[1] as required for
MyFaces, but for AS7 you need do it as well)
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 p.m.
New subject: [JBoss JIRA] (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Brian Leathem edited comment on RFPL-1493 at 11/23/11 5:51 PM:
---------------------------------------------------------------
A bit more difficult was configuration RichFaces-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RichFaces-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RF-3.3.3.Final demo, build with Mojarra 1.2, then following steps
should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
5.) Add following option to WEB-INF/web.xml (this is mentioned in doc[1] as required for
MyFaces, but for AS7 you need do it as well)
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
was (Author: jjamrich):
A bit more difficult was configuration RF-3.3.3.Final with JSF 2.0
There was useful documentation [1] for RF-3.3.x with JSF2 as well.
To get richfaces-demo (3.3.3.Final) working on JBoss AS7, following steps are need to be
done:
1.) if richfaces-demo build with "jsf2_0" profile, remove JSF impl and api
(jsf-impl-2.0.2.jar and jsf-api-2.0.2.jar)
if you have default RF-3.3.3.Final demo, build with Mojarra 1.2, then following steps
should be done:
- remove JSF (1.2) impl and api jars
- replace richfaces-impl-3.3.3.Final.jar by richfaces-impl-jsf2-3.3.3.Final.jar
2.) remove WEB-INF/jboss-web.xml according to [2]: Create or modify files that control
class loading in AS7
3.) according to doc[1], make sure that following context params are set in
WEB-INF/web.xml (should be done by default)
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
4.) Add following option to WEB-INF/faces-config.xml (this is mentioned in doc[1] as
required for MyFaces, but for AS7 you need do it as well)
<application>
<view-handler>org.ajax4jsf.application.AjaxViewHandler</view-handler>
</application>
5.) Add following option to WEB-INF/web.xml (this is mentioned in doc[1] as required for
MyFaces, but for AS7 you need do it as well)
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
[1] http://community.jboss.org/wiki/RichFaces333AndJSF20
[2]
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 a.m.
New subject: [JBoss JIRA] (RFPL-1493) Test deployment, and execution of RichFaces 3.3.3.Final component demo on the latest release of AS7
[
https://issues.jboss.org/browse/RFPL-1493?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1493:
-----------------------------------
Deploy richfaces-demo.war updated according to previous comments to JBoss AS 7.1 causes
another exception:
javax.servlet.ServletException: Servlet execution threw an exception
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:295)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:373)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:500)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
org.apache.jsp.index_jsp._jspService(index_jsp.java:60)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
root cause
java.lang.StackOverflowError
org.jboss.seam.interop.jul.Log4JConversionFilter.getLogger(Log4JConversionFilter.java:163)
org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:64)
org.jboss.logmanager.Logger.logRaw(Logger.java:640)
org.jboss.logmanager.Logger.log(Logger.java:600)
org.jboss.logmanager.Logger.log(Logger.java:612)
org.jboss.logmanager.log4j.BridgeLogger.info(BridgeLogger.java:84)
org.jboss.seam.interop.jul.Log4JConversionFilter.logWithoutThrowable(Log4JConversionFilter.java:139)
org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:72)
org.jboss.logmanager.Logger.logRaw(Logger.java:640)
org.jboss.logmanager.Logger.log(Logger.java:600)
org.jboss.logmanager.Logger.log(Logger.java:612)
org.jboss.logmanager.log4j.BridgeLogger.info(BridgeLogger.java:84)
org.jboss.seam.interop.jul.Log4JConversionFilter.logWithoutThrowable(Log4JConversionFilter.java:139)
It is caused by infinite loop trying to convert logger into JUL type logger. Since JBoss
AS 7.1 has jul logger bridge builtin, there is no longer needed include jboss-seam-jul in
deployed app. So one more step is required to run richfaces-demo.war updated by steps
above: remove jboss-seam-jul*.jar from WEB-INF/lib.
Test deployment, and execution of RichFaces 3.3.3.Final component
demo on the latest release of AS7
---------------------------------------------------------------------------------------------------
Key: RFPL-1493
URL: https://issues.jboss.org/browse/RFPL-1493
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone1
We need to make sure there are no issue with running RichFaces 3.3.3.Final version of the
component demo on the latest AS7
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4465
days inactive
4763
days old
richfaces-planning-issues@lists.jboss.org
15 comments
5 participants
participants (5)
-
Brian Leathem (Issue Comment Edited) (JIRA) -
Brian Leathem (Updated) (JIRA)
-
Jay Balunas (JIRA)
-
Ján Jamrich (JIRA)
-
Pavol Pitonak (JIRA)