July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBAS-3278) Securitymgr tests failure (jboss-head) - MDBUnitTestCase doesnt cleanup deployments

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3278?page=all ] Anil Saldhana closed JBAS-3278. ------------------------------- This should be fixed as the MDBUnitTestCase has been synched up with the version in Branch_4_0. Test passes locally. > Securitymgr tests failure (jboss-head) - MDBUnitTestCase doesnt cleanup deployments > ------------------------------------------------------------------------------------ > > Key: JBAS-3278 > URL: http://jira.jboss.com/jira/browse/JBAS-3278 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Rajesh Rajasekaran > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta > > > To verify: > jboss-head/testsuite ant tests-security-manager > org.jboss.test.securitymgr.test.MDBUnitTestCase deploys cts.jar but doesnt cleanup. > This causes the following tests to fail. > org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase > org.jboss.test.securitymgr.test.StatelessSessionUnitTestCase > org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase > with the following error: > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:service=Topic,name=testTopic > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) > at org.jboss.system.ServiceController.install(ServiceController.java:226) > When org.jboss.test.securitymgr.test.MDBUnitTestCase is removed from the suite the above tests pass. > http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-1.5/2006... -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3278) Securitymgr tests failure (jboss-head) - MDBUnitTestCase doesnt cleanup deployments

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3278?page=comments#action_12339395 ] Anil Saldhana commented on JBAS-3278: ------------------------------------- Sacha is the culprit. http://fisheye.jboss.com/viewrep/JBoss/jbosstest/src/main/org/jboss/test/... > Securitymgr tests failure (jboss-head) - MDBUnitTestCase doesnt cleanup deployments > ------------------------------------------------------------------------------------ > > Key: JBAS-3278 > URL: http://jira.jboss.com/jira/browse/JBAS-3278 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Rajesh Rajasekaran > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta > > > To verify: > jboss-head/testsuite ant tests-security-manager > org.jboss.test.securitymgr.test.MDBUnitTestCase deploys cts.jar but doesnt cleanup. > This causes the following tests to fail. > org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase > org.jboss.test.securitymgr.test.StatelessSessionUnitTestCase > org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase > with the following error: > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:service=Topic,name=testTopic > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) > at org.jboss.system.ServiceController.install(ServiceController.java:226) > When org.jboss.test.securitymgr.test.MDBUnitTestCase is removed from the suite the above tests pass. > http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-1.5/2006... -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3278) Securitymgr tests failure (jboss-head) - MDBUnitTestCase doesnt cleanup deployments

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3278?page=all ] Anil Saldhana resolved JBAS-3278. --------------------------------- Resolution: Done The test was trying to additionally deploy "test-destinations-full-service.xml" when the cts.jar, the archive that is part of this test, contained this service.xml. Hence the attempt to duplicate registration. I commented out the deployment of the service.xml in the testcase. > Securitymgr tests failure (jboss-head) - MDBUnitTestCase doesnt cleanup deployments > ------------------------------------------------------------------------------------ > > Key: JBAS-3278 > URL: http://jira.jboss.com/jira/browse/JBAS-3278 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Rajesh Rajasekaran > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta > > > To verify: > jboss-head/testsuite ant tests-security-manager > org.jboss.test.securitymgr.test.MDBUnitTestCase deploys cts.jar but doesnt cleanup. > This causes the following tests to fail. > org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase > org.jboss.test.securitymgr.test.StatelessSessionUnitTestCase > org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase > with the following error: > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:service=Topic,name=testTopic > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) > at org.jboss.system.ServiceController.install(ServiceController.java:226) > When org.jboss.test.securitymgr.test.MDBUnitTestCase is removed from the suite the above tests pass. > http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-1.5/2006... -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBADMCON-145) Need to download 'htmlunit' from jboss repository instead of sourceforge

by Charles Crouch (JIRA)

