May 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4083) Update ICEfaces jars to 1.8.0 on jboss maven repository

by judy guglielmin (JIRA)

Update ICEfaces jars to 1.8.0 on jboss maven repository ------------------------------------------------------- Key: JBSEAM-4083 URL: https://jira.jboss.org/jira/browse/JBSEAM-4083 Project: Seam Issue Type: Task Components: ICE Faces Integration Environment: ICEfaces example and seam-gen option with ICEfaces to be affected Reporter: judy guglielmin Assignee: judy guglielmin Priority: Blocker Fix For: 2.1.2.CR1 Please let me know when this is done and I will update the build scripts. -- 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

14 years, 8 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4007) Provide an <s:token> UI component to secure JSF forms against cross-site request forgery (XSRF)

by Dan Allen (JIRA)

Provide an <s:token> UI component to secure JSF forms against cross-site request forgery (XSRF) ----------------------------------------------------------------------------------------------- Key: JBSEAM-4007 URL: https://jira.jboss.org/jira/browse/JBSEAM-4007 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.1.1.GA Reporter: Dan Allen Fix For: 2.1.2.GA Introduce the UI component tag <s:token> to secure JSF form posts against cross-site request forgery (XSRF) attacks. Please note that if the solution below is implemented in JSF 2, then Seam does not need to provide a custom solution and this issue can be closed. However, we still need to implement something equivalent for Seam Remoting. The problem today is that when using client-side state saving, a form POST can be crafted (forged) to submit into a JSF application from an external site (cross-site). The serialized view is simply passed in the javax.faces.ViewState parameter. JSF will blindly recreate the view and process the request. Server-side state saving is equally insecure since all the forged POST has to do is provide the identifier of the view state on the server in the javax.faces.ViewState parameter. Actually, this is only a problem since JSF generates sequential identifiers per session in the form j_id + # of views in session. Server-side state saving becomes event more problematic in JSF 2.0 since Facelets' "build during restore" feature is enabled by default. In this case, the javax.faces.ViewState parameter isn't even required since JSF will recreate the view before processing the request. The <s:token> UI component will perform two steps. First, it will assign a unique identifier to the browser using a cookie that lives until the end of the browser session. This is roughly the browser's private key. The <s:token> tag is used inside of an <h:form> and generates a hidden form field named javax.faces.FormSignature. The form signature is calculated as follows: sha1( signature = viewId + "," + formClientId, salt = clientUid ) The developer can also choose to incorporate the session id into this hash for a more secure token (at the cost of binding it to the session) sha1( signature = viewId + "," + formClientId + "," + sessionId, salt = clientUid ) When the form is submitted, the hash is recreated and compared against the value of the javax.faces.FormSignature parameter. -- 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

14 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4014) cannot configure max age of remember me cookie

by Dan Allen (JIRA)

cannot configure max age of remember me cookie ---------------------------------------------- Key: JBSEAM-4014 URL: https://jira.jboss.org/jira/browse/JBSEAM-4014 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.1.GA Reporter: Dan Allen Fix For: 2.1.2.CR1 The configuration for the max age of the remember me cookie got totally messed up. First, the definition of the rememberMe element is missing from security-2.1.xsd. Second, the cookieMaxAge is no longer reachable through the configuration of the rememberMe component. Finally, there is a completely bogus definition of the facesSecurityEvents element, which claims to have a cookie-max-age attribute, when it has no corresponding property. To fix this, there needs to be a cookieMaxAge property on the rememberMe component and the security-2.1.xsd file needs to be updated. -- 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

14 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4034) Using outdated Drools API in documentation example

by Joseph Miller (JIRA)

Using outdated Drools API in documentation example -------------------------------------------------- Key: JBSEAM-4034 URL: https://jira.jboss.org/jira/browse/JBSEAM-4034 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Joseph Miller In section "14.2. Using rules from a Seam component" of the manual, it refers to: policyPricingWorkingMemory.assertObject(policy); policyPricingWorkingMemory.assertObject(customer); This was valid for Drools 3.x. However Seam 2.1.1.GA is using Drools 4.x, which has changed it's API. The equivalent lines are: policyPricingWorkingMemory.insert(policy); policyPricingWorkingMemory.insert(customer); Doc URL: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/drools.html#d0e8296 -- 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

14 years, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4043) seam-gen wrong navigation in icefaces project

by Jozef Hartinger (JIRA)

