March 2009 - jbosscache-issues - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1409) Unnecessarily scary debug message during config parsing

by Brian Stansberry (JIRA)

Unnecessarily scary debug message during config parsing ------------------------------------------------------- Key: JBCACHE-1409 URL: https://jira.jboss.org/jira/browse/JBCACHE-1409 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA Reporter: Brian Stansberry Assignee: Manik Surtani Priority: Minor XmlConfigurationParser.setValue logs a rather alarming message when it tries and fails to find a property setter that takes a String or Element: 2008-09-11 17:07:09,026 DEBUG [org.jboss.cache.factories.XmlConfigurationParser] (main) Unrecognised attribute SyncReplTimeout. Please check your configuration. Ignoring!! It then goes on to look for a setter that takes a different type (in this case, long) and sets the property, or fails with an exception if there really is no appropriate setter. It's only a DEBUG message, so this is minor, but the message itself is quite alarming. If there needs to be a message at all, perhaps "No property SyncReplTimeout of type String or Element; checking for other types." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-311) Refactor jbosscache to provide an interface for transport

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-311?page=com.atlassian.jira.pl... ] Manik Surtani resolved JBCACHE-311. ----------------------------------- Fix Version/s: (was: 4.0.0) Resolution: Won't Fix > Refactor jbosscache to provide an interface for transport > --------------------------------------------------------- > > Key: JBCACHE-311 > URL: https://jira.jboss.org/jira/browse/JBCACHE-311 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nick Betteridge > Assignee: Manik Surtani > > There are many different transports available (jgroups, jboss remoting etc) which are available and which already exist within commnissioned systems. Further, clients requirements/project specification sometimes stipulates a specific transport to be used. JBossCache currently has JGroups embedded as the transport used. If BossCache was refactored to provide a generic transport interface, it would make JBossCache more 'user friendly' so that the features of JBossCache can be used within a greater variety of projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-311) Refactor jbosscache to provide an interface for transport

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-311?page=com.atlassian.jira.pl... ] Manik Surtani reopened JBCACHE-311: ----------------------------------- > Refactor jbosscache to provide an interface for transport > --------------------------------------------------------- > > Key: JBCACHE-311 > URL: https://jira.jboss.org/jira/browse/JBCACHE-311 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nick Betteridge > Assignee: Manik Surtani > Fix For: 4.0.0 > > > There are many different transports available (jgroups, jboss remoting etc) which are available and which already exist within commnissioned systems. Further, clients requirements/project specification sometimes stipulates a specific transport to be used. JBossCache currently has JGroups embedded as the transport used. If BossCache was refactored to provide a generic transport interface, it would make JBossCache more 'user friendly' so that the features of JBossCache can be used within a greater variety of projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1242) Remove deprecated public API methods that expose JGroups classes

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1242?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1242. ------------------------------------ Resolution: Won't Fix > Remove deprecated public API methods that expose JGroups classes > ---------------------------------------------------------------- > > Key: JBCACHE-1242 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1242 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Manik Surtani > Assignee: Manik Surtani > > Public API or SPI methods that expose JGroups classes - such as BuddyLocator.locateBuddies() exposing Address or ViewChangeEvent exposing a View - should be deprecated since 2.1.0 (see dependent JIRA). > These deprecated methods should be removed in 3.0.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1242) Remove deprecated public API methods that expose JGroups classes

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1242?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1242: ----------------------------------- Fix Version/s: (was: 4.0.0) > Remove deprecated public API methods that expose JGroups classes > ---------------------------------------------------------------- > > Key: JBCACHE-1242 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1242 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Manik Surtani > Assignee: Manik Surtani > > Public API or SPI methods that expose JGroups classes - such as BuddyLocator.locateBuddies() exposing Address or ViewChangeEvent exposing a View - should be deprecated since 2.1.0 (see dependent JIRA). > These deprecated methods should be removed in 3.0.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-1242) Remove deprecated public API methods that expose JGroups classes

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1242?page=com.atlassian.jira.p... ] Manik Surtani reopened JBCACHE-1242: ------------------------------------ > Remove deprecated public API methods that expose JGroups classes > ---------------------------------------------------------------- > > Key: JBCACHE-1242 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1242 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Manik Surtani > Assignee: Manik Surtani > > Public API or SPI methods that expose JGroups classes - such as BuddyLocator.locateBuddies() exposing Address or ViewChangeEvent exposing a View - should be deprecated since 2.1.0 (see dependent JIRA). > These deprecated methods should be removed in 3.0.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1243) Provide alternatives to JGroups classes in public API methods, deprecate old methods.

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1243?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1243. ------------------------------------ Fix Version/s: (was: 4.0.0) Resolution: Won't Fix > Provide alternatives to JGroups classes in public API methods, deprecate old methods. > ------------------------------------------------------------------------------------- > > Key: JBCACHE-1243 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1243 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Manik Surtani > Assignee: Manik Surtani > > This would involve additional JBC classes to represent: > 1) An Address > 2) A MethodCall > 3) A View > as counterparts to their JGroups namesakes. > The public API and SPI - such as BuddyLocator, ViewChangedEvent, InvocationContext and Cache/CacheSPI - should use JBC classes/interfaces rather than JGroups ones. > Old methods to still be retained but deprecated for now, with a clear message that they will disappear in 3.0.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1242) Remove deprecated public API methods that expose JGroups classes

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1242?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1242. ------------------------------------ Resolution: Won't Fix > Remove deprecated public API methods that expose JGroups classes > ---------------------------------------------------------------- > > Key: JBCACHE-1242 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1242 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.0.0 > > > Public API or SPI methods that expose JGroups classes - such as BuddyLocator.locateBuddies() exposing Address or ViewChangeEvent exposing a View - should be deprecated since 2.1.0 (see dependent JIRA). > These deprecated methods should be removed in 3.0.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-311) Refactor jbosscache to provide an interface for transport

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-311?page=com.atlassian.jira.pl... ] Manik Surtani resolved JBCACHE-311. ----------------------------------- Resolution: Won't Fix > Refactor jbosscache to provide an interface for transport > --------------------------------------------------------- > > Key: JBCACHE-311 > URL: https://jira.jboss.org/jira/browse/JBCACHE-311 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Nick Betteridge > Assignee: Manik Surtani > Fix For: 4.0.0 > > > There are many different transports available (jgroups, jboss remoting etc) which are available and which already exist within commnissioned systems. Further, clients requirements/project specification sometimes stipulates a specific transport to be used. JBossCache currently has JGroups embedded as the transport used. If BossCache was refactored to provide a generic transport interface, it would make JBossCache more 'user friendly' so that the features of JBossCache can be used within a greater variety of projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1486) Provider a *tests-sources.jar