[ http://jira.jboss.com/jira/browse/JBADMCON-145?page=comments#action_12339391 ] Charles Crouch commented on JBADMCON-145: ----------------------------------------- The steer from Ruel was to add the necessary jars for the new version of html unit to the repo using the standard process. Then update build/build-thirdparty.xml to include them. You can then reference the jars from the regular build.xml. You can ping him directly at ruel.loehr(a)jboss.com or via the build forus. > Need to download 'htmlunit' from jboss repository instead of sourceforge > ------------------------------------------------------------------------ > > Key: JBADMCON-145 > URL: http://jira.jboss.com/jira/browse/JBADMCON-145 > Project: JBoss Admin Console > Issue Type: Task > Components: General Console > Affects Versions: 1.1 alpha > Environment: build environment > Reporter: walkerrl > Assigned To: walkerrl > Fix For: 1.1 alpha > > Original Estimate: 1 day > Time Spent: 2 days > Remaining Estimate: 1 day > > Currently, I am downloading the htmlunit binaries from sourceforge. Need to change 'build.xml' to get same from the jboss repository. > ( see related thread in "design of the jboss build system" forum @ http://www.jboss.com/index.html?module=bb&op=viewtopic&t=81061 "Request: access to htmlunit from jboss repository", and the reply from ryan). -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JGRP-252) TCP_NIO support is impacted by a Sun Java bug during TCP_NIO shutdown operation

by Scott Marlow (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-252?page=all ] Scott Marlow closed JGRP-252. ----------------------------- Sun will fix for the jdk 1.5.0_08 release. > TCP_NIO support is impacted by a Sun Java bug during TCP_NIO shutdown operation > ------------------------------------------------------------------------------- > > Key: JGRP-252 > URL: http://jira.jboss.com/jira/browse/JGRP-252 > Project: JGroups > Issue Type: Sub-task > Affects Versions: 2.4 > Environment: Novell Linux Desktop > Linux smarlow 2.6.5-7.243-default #1 Mon Dec 5 21:08:42 UTC 2005 i686 i686 i386 GNU/Linux > Reporter: Scott Marlow > Assigned To: Scott Marlow > Priority: Minor > Attachments: config.txt, sendernio.sh, tcp_nio.xml > > > During TCP_NIO, I used to ignore exceptions thrown while closing connections at shutdown time. I changed this for the 2.4 release, however, there seems to be a Java bug that Sun just fixed in Mustang build 89. I verified that the Sun fix works by downloading jdk-6-rc-bin-b89-linux-i586-22_jun_2006.bin from http://download.java.net/jdk6/binaries/ and running the org.jgroups.tests.perf.Test. I asked my support contact at Sun if they could also fix this bug in the Java 5 release, I'll update this bug when I hear the answer. > I created this Jira to track the issue since others will likely see the same problem. When Sun reports back their plans for a Java5 fix, I'll update this Jira. The Sun bug id is supposed to be 6445262 but I cannot seem to find that on the Java bug parade (perhaps its marked private.) > Run the attached script files to recreate. > The stack trace below shows that the unexpected error occurs when we attempt to close the channel (socket connection): > SEVERE: error closing socket connection > java.io.IOException: Invalid argument > at sun.nio.ch.NativeThread.signal(Native Method) > at sun.nio.ch.SocketChannelImpl.implCloseSelectableChannel(SocketChannelImpl.java:634) > at java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel(AbstractSelectableChannel.java:201) > at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:97) > at org.jgroups.blocks.ConnectionTableNIO$Connection.closeSocket(ConnectionTableNIO.java:913) > at org.jgroups.blocks.ConnectionTableNIO$Connection.destroy(ConnectionTableNIO.java:880) > at org.jgroups.blocks.ConnectionTableNIO.stop(ConnectionTableNIO.java:312) > at org.jgroups.protocols.TCP_NIO.stop(TCP_NIO.java:71) > at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:604) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:514) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.Discovery.down(Discovery.java:333) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:395) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:480) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:283) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.VIEW_SYNC.down(VIEW_SYNC.java:166) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:797) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:385) > at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:324) > at org.jgroups.JChannel._close(JChannel.java:1286) > at org.jgroups.JChannel.shutdown(JChannel.java:492) > at org.jgroups.tests.perf.transports.JGroupsTransport.stop(JGroupsTransport.java:59) > at org.jgroups.tests.perf.Test.stop(Test.java:208) > at org.jgroups.tests.perf.Test.main(Test.java:705) -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JGRP-252) TCP_NIO support is impacted by a Sun Java bug during TCP_NIO shutdown operation

by Scott Marlow (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-252?page=all ] Scott Marlow resolved JGRP-252. ------------------------------- Resolution: Done Sun will fix for the jdk 1.5.0_08 release. > TCP_NIO support is impacted by a Sun Java bug during TCP_NIO shutdown operation > ------------------------------------------------------------------------------- > > Key: JGRP-252 > URL: http://jira.jboss.com/jira/browse/JGRP-252 > Project: JGroups > Issue Type: Sub-task > Affects Versions: 2.4 > Environment: Novell Linux Desktop > Linux smarlow 2.6.5-7.243-default #1 Mon Dec 5 21:08:42 UTC 2005 i686 i686 i386 GNU/Linux > Reporter: Scott Marlow > Assigned To: Scott Marlow > Priority: Minor > Attachments: config.txt, sendernio.sh, tcp_nio.xml > > > During TCP_NIO, I used to ignore exceptions thrown while closing connections at shutdown time. I changed this for the 2.4 release, however, there seems to be a Java bug that Sun just fixed in Mustang build 89. I verified that the Sun fix works by downloading jdk-6-rc-bin-b89-linux-i586-22_jun_2006.bin from http://download.java.net/jdk6/binaries/ and running the org.jgroups.tests.perf.Test. I asked my support contact at Sun if they could also fix this bug in the Java 5 release, I'll update this bug when I hear the answer. > I created this Jira to track the issue since others will likely see the same problem. When Sun reports back their plans for a Java5 fix, I'll update this Jira. The Sun bug id is supposed to be 6445262 but I cannot seem to find that on the Java bug parade (perhaps its marked private.) > Run the attached script files to recreate. > The stack trace below shows that the unexpected error occurs when we attempt to close the channel (socket connection): > SEVERE: error closing socket connection > java.io.IOException: Invalid argument > at sun.nio.ch.NativeThread.signal(Native Method) > at sun.nio.ch.SocketChannelImpl.implCloseSelectableChannel(SocketChannelImpl.java:634) > at java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel(AbstractSelectableChannel.java:201) > at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:97) > at org.jgroups.blocks.ConnectionTableNIO$Connection.closeSocket(ConnectionTableNIO.java:913) > at org.jgroups.blocks.ConnectionTableNIO$Connection.destroy(ConnectionTableNIO.java:880) > at org.jgroups.blocks.ConnectionTableNIO.stop(ConnectionTableNIO.java:312) > at org.jgroups.protocols.TCP_NIO.stop(TCP_NIO.java:71) > at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:604) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:514) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.Discovery.down(Discovery.java:333) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:395) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:480) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:283) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.VIEW_SYNC.down(VIEW_SYNC.java:166) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.Protocol.passDown(Protocol.java:551) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:797) > at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:385) > at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:324) > at org.jgroups.JChannel._close(JChannel.java:1286) > at org.jgroups.JChannel.shutdown(JChannel.java:492) > at org.jgroups.tests.perf.transports.JGroupsTransport.stop(JGroupsTransport.java:59) > at org.jgroups.tests.perf.Test.stop(Test.java:208) > at org.jgroups.tests.perf.Test.main(Test.java:705) -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-947) Remove dependency on itemExistsCommand for clustered cache

by Roy Russo (JIRA)

Remove dependency on itemExistsCommand for clustered cache ---------------------------------------------------------- Key: JBPORTAL-947 URL: http://jira.jboss.com/jira/browse/JBPORTAL-947 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Reporter: Roy Russo Assigned To: Roy Russo -- 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

17 years, 10 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-689) PojoCache sensor example broken

