January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-500) Special connective "or" constraint

by Michael Neale (JIRA)

Special connective "or" constraint ---------------------------------- Key: JBRULES-500 URL: http://jira.jboss.com/jira/browse/JBRULES-500 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo, Rule Assemply/SPI Reporter: Michael Neale Assigned To: Mark Proctor Would be nice to have some construct like Person(address == null or age < 30) which would kind of short circuit (ideally). Could be done as a special thing with alpha nodes, or another type of join node, or something else. This is a common problem to have for users. -- 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

18 years, 12 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-191) Update CORBA examples

by Mark Little (JIRA)

Update CORBA examples --------------------- Key: JBTM-191 URL: http://jira.jboss.com/jira/browse/JBTM-191 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, JTS Implementation Affects Versions: 4.2.2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.6 The CORBA examples are out-of-date, referring to BOA classes. -- 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

[JBoss JIRA] Created: (JBTM-121) Check recovery

by Mark Little (JIRA)

Check recovery -------------- Key: JBTM-121 URL: http://jira.jboss.com/jira/browse/JBTM-121 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 -- 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

[JBoss JIRA] Created: (JBMESSAGING-725) Add a release-admin check that would cleanly stop the installation process if ant version is too old

by Ovidiu Feodorov (JIRA)

Add a release-admin check that would cleanly stop the installation process if ant version is too old ---------------------------------------------------------------------------------------------------- Key: JBMESSAGING-725 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-725 Project: JBoss Messaging Issue Type: Feature Request Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.CR1 ... and avoid cryptic failures like this one: [C:/temp/jboss-messaging-1.2.0.Beta1/util] ant -f release-admin.xml Buildfile: release-admin.xml default: BUILD FAILED C:\temp\jboss-messaging-1.2.0.Beta1\util\release-admin.xml:36: The following error occurred while ex ecuting this line: C:\temp\jboss-messaging-1.2.0.Beta1\util\release-admin.xml:519: Class org.apache.tools.ant.taskdefs. ConditionTask doesn't support the nested "length" element. Total time: 1 second [C:/temp/jboss-messaging-1.2.0.Beta1/util] ant -version Apache Ant version 1.6.2 compiled on July 16 2004 -- 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
5
0 / 0

[JBoss JIRA] Created: (JBRULES-463) audit log for all system actions

by Michael Neale (JIRA)

audit log for all system actions -------------------------------- Key: JBRULES-463 URL: http://jira.jboss.com/jira/browse/JBRULES-463 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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
5
0 / 0

[JBoss JIRA] Created: (JBAS-3576) Unified Security Context

by Anil Saldhana (JIRA)

Unified Security Context ------------------------ Key: JBAS-3576 URL: http://jira.jboss.com/jira/browse/JBAS-3576 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Currently the roles are an aspect of the Subject that is populated as part of the Jaas Authentication process (in the derivatives of the AbstractServerLoginModule). There is a need for the establishment of a security context to hold the roles, authoriation info etc. -- 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
3
0 / 0

[JBoss JIRA] Created: (SECURITY-11) Principal To Role mapping provider

by Anil Saldhana (JIRA)

Principal To Role mapping provider ---------------------------------- Key: SECURITY-11 URL: http://jira.jboss.com/jira/browse/SECURITY-11 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 We need a mechanism that will allow a user to configure a mapping of principal to roles that need to be added to the security context. -- 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

[JBoss JIRA] Created: (SECURITY-26) Legacy MBeans move back to JBAS/security project for porting

by Anil Saldhana (JIRA)

Legacy MBeans move back to JBAS/security project for porting ------------------------------------------------------------ Key: SECURITY-26 URL: http://jira.jboss.com/jira/browse/SECURITY-26 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 The legacy mbean services like jaassecuritymanagerservice etc need to be retained in the security module of the jbas build for porting customers. This is according to Scott. === The security mbeans really should be back in the jbossas/security as integration code so that the security project is a mc/pojo based set of security aspects. I'm talking about the legacy mbeans which we should keep for porting. === -- 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

[JBoss JIRA] Created: (JBAOP-312) Package retroed deployer for JBoss 4 on jdk1.4

by Kabir Khan (JIRA)

Package retroed deployer for JBoss 4 on jdk1.4 ---------------------------------------------- Key: JBAOP-312 URL: http://jira.jboss.com/jira/browse/JBAOP-312 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan -- 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

[JBoss JIRA] Created: (JBRULES-399) add support for authentication / permissions / ownership

by Michael Neale (JIRA)

add support for authentication / permissions / ownership --------------------------------------------------------- Key: JBRULES-399 URL: http://jira.jboss.com/jira/browse/JBRULES-399 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This authentication/permissions should be tied to the user context that JAAS established. The only things that need to be programmatic are ideally ACLs on a resource. We may need however to show/hide functionality based on the users roles. -- 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
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007