July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-154) Improved lifecycle events

by Kabir Khan (JIRA)

Improved lifecycle events ------------------------- Key: JBMICROCONT-154 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-154 Project: JBoss MicroContainer Issue Type: Task Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossMC_2_0_0 Beta3 -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-997) create test for role-mapping

by William DeCoste (JIRA)

create test for role-mapping ---------------------------- Key: EJBTHREE-997 URL: http://jira.jboss.com/jira/browse/EJBTHREE-997 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 4.2.0 GA Reporter: William DeCoste Assigned To: William DeCoste -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-109) Support direct registration of beans without a StandardMBean wrapper

by Brian Stansberry (JIRA)

Support direct registration of beans without a StandardMBean wrapper -------------------------------------------------------------------- Key: JBMICROCONT-109 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-109 Project: JBoss MicroContainer Issue Type: Sub-task Components: General Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossMC_2_0_0 Beta If a bean is already a valid MBean, it should be possible to directly register it in JMX without wrapping it in a StandardMBean. Otherwise beans that implement things like MBeanRegistration, NotificationBroadcaster, NotificationEmitter will not expose that API to the mbean server. To support this, @JMX will add an attribute: boolean registerDirectly() default false; JMXIntroduction will check the attribute; if true the target bean will be registered directly; otherwise a StandardMBean will be created and registered. -- 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, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-4530) Direct inject HAPartition into ProxyFactoryHAMBean

by Brian Stansberry (JIRA)

Direct inject HAPartition into ProxyFactoryHAMBean -------------------------------------------------- Key: JBAS-4530 URL: http://jira.jboss.com/jira/browse/JBAS-4530 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 Cluster module's org.jboss.proxy.generic.ProxyFactoryHAMBean exposes attribute PartitionObjectName, and impl does a JMX lookup to find the HAPartition. Change the attribute name to Partition just inject the HAPartition. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1541) Exception when changing the Dashboard theme properties

by Chris Laprun (JIRA)

Exception when changing the Dashboard theme properties ------------------------------------------------------ Key: JBPORTAL-1541 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1541 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.1 Final PortalObjectImpl.setDeclaredProperty doesn't handle properly the case where there is no parent. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-28) NDC/MDC support for common-logging

by Jason T. Greene (JIRA)

NDC/MDC support for common-logging ---------------------------------- Key: JBCOMMON-28 URL: http://jira.jboss.com/jira/browse/JBCOMMON-28 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: logging-jdk, logging-log4j, logging-spi Reporter: Jason T. Greene Assigned To: Jason T. Greene Fix For: 2.0.4.GA -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1562) Isolate Identity services in separate .sar

by Antoine Herzog (JIRA)

Isolate Identity services in separate .sar ------------------------------------------ Key: JBPORTAL-1562 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1562 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6 Final Environment: JBP2.6.0 Reporter: Antoine Herzog Priority: Minor Fix For: 2.8 Final All the classes of Identity are in a jar (portal-identity.jar). The configuration is in several folders : "deploy\jboss-portal.sar\conf\hibernate\user/" and "deploy\jboss-portal.sar\conf\identity" May be it is possible to bundle all the identity features in a separate (sub) sar of the portal. And also provide a deploy option to build : - Hibernate implementation only - LDAP implementation only - Both Usecase : - More clean, for customization - Ability to remove the original JBoss Portal portal-identity.sar and deploy a new customized one More more easy for release upgrade than writting in the files of jboss-portal.sar. - Ability to avoid having the LDAP config in prod that does not use LDAP. - More easy to build automatic test, for various User and Role implementation (Hib, LDAP, ... EJB3 coming ?) - More easy for providing other identity storage and management (community or vendors). I guess that should work. may be check a few things : - deployement : make sure that all goes fine when the server start (this service is vital for a lot of major portal services) - make sure all is fine with CMS needs etc... see Jira : http://jira.jboss.com/jira/browse/JBPORTAL-1499 - adaptation of the documentation I have adapted the Hibernate implementation, to work with some "extended User and Role". Works fine. But not easy (not clean) to set the configuration in the original files (and will not also for upgrades like next 2.6.1). By the way : Identity is widely used in systems. May be this implementation (services, controlers, etc...) could become a separate JBoss AS module (not only for portal) ? -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2957) Replace HA-JNDI AutoDiscovery with JGroups based implementation

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2957?page=all ] Brian Stansberry updated JBAS-2957: ----------------------------------- Fix Version/s: No Release (was: JBossAS-5.0.0.CR1) I don't see this happening any time soon. The initial work Jerry did on it found as many issues as it would resolve. > Replace HA-JNDI AutoDiscovery with JGroups based implementation > --------------------------------------------------------------- > > Key: JBAS-2957 > URL: http://jira.jboss.com/jira/browse/JBAS-2957 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Jerry Gauthier > Assigned To: Brian Stansberry > Priority: Minor > Fix For: No Release > > > HA-JNDI AutoDiscovery uses its own IP multicasting-based discovery mechanism. This is error-prone code and should be replaced with the well-tested JGroups framework. > See JIRA issue JBCLUSTER-43 for further details. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-343) Stress test with a large number of clients accessing the server in parallel

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ] Clebert Suconic reassigned JBMESSAGING-343: ------------------------------------------- Assignee: Clebert Suconic > Stress test with a large number of clients accessing the server in parallel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-343 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: 1.4.0.CR1 > > > Push the limit of concurent clients to limit -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1010) ORA-01000: maximum open cursors exceeded when adding messages to a queue

by Jay Howell (JIRA)

ORA-01000: maximum open cursors exceeded when adding messages to a queue ------------------------------------------------------------------------ Key: JBMESSAGING-1010 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1010 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.3.0.GA Reporter: Jay Howell Assigned To: Tim Fox When users create a large amount of messages and don't consume them, oracle users will get an error telling them that there are too many cursors open. The test was done with 20,000 text messages. In JDBCPersistenceManager::pageReferences we need to create the prepared statement once. We need to move the prepared statement out side of the loop. This will reduce the number of cursors open and should alleviate the problem. -- 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, 3 months

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 July 2007