by Rajesh Rajasekaran (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-689?page=all ] Rajesh Rajasekaran resolved JBCACHE-689. ---------------------------------------- Resolution: Cannot Reproduce Bug This had to do with some problem on my local Windows box. The bug was not reproducable on other boxes. > PojoCache sensor example broken > ------------------------------- > > Key: JBCACHE-689 > URL: http://jira.jboss.com/jira/browse/JBCACHE-689 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Rajesh Rajasekaran > Assigned To: Manik Surtani > Priority: Critical > Fix For: 1.4.0 > > > Below is the error report on running Sensor example under PojoCache. > bsh % sourceRelative("aop2.bsh"); > // Error: // Uncaught Exception: Method Invocation this.interpreter.source : at Line: 19 : in file: /bsh/commands/sourceRelative.bsh : this .interpreter .source ( path , this .caller .namespace ) > Called from method: sourceRelative : at Line: 1 : in file: <unknown file> : sourceRelative ( "aop2.bsh" ) > Target exception: Sourced file: C:\Documents and Settings\rrajasekaran\Desktop\JBossCache-1.4.0.GA\examples\PojoCache\sensor\aop2.bsh : at Line: 60 : in file: C:\Documents and Settings\rrajasekaran\Desktop\JBossCache-1.4.0.GA\examples\PojoCache\sensor\aop2.bsh : pm .printNodes ( ) > Called from method: printStatus : at Line: 72 : in file: C:\Documents and Settings\rrajasekaran\Desktop\JBossCache-1.4.0.GA\examples\PojoCache\sensor\aop2.bsh : printStatus ( "Initial state" , pm ) > Target exception: java.lang.NullPointerException: Null Pointer in Method Invocation > Also a NullPointerException on running PojoCache/Sensor/build.bat run.aop.example > [java] --------------------------------------------- > [java] Exception in thread "main" java.lang.NullPointerException > [java] at test.propagation.PropagationReplAopTest.printStatus(PropagationReplAopTest.java:113) > [java] at test.propagation.PropagationReplAopTest.testPropagation(PropagationReplAopTest.java:98) > [java] at test.propagation.PropagationReplAopTest.main(PropagationReplAopTest.java:124) > [java] Java Result: 1 > But this doesnt cause a build failure. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-688) TreecacheGUI not updated when the example scripts are run

