January 2011 - seam-issues - Jboss List Archives

[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, 4 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, 4 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, 4 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, 4 months

7
20
0 / 0

[JBoss JIRA] Created: (SEAMINTL-13) Support Java 6 ResourceBundle.Control

by Nicklas Karlsson (JIRA)

Support Java 6 ResourceBundle.Control ------------------------------------- Key: SEAMINTL-13 URL: https://jira.jboss.org/browse/SEAMINTL-13 Project: Seam i18n Issue Type: Feature Request Components: Messages Affects Versions: 3.0.0.Alpha1 Reporter: Nicklas Karlsson It would be nice to support ResourceBundle.Control so you could easily implement e.g. DB backed RB:s, timeouts etc. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4528) static pages don't work at all with database down and XA datasource used

by deanhiller (JIRA)

static pages don't work at all with database down and XA datasource used ------------------------------------------------------------------------ Key: JBSEAM-4528 URL: https://jira.jboss.org/jira/browse/JBSEAM-4528 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: postgres or oracle with postgres or oracle XADatasource. postgres jdbc driver is fine while oracle driver is not Reporter: deanhiller Priority: Critical If this is a hibernate bug, please report hibernate issue and ticket here as other seam users will run into this problem and it looks like a seam framework problem(or at least could be solved in seam but it may be possible to solve in hibernate too and could be solved in each and every driver datasource as well). Steps to reproduce 1. start up the jboss 5.1.0 with latest seam 2. pull your internet connection so the db is gone 3. have all your customers go to a static page like /web/error.xhtml RESULT: jboss goes to it's knees as users in IE end up in infinite redirects to your server causing more and more load on the server. The drivers talk to the database when they should not be. I have a work around proxy driver for oracle's jdbc driver. I do not however have a fix for oracle's datasource or postgres datasource. I imagine someone could write a proxy datasource that would solve this problem for all people, hibernate, seam and all xa drivers. I will attach logs of postgres xa driver and oracle one but basically they are trying to open a connection to database when ANY http request comes in until waiting to see if we actually do any select statements or updates or inserts. For some reason, the postgres driver and oracle driver where fine here...they did not make db requests when an http request came in. The oracle driver however did make a request to the db when commit is called even if no sql was done against the db where postgres driver ignored the commit since no sql was done. I will try to attach files or more comments here. PLEASE if you report a tic in hibernate put it in here for others to find when they hit this issue. keyphrases: seam doesn't work when database goes down seam infinite redirect on db outage database failure causes seam to not work -- 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

2
11
0 / 0

[JBoss JIRA] Created: (SEAMFACES-44) View scope problems

by Aleksandar Pejovic (JIRA)

View scope problems ------------------- Key: SEAMFACES-44 URL: https://jira.jboss.org/browse/SEAMFACES-44 Project: Seam Faces Issue Type: Bug Affects Versions: 3.0.0.Alpha3 Environment: glassfish v3.0.1 Reporter: Aleksandar Pejovic 1.View scope should behave like normal scope, but client proxies aren't being used. 2.View scoped beans should be passivation capable, but the container isn't enforcing that. 3.@ViewScoped annotation cannot be used on producer methods/fields. More detailed description is available on a forum: http://seamframework.org/Community/SeamfacesViewScopeProblems -- 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

9
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011