February 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4637) Seam does not work with JSF 2.0 faces-config.xml

by Ryan Nideffer (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBSEAM-4637 URL: https://jira.jboss.org/jira/browse/JBSEAM-4637 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR1 Reporter: Ryan Nideffer I am attempting to use JSF 2.0 in my Seam application for, among other benefits, composite components. I am able to upgrade the jsf-api.jar and jsf-impl.jar, remove jsf-facelets.jar and my application functions fine, however I am still running in JSF 1.2 mode due to this faces-config.xml: <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> According to thread comments from a Mojarra developer and the Release Notes for Mojarra 2, all thats needed is to remove the view-handler and reference v2.0 in faces-config. http://forums.java.net/jive/message.jspa?messageID=373539 https://javaserverfaces.dev.java.net/nonav/rlnotes/2.0.1/releasenotes.html As soon as I do this though, I get the following exception when my application is deployed: 2010-04-16 11:24:18,249 INFO [javax.enterprise.resource.webcontainer.jsf.config] (Thread-2) Unsanitized stacktrace from failed start... javax.faces.view.facelets.FaceletException: Must have a Constructor that takes in a ComponentConfig at com.sun.faces.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.<init>(AbstractTagLibrary.java:289) ... Caused by: java.lang.NoSuchMethodException: org.jboss.seam.ui.handler.CommandButtonParameterComponentHandler.<init>(javax.faces.view.facelets.ComponentConfig) at java.lang.Class.getConstructor0(Class.java:2706) According to Dan Allen, Seam 2 and JSF 2 work together beautifully: http://seamframework.org/Documentation/DoesSeamWorkWithJSF2 -- 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

12 years, 4 months

7
17
0 / 0

[JBoss JIRA] Created: (JBSEAM-4667) Using JSF 2 And Seam - conversation Id

by varun shaji (JIRA)

Using JSF 2 And Seam - conversation Id -------------------------------------- Key: JBSEAM-4667 URL: https://jira.jboss.org/browse/JBSEAM-4667 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Environment: JBoss-6.0 M2 , Seam 2.2.0 & Seam 2.2.1 CR1, JSF 2(Mojarro - 2.0.2) Reporter: varun shaji During Postback from a JSF page , the conversation id cannot be retored. The debug logs that i obtained for JSF 1.2 and JSF 2.0 are as shown for the same postback in a pageflow are as shown JSF 1.2 ******************************************************************************************************************** 06-15@23:18:50 (JbpmContextInfo.java:145) DEBUG - creating jbpm context with service factories '[]' 06-15@23:18:50 (JbpmContext.java:124) DEBUG - creating org.jbpm.JbpmContext@7b3555 06-15@23:18:50 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello 06-15@23:18:50 (GraphElement.java:170) DEBUG - event 'process-start' on 'ProcessDefinition(hello)' for 'Token(/)' 06-15@23:18:50 (JbpmContext.java:133) DEBUG - closing jbpmContext org.jbpm.JbpmContext@7b3555 ******************************************************************************************************* JSF 2.0 ********************************************************************************************** 06-15@22:38:27 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello ********************************************************************************************** I debuged and found the FacesPage from which the conversation Id is returning..Is returning null in JSF2 ..ConversationId is returning null in FacesPage returned by Seam when Using JSF2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3020) Links to seam and gsg of jbosstools

by Svetlana mukhina (JIRA)

Links to seam and gsg of jbosstools ----------------------------------- Key: JBSEAM-3020 URL: http://jira.jboss.com/jira/browse/JBSEAM-3020 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Svetlana mukhina Assigned To: Michael Yuan Priority: Optional Looking through the guide http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/index.html I've found a chapter http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/gettingstartedwi... that overlapping with some of our guides - http://docs.jboss.org/tools/2.1.0.CR1/en/seam/publish/en-US/html/index.html and http://docs.jboss.org/tools/2.1.0.CR1/en/GettingStartedGuide/publish/en-U..., maybe it will be good to add links in the chapter referring to these 2 guides where a user could find more information on the topic? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3971) Documentation to run under Websphere should contain information about Websphere 6.1 and Websphere 7.0

by Julien Kronegg (JIRA)

Documentation to run under Websphere should contain information about Websphere 6.1 and Websphere 7.0 ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3971 URL: https://jira.jboss.org/jira/browse/JBSEAM-3971 Project: Seam Issue Type: Feature Request Components: Documentation Issues Environment: Trunk documentation http://fisheye.jboss.org/browse/Seam/trunk/doc/Seam_Reference_Guide/en-US... Reporter: Julien Kronegg Priority: Minor Until Seam 2.1.1.GA, the documentation gives information about running examples under Websphere 6.1: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/websphere.html In the latest version (future 2.1.2.GA?), the documentation gives information about running examples under Websphere 7.0. The (valuable) documentation about running under WAS 6.1 is gone. It would be cool to add a sentence such as: "Information about other Websphere version can be found in previous Seam release documentation: - [Websphere 6.1=>http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/websphere.html]" This has the advantage to give useful information to Websphere users without having to much documentation content to add/rewrite. -- 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

12 years, 4 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing

by Arsen Torbarina (JIRA)

HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing -------------------------------------------------------------------------------- Key: JBSEAM-4454 URL: https://jira.jboss.org/jira/browse/JBSEAM-4454 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1 Reporter: Arsen Torbarina Fix For: 2.2.1.CR1 Method org.jboss.seam.persistence.PersistenceProvider.init() (including its subclass' method HibernatePersistenceProvider.init()) never gets executed, because it is annotated with @org.jboss.seam.annotations.intercept.PostConstruct instead of @javax.ejb.PostConstruct. -- 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

12 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-18) @Transactional not inherited in larger hierarchies