by Rajesh Rajasekaran (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-688?page=all ] Rajesh Rajasekaran resolved JBCACHE-688. ---------------------------------------- Resolution: Cannot Reproduce Bug This had to do with some problem on my local Windows box. The bug was not reproducable on other boxes. > TreecacheGUI not updated when the example scripts are run > --------------------------------------------------------- > > Key: JBCACHE-688 > URL: http://jira.jboss.com/jira/browse/JBCACHE-688 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Rajesh Rajasekaran > Assigned To: Manik Surtani > Priority: Critical > Fix For: 1.4.0 > > > The TreeCacheGUI doesn't get updated when I run the example scripts. > I tried the plain.bsh, aop.bsh and aopWithTx.bsh scripts. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3324) Authorization Framework with pluggable Authorization Modules

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3324?page=all ] Anil Saldhana closed JBAS-3324. ------------------------------- Closed after the testcase has tested majority of possible usecases. Please refer to the forum thread for more information. > Authorization Framework with pluggable Authorization Modules > ------------------------------------------------------------ > > Key: JBAS-3324 > URL: http://jira.jboss.com/jira/browse/JBAS-3324 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Anil Saldhana > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta > > > Need for an Authorization Framework with an AuthorizationContext has can have a stack of configurable Authorization Modules. Individual modules can implement XACML, JACC , Custom Policy 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

17 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006