November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCACHE-619) PojoCache to support JDK5.0 Enum

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-619?page=all ] Ben Wang updated JBCACHE-619: ----------------------------- Component/s: PojoCache Fix Version/s: 2.0.0.GA (was: PojoCache 2.1.0) > PojoCache to support JDK5.0 Enum > -------------------------------- > > Key: JBCACHE-619 > URL: http://jira.jboss.com/jira/browse/JBCACHE-619 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0.GA > > Original Estimate: 4 days > Remaining Estimate: 4 days > > In JDK5.0, Enum is Serializabe. We need to look into whether it is possible to intercept Enum operation as well. -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-674) PojoCache to handle simultaneous pojo attach on the clustering nodes

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-674?page=all ] Ben Wang updated JBCACHE-674: ----------------------------- Priority: Critical (was: Major) > PojoCache to handle simultaneous pojo attach on the clustering nodes > -------------------------------------------------------------------- > > Key: JBCACHE-674 > URL: http://jira.jboss.com/jira/browse/JBCACHE-674 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Critical > Fix For: PojoCache 2.2.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently we don't handle cases with active attachment of pojo on all clustering nodes. For example, > cacheA.attach("1", pojo1); > cacheB.attach("1", pojo2); > pojo2 will overwrite pojo1 but pojo1 will still have cache interceptor attached to it. So solution will have to be some sort of check dirty mechanism when any POJO operation is called. But this will introduce more overheads. > Still need to gather more use case for this. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-328) Support for added methods and constructor in java.util.Timer

by Elias Ross (JIRA)

Support for added methods and constructor in java.util.Timer ------------------------------------------------------------ Key: JBBUILD-328 URL: http://jira.jboss.com/jira/browse/JBBUILD-328 Project: JBoss Build System Issue Type: Patch Affects Versions: JBossRetro-1.0.4.GA Reporter: Elias Ross Priority: Minor Fix For: JBossRetro-1.0.5.GA I extended the retro compiler to deal with the new 1.5 java.util.Timer() methods and constructor and wrote a test for 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

19 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1054) Invalid HTML in divRenderer

by Johnny Healey (JIRA)

Invalid HTML in divRenderer --------------------------- Key: JBPORTAL-1054 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1054 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.4 Final Environment: CentOS release 4.4 (Final), jdk1.5.0_06 Reporter: Johnny Healey Assigned To: Julien Viet Minimize/Maximize buttons have urls containing unescaped ampersands. "&windowstate=minimized" should read "&windowstate=minimized" -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-475) Error in documentation concerning the joining of constarints

by Matias Zaya Mendez (JIRA)

Error in documentation concerning the joining of constarints ------------------------------------------------------------ Key: JBRULES-475 URL: http://jira.jboss.com/jira/browse/JBRULES-475 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.4 Reporter: Matias Zaya Mendez Assigned To: Mark Proctor Priority: Trivial In the documentation it is specified that in the DSL in order to create join constraints you define them as such: (URL:http://labs.jboss.com/file-access/default/members/jbossrules/freezone...) [when]There is a Cheese with=Cheese() [when]-age is less than {age}=age<{age} [when]-type is '{type}'=type=='{type}' [when]-country equal to '{country}'=country=='{country}' Actually, there must be a space between the "dash" and the constraint, such as: [when]There is a Cheese with=Cheese() [when]- age is less than {age}=age<{age} [when]- type is '{type}'=type=='{type}' [when]- country equal to '{country}'=country=='{country}' -- 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 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1032) Document NavigationPortlet new features

by Roy Russo (JIRA)

Document NavigationPortlet new features --------------------------------------- Key: JBPORTAL-1032 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1032 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 1. excplitict tab ordering 2. localization support -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-838) Document where non-String FQN is unacceptable

by Elias Ross (JIRA)

Document where non-String FQN is unacceptable --------------------------------------------- Key: JBCACHE-838 URL: http://jira.jboss.com/jira/browse/JBCACHE-838 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani Clearly, Region names are supposed to be described using String-only FQNs. This is because Regions are configured using String names in their configuration. Also, the file and JDBC based persistence system do not handle non-String FQNs. But here are several use cases for using non-String FQN. For example, at my past company, we stored mobile handset data by country code and phone numbers as numbers. Things like integers and enumerated types are obviously more lightweight than string objects as keys. Personally, I think that being able to use appropriate types in the FQN is worthwhile efficiency and is more consistent with the Java philosophy of type safety. In any case, it would be nice to have an audit of areas that: 0. Do support non-String FQN by design. 1. Do not support non-String FQN, but possibly could (create new issues for these?). 2. Cannot support non-String FQN, and are not documented. -- 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 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBRULES-223) LinkedList for Tuples

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-223?page=all ] Edson Tirelli closed JBRULES-223. --------------------------------- Resolution: Duplicate Issue Work for this issue was done as part of issues JBRULES-484 and JBRULES-498. > LinkedList for Tuples > ---------------------- > > Key: JBRULES-223 > URL: http://jira.jboss.com/jira/browse/JBRULES-223 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 3.1-m2 > > > currently each node creates a new Tuple instance, along with a full Key creation. This is a lot of overhead. Instead we should look at a LinkedList situation where each node just attaches the new column to the passed tuple. We will need to rework parser and any other area of code that does adhoc column looking, so we don't get performance hits. -- 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 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBRULES-44) Dynamic proxy for shadow fact support

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-44?page=all ] Edson Tirelli resolved JBRULES-44. ---------------------------------- Resolution: Done Dynamic shadow proxies are now completelly integrated into core and compiler. > Dynamic proxy for shadow fact support > ------------------------------------- > > Key: JBRULES-44 > URL: http://jira.jboss.com/jira/browse/JBRULES-44 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo, Manual, Drl Parser/Builder > Affects Versions: 3.1-m1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 3.1-m1 > > > The idea is to use dynamic proxies to support shadow facts. So changes to the facts can be queued up, and the shadows refreshed when propagation has finished. -- 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 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBRULES-44) Dynamic proxy for shadow fact support

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-44?page=all ] Edson Tirelli closed JBRULES-44. -------------------------------- > Dynamic proxy for shadow fact support > ------------------------------------- > > Key: JBRULES-44 > URL: http://jira.jboss.com/jira/browse/JBRULES-44 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo, Manual, Drl Parser/Builder > Affects Versions: 3.1-m1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 3.1-m1 > > > The idea is to use dynamic proxies to support shadow facts. So changes to the facts can be queued up, and the shadows refreshed when propagation has finished. -- 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 months

1
0
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 November 2006