by Stephan Pabinger (JIRA)

@Transactional not inherited in larger hierarchies -------------------------------------------------- Key: SEAMPERSIST-18 URL: https://issues.jboss.org/browse/SEAMPERSIST-18 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Beta2 Environment: JBoss 6.0.0.Final, Seam Persistence 3.0.0.Beta2 Reporter: Stephan Pabinger I am using the following hierarchy: ClassA (abstract) inherited by ClassB (abstract) inherited by ClassC ClassA - injects a Seam-Managed Persistence Context as described in (http://docs.jboss.org/seam/3/persistence/latest/reference/en-US/html/pers...) - performs em.joinTransaction() in a method that is annotated with @Transactional ClassB - just extends ClassA (nothing added) ClassC - extends ClassB - is annotated with @Named When I call #{classC.joinTransaction} I get the following exception: [1]. When inheriting ClassC directly from ClassA the method is called just fine. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-45) Allow fine grained control of seam managed transactions

by Stuart Douglas (JIRA)

Allow fine grained control of seam managed transactions ------------------------------------------------------- Key: SEAMFACES-45 URL: https://jira.jboss.org/browse/SEAMFACES-45 Project: Seam Faces Issue Type: Feature Request Components: Transactions & Persistence Reporter: Stuart Douglas Seam managed transactions should be controllable on a per view basis, e.g. you should be able to turn them on for /app/crud/* and off for /app/complexpages/* Also we should look at the possibility of having a 'partially on' mode where seam only manages the transaction in the render response phase, and leaves the app to manage its own transaction for the rest of the lifecycle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-29) Support Seam Managed Transactions over Multiple Requests

by Lincoln Baxter III (JIRA)

Support Seam Managed Transactions over Multiple Requests -------------------------------------------------------- Key: SEAMFACES-29 URL: https://jira.jboss.org/browse/SEAMFACES-29 Project: Seam Faces Issue Type: Feature Request Components: Transactions & Persistence Reporter: Lincoln Baxter III Seam should support Managed Transactions (Java EE EntityManager, or HibernateSession) via an abstraction provided in the new persistence module. Goals: -- Allow declarative enabling/disabling of managed transactions. -- Multi-transactional JSF lifecycle, use transaction from Before Restore View to before Render Response, then another from before Render Response to after Render Response. http://docs.jboss.com/seam/2.2.0.GA/en-US/html_single/#persistence.seam-m... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

