September 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Closed: (SEAMFACES-49) faces-redirect not working with non-transient converations and implicit navigation

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-49?page=com.atlassian.jira.plug... ] Brian Leathem closed SEAMFACES-49. ---------------------------------- Fix Version/s: (was: Future) Resolution: Done > faces-redirect not working with non-transient converations and implicit navigation > ---------------------------------------------------------------------------------- > > Key: SEAMFACES-49 > URL: https://issues.jboss.org/browse/SEAMFACES-49 > Project: Seam Faces > Issue Type: Bug > Components: Conversations > Affects Versions: 3.0.0.Alpha3 > Reporter: Nicklas Karlsson > > if you start a long-running conversation and return a navigation string "foo?faces-redirect=true", there is no navigation > The reason could be that the ConversationAwareViewHandler sees only foo.xhtml and the handler then generates foo.xhtml?cid=666, then at a later stage the original redirect is handled, resulting in foo.xhtml?cid=666?faces-redirect=true -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SEAMFACES-49) faces-redirect not working with non-transient converations and implicit navigation

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-49?page=com.atlassian.jira.plug... ] Brian Leathem reopened SEAMFACES-49: ------------------------------------ Wrong fix version > faces-redirect not working with non-transient converations and implicit navigation > ---------------------------------------------------------------------------------- > > Key: SEAMFACES-49 > URL: https://issues.jboss.org/browse/SEAMFACES-49 > Project: Seam Faces > Issue Type: Bug > Components: Conversations > Affects Versions: 3.0.0.Alpha3 > Reporter: Nicklas Karlsson > Fix For: Future > > > if you start a long-running conversation and return a navigation string "foo?faces-redirect=true", there is no navigation > The reason could be that the ConversationAwareViewHandler sees only foo.xhtml and the handler then generates foo.xhtml?cid=666, then at a later stage the original redirect is handled, resulting in foo.xhtml?cid=666?faces-redirect=true -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFACES-188) CatchExceptionHandler ignores JSF AbortProcessingException

by George Gastaldi (JIRA)

CatchExceptionHandler ignores JSF AbortProcessingException ---------------------------------------------------------- Key: SEAMFACES-188 URL: https://issues.jboss.org/browse/SEAMFACES-188 Project: Seam Faces Issue Type: Bug Reporter: George Gastaldi When an exception is thrown on an actionListener (clicking a link for example), an AbortProcessingException is thrown. However, this exception is ignored on org.jboss.seam.faces.exception.CatchExceptionHandler. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-196) Support for FacesManager

by George Gastaldi (JIRA)

Support for FacesManager ------------------------ Key: SEAMFACES-196 URL: https://issues.jboss.org/browse/SEAMFACES-196 Project: Seam Faces Issue Type: Feature Request Reporter: George Gastaldi It would be nice to have a FacesManager class just like we had in Seam 2, to - allow redirects to another view; - pass parameters as a Map - encode the conversation ID -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (SEAMFACES-195) Removed combined maven module

by Brian Leathem (JIRA)

