February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-428) Access Control List - each node to be protected

by Michael Neale (JIRA)

Access Control List - each node to be protected ------------------------------------------------ Key: JBRULES-428 URL: http://jira.jboss.com/jira/browse/JBRULES-428 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Rule nodes (at least) need to have an ACL: what groups can access it in what capacity. First need to have a structure for ACLs to be stored. They should be tied to user groups/roles, not individual logins. JAAS should provide the user name and the users context (group membership) I believe. When there is an ACL, it must be checked to see if the user (via their group membership) can do one of the following: Edit, change status, view, delete. If they can't view, ideally it will not be shown in any "lists", but if that is not feasable, it would be acceptable to list it, but not show the contents. -- 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

14 years, 1 month

6
13
0 / 0

[JBoss JIRA] Created: (JBRULES-433) decision table editor

by Michael Neale (JIRA)

decision table editor --------------------- Key: JBRULES-433 URL: http://jira.jboss.com/jira/browse/JBRULES-433 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale A grid based decision table editor. Can be based on the concepts in 3.0.4 decision tables. Obviously, this entails a grid, with the ability to add rows, columns and shuffle data along. It also needs a "header" area where rule snippets are setup, like the excel equivalent. -- 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

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-429) Rule meta data viewer/editor

by Michael Neale (JIRA)

Rule meta data viewer/editor ---------------------------- Key: JBRULES-429 URL: http://jira.jboss.com/jira/browse/JBRULES-429 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Need to have a meta-data editor that is rule specific (including dublin core, but also perhaps rule attributes). Does not include documentation (that will be a seperate editor). -- 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

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-411) JBRMS Front End - parent task

by Michael Neale (JIRA)

JBRMS Front End - parent task ----------------------------- Key: JBRULES-411 URL: http://jira.jboss.com/jira/browse/JBRULES-411 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale This is the parent task for BRMS front end activities (which use the drools-repository component). No work should be done directly on this issue, only subtasks. -- 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

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-412) Create web app component infrastructure

by Michael Neale (JIRA)

Create web app component infrastructure --------------------------------------- Key: JBRULES-412 URL: http://jira.jboss.com/jira/browse/JBRULES-412 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Using Seam, or otherwise, need a "back end" web component framework which will work with the GWT generated UI, and use the drools-repository api. This task is just to setup the initial skeleton for development -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1108) Re-factor WSRPProducer to extract a MetaData interface

by Chris Laprun (JIRA)

Re-factor WSRPProducer to extract a MetaData interface ------------------------------------------------------ Key: JBPORTAL-1108 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1108 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.DR1, 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Alpha1 Methods pertaining to registration, cookies and session expiration should all be part of the MetaData... -- 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

14 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1250) Optimize access to service description

by Chris Laprun (JIRA)

Optimize access to service description -------------------------------------- Key: JBPORTAL-1250 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1250 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Producer information code still tries to access service too many times. Should add a transaction-like concept during which the service description would stay valid since for a single operation it is currently possible to request the service description several times (when cache is not used)... -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1109) WSRP integration API

by Julien Viet (JIRA)

WSRP integration API -------------------- Key: JBPORTAL-1109 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1109 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha1 Reporter: Julien Viet Assigned To: Chris Laprun Fix For: 2.6.Alpha1 -- 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

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1106) Find a way to prevent re-generation of Service Description for each call

by Chris Laprun (JIRA)

Find a way to prevent re-generation of Service Description for each call ------------------------------------------------------------------------ Key: JBPORTAL-1106 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1106 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.DR1, 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.Alpha1 A way to do it would be to be able to listen to portlet deployment inside the server. This way, we could mark the service description as dirty when a new remotable portlet is deployed and only re-generate the service description when it is dirty. -- 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

14 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1016) Allow creation and deployment of WSRP portlets from descriptors

by Chris Laprun (JIRA)

Allow creation and deployment of WSRP portlets from descriptors --------------------------------------------------------------- Key: JBPORTAL-1016 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1016 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.4.1 Final Right now, the only way to deploy WSRP portlets is via the management portlet. We should be able to do this via the descriptors. Proposed solution is to evolve the -wsrp.xml file to accomodate portlet definition. -- 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

14 years, 1 month

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007