October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4888) Inject InvalidationManagerMBean into JGCacheInvalidationBridge

by Brian Stansberry (JIRA)

Inject InvalidationManagerMBean into JGCacheInvalidationBridge -------------------------------------------------------------- Key: JBAS-4888 URL: http://jira.jboss.com/jira/browse/JBAS-4888 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 Currently an ObjectName is injected, and startService() does a JMX lookup. Just have the MC inject the service. Will also remove the getter/setter from JGCacheInvalidationServiceMBean -- MC is doing the injection into a pojo service, and it doesn't need to be in an MBean interface for any other reason. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-24) Get OpenSaml2 snapshot libraries into the JBoss repository

by Anil Saldhana (JIRA)

Get OpenSaml2 snapshot libraries into the JBoss repository ---------------------------------------------------------- Key: SECURITY-24 URL: http://jira.jboss.com/jira/browse/SECURITY-24 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OnDemand, Repository Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories. -- 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

2
4
0 / 0

[JBoss JIRA] Commented: (JBAS-1292) SFSB session replication

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1292?page=comments#action_12383478 ] Dimitris Andreadis commented on JBAS-1292: ------------------------------------------ Is this issue still current, or outdated? > SFSB session replication > ------------------------ > > Key: JBAS-1292 > URL: http://jira.jboss.com/jira/browse/JBAS-1292 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Bela Ban > Assigned To: Jason T. Greene > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Issues: who instrument the user-specified object? Can it be done transparently? > - SFSB has states defined already and user declared it as "clusterable", can we > declare the fields object as "advisable" at runtime. Meaning, deployer will know > this bean is clusterable and it will "delegate" it to JBossAop to declare all > the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor > at run time. Check with Bill on this feature. > - Check modified field and do fine-grained replication only -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2153) Spring-int tests

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2153?page=all ] Dimitris Andreadis updated JBAS-2153: ------------------------------------- Component/s: Spring integration (was: Test Suite) > Spring-int tests > ---------------- > > Key: JBAS-2153 > URL: http://jira.jboss.com/jira/browse/JBAS-2153 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Spring integration > Reporter: Adrian Brock > Assigned To: Ales Justin > > Need some ant unit tests for spring-int such that we don't break it. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2040) Spring Deployer

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2040?page=all ] Dimitris Andreadis updated JBAS-2040: ------------------------------------- Component/s: Spring integration (was: Deployment services) > Spring Deployer > --------------- > > Key: JBAS-2040 > URL: http://jira.jboss.com/jira/browse/JBAS-2040 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Spring integration > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Optional > > Complete me for release notes. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2042) Spring deployer and coding standards

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2042?page=all ] Dimitris Andreadis updated JBAS-2042: ------------------------------------- Component/s: Spring integration (was: Other) > Spring deployer and coding standards > ------------------------------------ > > Key: JBAS-2042 > URL: http://jira.jboss.com/jira/browse/JBAS-2042 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Spring integration > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Trivial > > The spring deployer follows incorrect coding standards. > i.e. Kernigan and Ritchie > Also, it should not use printStackTrace(), > nor should it use the horrible log.error and throw paradigm > that just leads to a console full of annoying duplicate logging of errors. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4886) Incorrect order/dependency shutting down MDBs

by Clebert Suconic (JIRA)

Incorrect order/dependency shutting down MDBs --------------------------------------------- Key: JBAS-4886 URL: http://jira.jboss.com/jira/browse/JBAS-4886 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Clebert Suconic Assigned To: Weston Price Fix For: JBossAS-5.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

2
2
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-381) Add param on destination to disable persistence

by Jeff Mesnil (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Jeff Mesnil reassigned JBMESSAGING-381: --------------------------------------- Assignee: Jeff Mesnil (was: Tim Fox) > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Jeff Mesnil > Fix For: 2.0.0 Beta 1 > > Attachments: patch-JBMESSAGING-381.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Jeff Mesnil (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Jeff Mesnil reassigned JBMESSAGING-375: --------------------------------------- Assignee: Jeff Mesnil (was: Tim Fox) > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Jeff Mesnil > Fix For: 2.0.0 Beta 1 > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1300) Default a portlet window to maximized.

by David Roberts (JIRA)

Default a portlet window to maximized. -------------------------------------- Key: JBPORTAL-1300 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Roberts Priority: Optional When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page. -- 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

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007