December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-883) Mechanism for notification on endpoint shutdown

by David Lloyd (JIRA)

Mechanism for notification on endpoint shutdown ----------------------------------------------- Key: JBREM-883 URL: http://jira.jboss.com/jira/browse/JBREM-883 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor Fix For: Remoting 3 M2 Allows protocols to clean up when the endpoint is terminated, among other things. -- 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
2
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-131) Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-131?page=all ] Manik Surtani reopened JBCACHE-131: ----------------------------------- Assignee: Manik Surtani Need to investigate whether there is a real use case for this, both in 1.4.x as well as 2.x. > Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup > ----------------------------------------------------------------------------------------------------- > > Key: JBCACHE-131 > URL: http://jira.jboss.com/jira/browse/JBCACHE-131 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.2 > Reporter: Jimmy Wilson > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.1.0.GA, 1.4.X > > Attachments: TreeCache.zip > > > Given the following single, unshared cache loader use case in the TreeCache documentation: > "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store" > A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability. > I have modified TreeCache to handle this situation, and I will attach the modified code to this issue. -- 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: (JBCACHE-131) Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-131?page=all ] Manik Surtani updated JBCACHE-131: ---------------------------------- Fix Version/s: 2.1.0.GA 1.4.X > Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup > ----------------------------------------------------------------------------------------------------- > > Key: JBCACHE-131 > URL: http://jira.jboss.com/jira/browse/JBCACHE-131 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.2 > Reporter: Jimmy Wilson > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.1.0.GA, 1.4.X > > Attachments: TreeCache.zip > > > Given the following single, unshared cache loader use case in the TreeCache documentation: > "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store" > A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability. > I have modified TreeCache to handle this situation, and I will attach the modified code to this issue. -- 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: (JBCACHE-131) Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-131?page=all ] Manik Surtani updated JBCACHE-131: ---------------------------------- Summary: Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup (was: Cache Loaders (when unshared, and not used with eviction) Should Persist Transient State Upon Startup) > Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup > -------------------------------------------------------------------------------------------------------- > > Key: JBCACHE-131 > URL: http://jira.jboss.com/jira/browse/JBCACHE-131 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.2 > Reporter: Jimmy Wilson > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.1.0.GA, 1.4.X > > Attachments: TreeCache.zip > > > Given the following single, unshared cache loader use case in the TreeCache documentation: > "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store" > A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability. > I have modified TreeCache to handle this situation, and I will attach the modified code to this issue. -- 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: (EJBTHREE-1168) Rename @Local in ext-api to @ProducerLocal

by Andrew Lee Rubinger (JIRA)

Rename @Local in ext-api to @ProducerLocal ------------------------------------------ Key: EJBTHREE-1168 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1168 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 5.0.0.Beta3 Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 org.jboss.ejb3.annotation.Local is misleading, is used to mark a Producer for local invocations. Easily confused with javax.ejb.Local, to designate local business interface of an EJB. Additionally, naming conflicts occur in ejb3-impl with LocalImpl, which should be renamed to ProducerLocalImpl such that LocalImpl from EJB3 Core (for javax.ejb.Local) may be moved to ejb3-impl without name change. -- 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: (JBPORTAL-1847) Add picture to user profile

by Alex Alvarez (JIRA)

Add picture to user profile ---------------------------- Key: JBPORTAL-1847 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1847 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alex Alvarez Add the capability to upload a user picture into his profile and a tag to display this picture from a portlet. -- 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
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2235) Server Controller Tasks: Throw error if normal shutdown fails

by Aleksandar Kostadinov (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2235?page=comments#action_12392808 ] Aleksandar Kostadinov commented on JBAS-2235: --------------------------------------------- linking forum thread as well http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126217 > Server Controller Tasks: Throw error if normal shutdown fails > ------------------------------------------------------------- > > Key: JBAS-2235 > URL: http://jira.jboss.com/jira/browse/JBAS-2235 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Environment: jboss-4.0 tip > Reporter: Ryan Campbell > Assigned To: Martin Vecera > Fix For: JBossAS-5.0.0.CR1 > > Attachments: jboss-test-diff > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Currently, when a server fails to respond to a shutdown request, the process is killed and the tests continue. > There should be an error thrown if the server fails to shutdown within the timeout period. -- 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-2235) Server Controller Tasks: Throw error if normal shutdown fails

by Aleksandar Kostadinov (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2235?page=all ] Aleksandar Kostadinov updated JBAS-2235: ---------------------------------------- Attachment: jboss-test-diff Attaching a diff with additional changes so I can link that through the forums. Using this JIRA task as very closely related. Actually I'm building on Martin's changes and the "failonerror" addribute should be part of the solution IMO. Even if default gets changed. > Server Controller Tasks: Throw error if normal shutdown fails > ------------------------------------------------------------- > > Key: JBAS-2235 > URL: http://jira.jboss.com/jira/browse/JBAS-2235 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Environment: jboss-4.0 tip > Reporter: Ryan Campbell > Assigned To: Martin Vecera > Fix For: JBossAS-5.0.0.CR1 > > Attachments: jboss-test-diff > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Currently, when a server fails to respond to a shutdown request, the process is killed and the tests continue. > There should be an error thrown if the server fails to shutdown within the timeout period. -- 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-4397) remove a resource by way of its ManagedComponent without removing the entire deployment

by Mark Spritzler (JIRA)

remove a resource by way of its ManagedComponent without removing the entire deployment --------------------------------------------------------------------------------------- Key: JBAS-4397 URL: http://jira.jboss.com/jira/browse/JBAS-4397 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Mark Spritzler remove a resource by way of its ManagedComponent without removing the entire deployment Example: If you delete a DataSource it also removes the xxx-ds.xml file if one exists. Where in that file it is possible to configure more than one DataSource. -- 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] Created: (JBAS-4395) Implement complex ManagedProperties with MetaTypes for Datasources

by Mark Spritzler (JIRA)

Implement complex ManagedProperties with MetaTypes for Datasources ------------------------------------------------------------------ Key: JBAS-4395 URL: http://jira.jboss.com/jira/browse/JBAS-4395 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Mark Spritzler Implement complex ManagedProperties with MetaTypes for Datasources. connection properties for example. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007