PojoCache 2.0 creates an example for passivation usage
------------------------------------------------------
Key: JBCACHE-722
URL: http://jira.jboss.com/jira/browse/JBCACHE-722
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Priority: Optional
Fix For: 2.0.0
--
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
Requalify WS-TX 1.0 interop against IBM/Microsoft endpoints
-----------------------------------------------------------
Key: JBTM-122
URL: http://jira.jboss.com/jira/browse/JBTM-122
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: WS-T Implementation
Affects Versions: 4.2.1
Reporter: Kevin Conner
Assigned To: Kevin Conner
--
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
[ http://jira.jboss.com/jira/browse/JBCACHE-204?page=all ]
Ben Wang resolved JBCACHE-204.
------------------------------
Resolution: Duplicate Issue
> Externalize RegionManager.Capacity parameter
> --------------------------------------------
>
> Key: JBCACHE-204
> URL: http://jira.jboss.com/jira/browse/JBCACHE-204
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Priority: Minor
> Fix For: 2.0.0.GA
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> RegionManager.CAPACITY is used to determine the size of the eviction event queue. It is fixed now. We should externalize it later such that we can tune the eviction policy performance. E.g., when the load is heavy, we may need to increase the queue size such that it is not blocking.
--
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
[ http://jira.jboss.com/jira/browse/JBCACHE-479?page=all ]
Ben Wang resolved JBCACHE-479.
------------------------------
Resolution: Out of Date
Non-issue anymore.
> Cache loader to load children as well when loading a node
> ---------------------------------------------------------
>
> Key: JBCACHE-479
> URL: http://jira.jboss.com/jira/browse/JBCACHE-479
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.4SP1
> Reporter: Manik Surtani
> Assigned To: Ben Wang
> Fix For: 2.0.0.GA
>
>
> Requested by Ben, for failing unit test o.j.c.aop.loader.FileCacheLoaderAopCollectionsTest
--
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
PojoCache to create an example for load-time option
---------------------------------------------------
Key: JBCACHE-773
URL: http://jira.jboss.com/jira/browse/JBCACHE-773
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Priority: Minor
Fix For: 2.0.0
As titled.
--
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
[ http://jira.jboss.com/jira/browse/JBCACHE-590?page=all ]
Ben Wang resolved JBCACHE-590.
------------------------------
Resolution: Done
> PojoCache release 2.0 tasks
> ---------------------------
>
> Key: JBCACHE-590
> URL: http://jira.jboss.com/jira/browse/JBCACHE-590
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Fix For: PojoCache
>
>
> This is a parent task that links all the key PojoCache tasks that I'd like to do in 2.0. Due to the schedule contraint, we may push some of these issues to 2.0.x.
--
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
[ http://jira.jboss.com/jira/browse/JBCACHE-660?page=all ]
Ben Wang resolved JBCACHE-660.
------------------------------
Resolution: Won't Fix
> Implement PojoCache Collection class that handles JDK50 generics
> ----------------------------------------------------------------
>
> Key: JBCACHE-660
> URL: http://jira.jboss.com/jira/browse/JBCACHE-660
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: PojoCache
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Priority: Minor
> Fix For: PojoCache
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> Currently for PojoCache Collection classes, we have internal implementation that we replace dynamically with the user one. This works for JDK1.4. However, in 5.0, if a user uses generics, then this can be a problem. E.g., here is the code snippet:
> List<Cube> list = new ArrayList();
> list.add(cube1);
> list.add(cube2);
> Cube cube = list.get(0);
> cache.attach(fqn, list);
> List<Cube> list1 = (List<Cube>) cache.find(fqn); // OK but not typed.
--
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
[ http://jira.jboss.com/jira/browse/JBCACHE-180?page=all ]
Ben Wang resolved JBCACHE-180.
------------------------------
Resolution: Out of Date
> Create a use case for PojoCache using CacheLoader
> -------------------------------------------------
>
> Key: JBCACHE-180
> URL: http://jira.jboss.com/jira/browse/JBCACHE-180
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: PojoCache
> Affects Versions: PojoCache
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Priority: Minor
> Fix For: PojoCache
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> It will be nice if we can find a use case for JBossCacheAop using cache loader, set it up, and document 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