June 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4225) Allow to add eventListeners to WorkingMemory

by Tihomir Surdilovic (JIRA)

Allow to add eventListeners to WorkingMemory -------------------------------------------- Key: JBSEAM-4225 URL: https://jira.jboss.org/jira/browse/JBSEAM-4225 Project: Seam Issue Type: Feature Request Reporter: Tihomir Surdilovic Add support to add eventListeners to WorkingMemory. -- 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

16 years, 2 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4149) Copy/paste is broken

by Christian Bauer (JIRA)

Copy/paste is broken -------------------- Key: JBSEAM-4149 URL: https://jira.jboss.org/jira/browse/JBSEAM-4149 Project: Seam Issue Type: Bug Components: Wiki Affects Versions: 2.1.2.CR1 Reporter: Christian Bauer Assignee: Christian Bauer For whatever reason, copy/paste of WikiFiles is broken. The tests run but it doesn't work on the UI, no error message... -- 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

16 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4188) Add decision table support to org.jboss.seam.drools.RuleBase

by Tihomir Surdilovic (JIRA)

Add decision table support to org.jboss.seam.drools.RuleBase ------------------------------------------------------------- Key: JBSEAM-4188 URL: https://jira.jboss.org/jira/browse/JBSEAM-4188 Project: Seam Issue Type: Feature Request Reporter: Tihomir Surdilovic Currently org.jboss.seam.drools.RuleBase only allows for use of drl (and additional dsl) files. Add support to be able to also add decision tables (xls). -- 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

16 years, 2 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4214) Upgrade to Drools 5

by Pete Muir (JIRA)

Upgrade to Drools 5 ------------------- Key: JBSEAM-4214 URL: https://jira.jboss.org/jira/browse/JBSEAM-4214 Project: Seam Issue Type: Feature Request Components: Drools Reporter: Pete Muir Assignee: Marek Novotny Priority: Blocker Fix For: 2.2.0.CR1 -- 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

16 years, 2 months

2
2
0 / 0

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

by Paul Chan (JIRA)

CLONE -captureCurrentView on redirect should capture all request parameters --------------------------------------------------------------------------- Key: JBSEAM-4236 URL: https://jira.jboss.org/jira/browse/JBSEAM-4236 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Paul Chan Assignee: Dan Allen Fix For: 2.1.2.CR1 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

16 years, 2 months

5
8
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

16 years, 2 months

2
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

16 years, 2 months

3
2
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

16 years, 2 months

3
4
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

16 years, 2 months

3
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

16 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2009