by Galder Zamarreno (JIRA)

Provider a *tests-sources.jar ----------------------------- Key: JBCACHE-1486 URL: https://jira.jboss.org/jira/browse/JBCACHE-1486 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Scripts and processes Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor On 12 Feb 2009, at 10:00, Galder Zamarreno wrote: > Hi, > > When doing a "mvn install", I've realised that the following files are installed in my local repo: > > [galder@localhost]~/jboss/code/cache/core-trunk% ls ~/.m2/repository/org/jboss/cache/jbosscache-core/3.1.0-SNAPSHOT -al > total 3816 > drwxr-xr-x 2 galder galder 4096 2009-02-10 22:24 . > drwxr-xr-x 5 galder galder 4096 2009-02-11 12:19 .. > -rw-r--r-- 1 galder galder 1137186 2009-02-11 11:57 jbosscache-core-3.1.0-SNAPSHOT.jar > -rw-r--r-- 1 galder galder 22315 2009-02-11 11:57 jbosscache-core-3.1.0-SNAPSHOT.pom > -rw-r--r-- 1 galder galder 1059047 2009-02-11 11:57 jbosscache-core-3.1.0-SNAPSHOT-sources.jar > -rw-r--r-- 1 galder galder 1655882 2009-02-11 11:57 jbosscache-core-3.1.0-SNAPSHOT-tests.jar > -rw-r--r-- 1 galder galder 318 2009-02-11 11:57 maven-metadata-local.xml > > What about jbosscache-core-3.1.0-SNAPSHOT-tests-sources.jar? I have no objection to generating these as well. Feel free to update the pom accordingly. -- Manik Surtani Lead, JBoss Cache http://www.jbosscache.org manik(a)jboss.org -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues March 2009