5
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4639) In JSF2, Seam sets JSF view Id to null for postback requests

by Alex Savitsky (JIRA)

In JSF2, Seam sets JSF view Id to null for postback requests ------------------------------------------------------------ Key: JBSEAM-4639 URL: https://jira.jboss.org/jira/browse/JBSEAM-4639 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.0.GA Environment: JSF 2 RI (Mojarra) v.2.0.2.FCS Reporter: Alex Savitsky Priority: Critical Run attached test-bug-2.2.1.war (I've been using Tomcat 6.0, but any web container will do). Access index.jsf in the context root (usually http://localhost:your-startup-port/your-context-root/index.jsf) and click the "Add" button. Note the exception, and also note the debug output in the system console: Before phase RESTORE_VIEW 1, view id = N/A (no root) After phase RESTORE_VIEW 1, view id = /index.xhtml Before phase RENDER_RESPONSE 6, view id = /index.xhtml TestBean created After phase RENDER_RESPONSE 6, view id = /index.xhtml Before phase RESTORE_VIEW 1, view id = N/A (no root) After phase RESTORE_VIEW 1, view id = null Before phase APPLY_REQUEST_VALUES 2, view id = null After phase APPLY_REQUEST_VALUES 2, view id = null Before phase PROCESS_VALIDATIONS 3, view id = null After phase PROCESS_VALIDATIONS 3, view id = null Before phase UPDATE_MODEL_VALUES 4, view id = null After phase UPDATE_MODEL_VALUES 4, view id = null Before phase INVOKE_APPLICATION 5, view id = null After phase INVOKE_APPLICATION 5, view id = null The very same setup without Seam (test-bug-clean.war, with no Seam JAR in WEB-INF/lib, and with Seam commented out in web.xml) has the button working (validation messages appear) as well as different debug output: Before phase RESTORE_VIEW 1, view id = N/A (no root) After phase RESTORE_VIEW 1, view id = /index.xhtml Before phase RENDER_RESPONSE 6, view id = /index.xhtml TestBean created After phase RENDER_RESPONSE 6, view id = /index.xhtml Before phase RESTORE_VIEW 1, view id = N/A (no root) After phase RESTORE_VIEW 1, view id = /index.xhtml Before phase APPLY_REQUEST_VALUES 2, view id = /index.xhtml After phase APPLY_REQUEST_VALUES 2, view id = /index.xhtml Before phase PROCESS_VALIDATIONS 3, view id = /index.xhtml After phase PROCESS_VALIDATIONS 3, view id = /index.xhtml Before phase RENDER_RESPONSE 6, view id = /index.xhtml After phase RENDER_RESPONSE 6, view id = /index.xhtml The debug phase listener source can be found in /WEB-INF/classes/test/TestListener.java -- 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

12 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4652) Using JSF 2 And Seam

by browny browny (JIRA)

Using JSF 2 And Seam -------------------- Key: JBSEAM-4652 URL: https://jira.jboss.org/browse/JBSEAM-4652 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR1, 2.2.0.GA Environment: JBoss-5.1.0 AS , Seam 2.2.0 & Seam 2.2.1 CR1, JSF 2(Mojarro - 2.0.2) Reporter: browny browny When using PageFlow with JSF 2.0 during transition from one page to another i get an excption :: javax.servlet.ServletException javax.faces.webapp.FacesServlet.service(FacesServlet.java:325) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) 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.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.lang.NullPointerException org.jboss.seam.document.DocumentStorePhaseListener.beforePhase(DocumentStorePhaseListener.java:38) com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) 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.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) The same example works fine with JSF 1.2.But with JSF 2.0 i get the same exception for Seam 2.2.0 and 2.2.1 Anyhow i get the seam variables resolved and application succeefuly deployed with JSF 2.0 but this error during page transition occurs. I use pageflow (jbpm-jpdl.jar) for stateful navigation. Any clues?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

7
20
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2011