seam-gen wrong navigation in icefaces project --------------------------------------------- Key: JBSEAM-4043 URL: https://jira.jboss.org/jira/browse/JBSEAM-4043 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.GA Reporter: Jozef Hartinger Assignee: Dan Allen Priority: Minor Fix For: 2.1.2.CR1 1.) Create new ear project and generate entities using database tables from release-process.txt (or any other tables, does not really matter) 2.) Deploy, create some entity and go to the listing page 3.) In the listing page there are two links in the last column of every row - View and Edit The problem is that both these links will get you to the "view entity" page, however Edit link should get you to the edit page (PersonEdit.seam for example) as it does in RichFaces case. -- 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

14 years, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4049) Drools Custom Consequence Exception handlers

by Tihomir Surdilovic (JIRA)

Drools Custom Consequence Exception handlers -------------------------------------------- Key: JBSEAM-4049 URL: https://jira.jboss.org/jira/browse/JBSEAM-4049 Project: Seam Issue Type: Feature Request Components: Drools Affects Versions: 2.1.1.GA Reporter: Tihomir Surdilovic Assignee: Tihomir Surdilovic Allow to specify a custom user defined handler for consequence exceptions in components.xml. For example: <drools:rule-base name="securityRules"> <drools:rule-files><value>/security.drl</value></drools:rule-files> <drools:consequence-exception-handler><value>myCustomHandler</value</drools:consequence-exception-handler> </drools:rule-base> -- 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

14 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4051) Add metawidget examples

by Dan Allen (JIRA)

Add metawidget examples ----------------------- Key: JBSEAM-4051 URL: https://jira.jboss.org/jira/browse/JBSEAM-4051 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.1.2.CR1 Adopt the Seam metawidget examples from the metawidget examples distribution into the examples directory (booking, groovybooking, dvdstore). Use the same build strategy by copying the source from original example into a staging directory and then overwriting the files that differ. That way, maintenance is kept to a minimum. -- 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

14 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4052) correct the meaning of debug mode

by Dan Allen (JIRA)

correct the meaning of debug mode --------------------------------- Key: JBSEAM-4052 URL: https://jira.jboss.org/jira/browse/JBSEAM-4052 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.2.CR1 It's not entirely clear what debug mode means in Seam. On the one hand, it activates the hot deploy filter. On the other hand, it activates the Seam debug page. The reality is, these should be different settings. There may be other uses of debug mode as well and these should be clearly defined and cataloged in the documentation. -- 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

14 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4065) Dynamic Web Project with Seam in Eclipse defaults to old version rather than newer version

by Jeff Wexler (JIRA)

Dynamic Web Project with Seam in Eclipse defaults to old version rather than newer version ------------------------------------------------------------------------------------------ Key: JBSEAM-4065 URL: https://jira.jboss.org/jira/browse/JBSEAM-4065 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.GA Environment: Windows 2003 server, 4GB memory, eclipse-jee-ganymede-SR2-win32.zip, JBossTools-ALL-win32-3.0.0.GA-R200903141626-H5.zip, PostgreSQL 8.3.7 JDBC Driver 8.3-604.jdbc4 Reporter: Jeff Wexler Priority: Minor Created a new project with configuration of Dynamic Web Project with Seam 2.1 (technology preview). Then select New project again to create another seam project. Configuration defaults to Dynamic Web Project with Seam 1.2 rather than 2.0 or 2.1. I would assume that the default should be to either the previously selected one (2.1) or to one of the later versions (2.0 or 2.1). -- 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

14 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4066) captureCurrentView on redirect should capture all request parameters

by Dan Allen (JIRA)

captureCurrentView on redirect should capture all request parameters -------------------------------------------------------------------- Key: JBSEAM-4066 URL: https://jira.jboss.org/jira/browse/JBSEAM-4066 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.2.0.CR1 Attachments: JBSEAM-4066-trunk-v1.txt When the captureCurrentRequest() method was deprecated and replaced by captureCurrentView(), the behavior changed such that page parameters were being saved instead of request parameters. I'm fine with the idea of preserving page parameters based on how they were bound to the model on the way into the page, but I also think that arbitrary request parameters need to be captured. Otherwise, the redirect back to the current view will in many cases be incomplete and thus fail. The logic I propose is to capture the request parameters and then override the values with the values from the page parameters (giving page parameters the precedence). However, long term, we should also consider the fact that multi-value parameters are not being preserved. Likely they should be captured as well, but there is a lack of infrastructure to support them. -- 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

14 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2009