March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1019) Asserted objects should be handled polymorphically

by Christian Bauer (JIRA)

Asserted objects should be handled polymorphically -------------------------------------------------- Key: JBSEAM-1019 URL: http://jira.jboss.com/jira/browse/JBSEAM-1019 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Christian Bauer Class hierarchy: Node(Document,Directory) I'm asserting an instance of Document into working memory like this: <s:link id="editDoc" styleClass="linkNavigation" action="editDoc" accesskey="E" rendered="#{s:hasPermission('NodeHome', 'edit', currentDocument)}"><u>E</u>dit</s:link> This doesn't fire: rule RestrictNodeHomeEditAccess no-loop; activation-group "permissions" when c: PermissionCheck(name == "NodeHome", action == "edit"); Node(nodeWriteAccessLevel : writeAccessLevel, nodeCreator : createdBy) Role(userAccessLevel : name -> (Integer.valueOf(userAccessLevel).intValue() >= nodeWriteAccessLevel.intValue()) ) or User(authenticatedUserId : id -> (nodeCreator.getId().equals(authenticatedUserId)) ) then c.grant(); modify(c); end; This does: rule RestrictNodeHomeEditAccess no-loop; activation-group "permissions" when c: PermissionCheck(name == "NodeHome", action == "edit"); Document(nodeWriteAccessLevel : writeAccessLevel, nodeCreator : createdBy) Role(userAccessLevel : name -> (Integer.valueOf(userAccessLevel).intValue() >= nodeWriteAccessLevel.intValue()) ) or User(authenticatedUserId : id -> (nodeCreator.getId().equals(authenticatedUserId)) ) then c.grant(); modify(c); end; I couldn't find anything in the Drools docs about polymorphism but it looks like Facts are not checked polymorphically. Sad language that is. -- 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

19 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1044) <s:selectDate> JavaScript read field for editing

by Ciro Cavani (JIRA)

<s:selectDate> JavaScript read field for editing ------------------------------------------------ Key: JBSEAM-1044 URL: http://jira.jboss.com/jira/browse/JBSEAM-1044 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.0.GA Reporter: Ciro Cavani For now, the JavaScript code of <s:selectDate> doesn't read input field when showing calendar first time using new date (this is my understand of JavaScript code). The request is read input field for valid date and set it as default: instead: var defaultDate = new Date(); this: var defaultDate = __calendarFactory.parseDateValue(getObject(this.name).value); if (!defaultDate) defaultDate = new Date(); Or something like. I don't know JavaScript, but this work for me. -- 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

19 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-928) Improve year selection in calendar component

by Guy Veraghtert (JIRA)

Improve year selection in calendar component -------------------------------------------- Key: JBSEAM-928 URL: http://jira.jboss.com/jira/browse/JBSEAM-928 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.7.CR1 Reporter: Guy Veraghtert The calendar popup shows the range [selectedYear -10 : selectedYear+10] for the selection of the year. When entering birthdates, this is not very usability friendly. Therefor, give the page developer the ability to specify the first and last year to be shown. -- 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

19 years

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-198) jBPM packaging

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-198?page=comments#action_12355863 ] Pete Muir commented on JBSEAM-198: ---------------------------------- But we need a way of deploying processes in both a development (easy to change) and production (maintain state between application restart). Whats the JBPM take on this? > jBPM packaging > -------------- > > Key: JBSEAM-198 > URL: http://jira.jboss.com/jira/browse/JBSEAM-198 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > > When the jBPM guys come up with some welldefined packaging, we should have a scanner that automagically discovers process and pageflow definitions, instead of having to list these things explicitly. -- 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

19 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-198) jBPM packaging

by Fady Matar (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-198?page=comments#action_12355861 ] Fady Matar commented on JBSEAM-198: ----------------------------------- The packaging of JBPM processes is in the database, I believe we can use a filter or a job scheduler that constantly reads those definition from the jBPM database > jBPM packaging > -------------- > > Key: JBSEAM-198 > URL: http://jira.jboss.com/jira/browse/JBSEAM-198 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > > When the jBPM guys come up with some welldefined packaging, we should have a scanner that automagically discovers process and pageflow definitions, instead of having to list these things explicitly. -- 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

19 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-995) Make it so that spring can be used in Seam Integration/unit tests

