January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-856) Rationalize the top-level mbean classes

by Brian Stansberry (JIRA)

Rationalize the top-level mbean classes --------------------------------------- Key: JBCACHE-856 URL: http://jira.jboss.com/jira/browse/JBCACHE-856 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA For the AS 5 beta I've added CacheJmxWrapper and PojoCacheJmxWrapper to meet the needs of the AS. There were existing classes in the jmx packages as well. Need to rationalize this; probably get rid of the old existing classes after any tests that use them are switched to the new ones. -- 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

[JBoss JIRA] Created: (JBTM-144) Restructure repository

by Mark Little (JIRA)

Restructure repository ---------------------- Key: JBTM-144 URL: http://jira.jboss.com/jira/browse/JBTM-144 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Release Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little We need to commit the QA tests into the repository, but do it in such a way that they can be checked out independently of the rest of the distribution. -- 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-3678) org.jboss.test.webservice.attachmentstepbystep.MyServiceClientTestCase fails on Solaris 10

by Phillip Thurmond (JIRA)

org.jboss.test.webservice.attachmentstepbystep.MyServiceClientTestCase fails on Solaris 10 ------------------------------------------------------------------------------------------ Key: JBAS-3678 URL: http://jira.jboss.com/jira/browse/JBAS-3678 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Environment: Sparc Solaris 10 jdk 1.4.2_08 Reporter: Phillip Thurmond org.jboss.test.webservice.attachmentstepbystep.MyServiceClientTestCase fails on Solaris 10 Testcase: testMyService took 1.656 sec Caused an ERROR null java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at org.jboss.ws.soap.attachment.ContentHandlerRegistry.<clinit>(ContentHandlerRegistry.java:5 1) at org.jboss.ws.soap.attachment.AttachmentPartImpl.<clinit>(AttachmentPartImpl.java:56) at org.jboss.ws.binding.soap.SOAPBindingProvider.getAttachmentPart(SOAPBindingProvider.java:6 14) at org.jboss.ws.binding.soap.SOAPBindingProvider.bindRequestMessage(SOAPBindingProvider.java: 137) at org.jboss.ws.binding.soap.SOAP11BindingProvider.bindRequestMessage(SOAP11BindingProvider.j ava:58) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:647) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398) at org.jboss.test.webservice.attachmentstepbystep.MyServiceClientTestCase.testMyService(MySer viceClientTestCase.java:70) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.lang.IllegalArgumentException: failed to parse:image/bmp, image/x-bmp, image/x-window s-bmp at java.awt.datatransfer.DataFlavor.<init>(DataFlavor.java:299) at javax.activation.ActivationDataFlavor.<init>(ActivationDataFlavor.java:64) at org.jboss.ws.soap.attachment.ImageDataContentHandler.buildFlavors(ImageDataContentHandler. java:77) at org.jboss.ws.soap.attachment.ImageDataContentHandler.<clinit>(ImageDataContentHandler.java :63) ... 31 more -- 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

6
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-855) Add NotificationBroadcaster support to top-level MBeans

by Brian Stansberry (JIRA)

Add NotificationBroadcaster support to top-level MBeans ------------------------------------------------------- Key: JBCACHE-855 URL: http://jira.jboss.com/jira/browse/JBCACHE-855 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.0.0.GA We need to clarify responsibility for this between the top level JMX wrapper beans and CacheMgmtInterceptor. -- 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
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-934) Remove JChannelFactory JMX lookup from CacheImpl

by Brian Stansberry (JIRA)

Remove JChannelFactory JMX lookup from CacheImpl ------------------------------------------------ Key: JBCACHE-934 URL: http://jira.jboss.com/jira/browse/JBCACHE-934 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1, 2.0.0.ALPHA2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.BETA2 CacheImpl tries to do a JMX lookup of the JChannelFactory. The factory should only be available from the RuntimeConfig -- the CacheImpl should not look it up. Any JMX lookup should be done by a JMX integration layer, i.e. CacheJmxWrapper or CacheLegacyJmxWrapper. With this the MBeanServer property can be removed from RuntimeConfig, as it's only use is for this llokup. -- 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

[JBoss JIRA] Created: (JBAOP-311) Update tutorial examples to work with jboss retro for jdk 1.4

by Kabir Khan (JIRA)

Update tutorial examples to work with jboss retro for jdk 1.4 ------------------------------------------------------------- Key: JBAOP-311 URL: http://jira.jboss.com/jira/browse/JBAOP-311 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 -- 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
7
0 / 0

[JBoss JIRA] Created: (SECURITY-14) Replace SecurityAssociation with Security SPI

by Anil Saldhana (JIRA)

Replace SecurityAssociation with Security SPI --------------------------------------------- Key: SECURITY-14 URL: http://jira.jboss.com/jira/browse/SECURITY-14 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 There is a need to move the legacy SecurityAssociation context to the Security SPI. -- 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-13) Authorization Framework should work off of the roles in the Security Context

by Anil Saldhana (JIRA)

Authorization Framework should work off of the roles in the Security Context ---------------------------------------------------------------------------- Key: SECURITY-13 URL: http://jira.jboss.com/jira/browse/SECURITY-13 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 There has been a discussion going on with reference to a Security Context in JBossSX. Refer to the forum thread As it stands, the Security Context is populated with the roles for the authenticated user, but the access checks that are happening (mainly for the jacc layer) needs to move away from the reliance on the role-group placed as a principal in the authenticated subject, but to use the roles in 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: (JBRULES-534) Rename Column to Pattern

by Mark Proctor (JIRA)

Rename Column to Pattern ------------------------ Key: JBRULES-534 URL: http://jira.jboss.com/jira/browse/JBRULES-534 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 We are now going to refer to Column as Patterns, as it was confusing 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

19 years

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-538) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBRULES-538 URL: http://jira.jboss.com/jira/browse/JBRULES-538 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Mark Proctor Fix For: 3.0.5 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, 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
6
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