Removed combined maven module ----------------------------- Key: SEAMFACES-195 URL: https://issues.jboss.org/browse/SEAMFACES-195 Project: Seam Faces Issue Type: Task Components: Build & Distribution Affects Versions: 3.0.2 Reporter: Brian Leathem Fix For: 3.1.0.Beta1 Removed combined maven module, and change the impl artifact to drop the impl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Updated: (SEAMFACES-194) Both Seam Faces and Mojarra have competing ServetContextInitalizers for adding the faces servlet

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-194?page=com.atlassian.jira.plu... ] Brian Leathem updated SEAMFACES-194: ------------------------------------ Fix Version/s: 3.1.0.Beta1 (was: 3.1.0.Beta2) > Both Seam Faces and Mojarra have competing ServetContextInitalizers for adding the faces servlet > ------------------------------------------------------------------------------------------------ > > Key: SEAMFACES-194 > URL: https://issues.jboss.org/browse/SEAMFACES-194 > Project: Seam Faces > Issue Type: Bug > Affects Versions: 3.0.2 > Environment: Java 7, Win 7 > Reporter: Nicklas Karlsson > Assignee: Brian Leathem > Fix For: 3.1.0.Beta1 > > > Effect observed: Intermittent JSF bootstrapping failure on AS7 > JSF automatically adds the faces servlet using a ServetContextInitalizer, as does seam faces. If Seam Faces SCI runs before the JSF one, deployment will fail. This is because of some weirdness in the JSF impl, where it checks is faces is enabled by looking in web.xml for the servlet, and checks if the com.sun.faces.facesInitializerMappingsAdded is set to true (this is set by the Faces SCI when it adds the servlet). > If the faces SCI runs first the JSF SCI will see the servlet as being registered and return, and then the JSF initialiser code will not see the programatically registered servlet and will not bootstrap JSF. > For now a work around would be to have the Seam Faces SCI set the servlet context attribute com.sun.faces.facesInitializerMappingsAdded to true. > Sometimes the application deployment fails with > 10:10:24,371 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/LTK]] (http--127.0.0.1-8080-2) StandardWrapper.Throwable: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.faces.webapp.FacesServlet.init(FacesServlet.java:166) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:188) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at java.lang.Thread.run(Thread.java:722) [:1.7.0] > > 10:10:24,374 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/LTK].[FacesServlet]] (http--127.0.0.1-8080-2) Allocate exception for servlet FacesServlet: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.faces.webapp.FacesServlet.init(FacesServlet.java:166) [jboss-jsf-api_2.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:188) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha1-SNAPSHOT] > at java.lang.Thread.run(Thread.java:722) [:1.7.0] > No further information is display. Sometimes a re-deploy helps, sometimes a reboot of the server, sometimes neither. The application worked fine on AS6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBSEAM-4838) CLONE - Upgrade openid4java in seam dependencies

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4838?page=com.atlassian.jira.plugi... ] Marek Novotny moved JBPAPP-7148 to JBSEAM-4838: ----------------------------------------------- Project: Seam 2 (was: JBoss Enterprise Application Platform) Key: JBSEAM-4838 (was: JBPAPP-7148) Affects Version/s: 2.2.2.Final 2.2.1.Final 2.2.0.GA (was: EAP_EWP 5.1.1) Release Notes Docs Status: (was: Not Required) Release Notes Text: (was: There is security vulnerability in openid4java 0.9.5 and in prior versions too. It required to upgrade to 0.9.6.) Component/s: Security (was: Seam) Security: (was: JBoss Internal) Fix Version/s: 2.3.0.ALPHA (was: EAP_EWP 5.1.2) Docs QE Status: (was: NEW) > CLONE - Upgrade openid4java in seam dependencies > ------------------------------------------------ > > Key: JBSEAM-4838 > URL: https://issues.jboss.org/browse/JBSEAM-4838 > Project: Seam 2 > Issue Type: Task > Components: Security > Affects Versions: 2.2.2.Final, 2.2.1.Final, 2.2.0.GA > Reporter: Marek Novotny > Assignee: Marek Novotny > Priority: Blocker > Fix For: 2.3.0.ALPHA > > > Upgrade openid4java dependency in OpenId integration. The version is affected by security vulnerability reported at http://openid.net/2011/05/05/attribute-exchange-security-alert/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBSEAM-4838) Upgrade openid4java in seam dependencies

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4838?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4838: ---------------------------------- Summary: Upgrade openid4java in seam dependencies (was: CLONE - Upgrade openid4java in seam dependencies) Affects: (was: [Release Notes]) > Upgrade openid4java in seam dependencies > ---------------------------------------- > > Key: JBSEAM-4838 > URL: https://issues.jboss.org/browse/JBSEAM-4838 > Project: Seam 2 > Issue Type: Task > Components: Security > Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final > Reporter: Marek Novotny > Assignee: Marek Novotny > Priority: Blocker > Fix For: 2.3.0.ALPHA > > > Upgrade openid4java dependency in OpenId integration. The version is affected by security vulnerability reported at http://openid.net/2011/05/05/attribute-exchange-security-alert/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-94) NoResultException when attempting to log with an unknown username

by Richard Barabe (JIRA)

NoResultException when attempting to log with an unknown username ----------------------------------------------------------------- Key: SEAMSECURITY-94 URL: https://issues.jboss.org/browse/SEAMSECURITY-94 Project: Seam Security Issue Type: Bug Environment: Ubuntu glassfish 3.1 firefox Reporter: Richard Barabe Priority: Minor Using JPA persistence store. A NoResultException is thrown when attempting to log in with an unknown username. query log : {quote} 295 Query /* */ select identityob0_.id as id14_, identityob0_.name as name14_ from IdentityObjectType identityob0_ where identityob0_.name='USER' limit 2 295 Query /* */ select identityob0_.id as id8_, identityob0_.name as name8_, identityob0_.IDENTITY_OBJECT_TYPE_ID as IDENTITY3_8_ from IdentityObject identityob0_ where identityob0_.name='unknownUserName' and identityob0_.IDENTITY_OBJECT_TYPE_ID=1 limit 2 {quote} see the forum thread [here|http://seamframework.org/Community/SeamsecurityNoResultExceptionWhil...]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3592) Security concerns regarding Seam.Remoting.eval()

by Drew Kutchar (JIRA)

Security concerns regarding Seam.Remoting.eval() ------------------------------------------------ Key: JBSEAM-3592 URL: https://jira.jboss.org/jira/browse/JBSEAM-3592 Project: Seam Issue Type: Task Components: Remoting Reporter: Drew Kutchar Assignee: Shane Bryzak A malicious user can import the seam/remoting/resource/remote.js and use Seam.Remoting.eval() to bypass @WebRemote restrictions and call any arbitrary method? This can be a very serious security hole, even if Seam Remoting is not enabled (by marking any components using @WebRemote). Shane Bryzak stated that he is aware of this issue and has disabled Seam.Remoting.eval() functionality until he finds a way for expression evaluations to honor the @WebRemote annotation. This JIRA is created to track Shane's 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

13 years, 4 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2011