by youngm (JIRA)

Make it so that spring can be used in Seam Integration/unit tests ----------------------------------------------------------------- Key: JBSEAM-995 URL: http://jira.jboss.com/jira/browse/JBSEAM-995 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 1.2.0.GA Reporter: youngm Fix For: 1.2.1.GA Currently there isn't really a way to use spring in Seam integration/unit tests. Spring provides support for testing with a super class which sets up spring and seam does the same thing. One easy way to fix this problem is to add a Seam component that installs and sets up a Spring ApplicationContext. That way the Seam super test class can be used and when it starts up the seam container will start up and configure spring. This will also help solve the slight race condition we currently have of the spring integration work being dependent upon Seam already configured. -- 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

19 years

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1028) Namespace uri conflict between Spring NamespaceHander and Seam Component namespace

by youngm (JIRA)

Namespace uri conflict between Spring NamespaceHander and Seam Component namespace ---------------------------------------------------------------------------------- Key: JBSEAM-1028 URL: http://jira.jboss.com/jira/browse/JBSEAM-1028 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 1.2.0.GA Reporter: youngm Fix For: 1.2.1.GA With the addition of a seam namespace with the spring:context-loader they both have a namespace of: http://jboss.com/products/seam/spring Since the spring namespace handler helps use seam in spring I was thinking of changing the spring namespace handler's uri to: http://jboss.com/products/spring/seam with the proposed prefix being seam: And since the component.xml namespace is made to help use spring in seam we would make the seam component namespace uri: http://jboss.com/products/seam/spring with the proposed prefix being spring: This will mean a backwards compatibility change for current users of the spring namespace handler but I think changing the spring namespace handler to spring/seam makes more sense. Any comments or any other ideas on possible namespace uri naming between the 2? Mike -- 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

19 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1018) Allow security checks in component lifecycle methds

by Christian Bauer (JIRA)

Allow security checks in component lifecycle methds --------------------------------------------------- Key: JBSEAM-1018 URL: http://jira.jboss.com/jira/browse/JBSEAM-1018 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Optional The Component.java.callComponentMethod() is used for lifecycle method calling, such as @Create methods. It also wraps all exceptions thrown in these methods, or at least casts them into RuntimeException (even if it already is a RuntimeException). So I can't use Identity.instance.checkPermission() in a @Create method and have my exception handling apply to failure. Minimum required: document this. -- 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

19 years

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1030) AuthorizationException in UPDATE MODEL VALUES is swallowed

by Christian Bauer (JIRA)

AuthorizationException in UPDATE MODEL VALUES is swallowed ---------------------------------------------------------- Key: JBSEAM-1030 URL: http://jira.jboss.com/jira/browse/JBSEAM-1030 Project: JBoss Seam Issue Type: Bug Components: Security Reporter: Christian Bauer Assigned To: Shane Bryzak I'm calling Identity.instance().checkPermission("Node", "setAccessLevel", accessLevel); in one of my setter methods, it's bound to a JSF UI component. The exception is silently swallowed in UPDATE MODEL VALUES and INVOKE APPLICATION continues. Either fix or document. -- 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

19 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1027) UI component for substring/full string display

by Christian Bauer (JIRA)

UI component for substring/full string display ---------------------------------------------- Key: JBSEAM-1027 URL: http://jira.jboss.com/jira/browse/JBSEAM-1027 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor Probably should go into RichFaces (if it isn't already there), noting it here so we won't forget. A nice Javascript component would be a substring display component that expands the string on click. For example, in a datatable column there is only 20 characters space reserved for a particular column. If my data is longer than that, I'd like to show the first 20 characters and allow the user to display/expand the string on click, e.g. "This is a very long varchar that doesn't fit into ...". If the user clicks on "...", either a DHTML layer pops up with the full string or the datatable is actually widened to make room for the full string. -- 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

19 years

2
1
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 March 2007