[JBoss JIRA] Updated: (JBCACHE-485) Refactor the current Collection classes (list and set)
by Elias Ross (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-485?page=all ]
Elias Ross updated JBCACHE-485:
-------------------------------
Attachment: icache.diff
For the List, adding an IntegerCache might help performance with List operations slightly. Again, using Integer.valueOf(int i) would be better than strings, but if there's that restriction, it's much better to use pooled Strings. I haven't looked into this.
> Refactor the current Collection classes (list and set)
> ------------------------------------------------------
>
> Key: JBCACHE-485
> URL: http://jira.jboss.com/jira/browse/JBCACHE-485
> 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
>
> Attachments: icache.diff, set.diff
>
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
>
> Current implementation of Collection uses direct coupling to the cache store indices. E.g., we map them into subtree according to index ordering. This is not very desirable for performance reason. We should consider to provide a indirect mapping such that it is considered a graph instead of ordered tree.
> Or we should investigate whether it is possible to use a proxy operates on java.util.* classes such that we don't need to have our own implementation. The JDK lincense aside, ArrayList, e.g., uses an internal transient array. Is it possible to "aspectize" on that array 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
19 years, 6 months
[JBoss JIRA] Updated: (JBCACHE-485) Refactor the current Collection classes (list and set)
by Elias Ross (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-485?page=all ]
Elias Ross updated JBCACHE-485:
-------------------------------
Attachment: set.diff
I lost my CVS commit rights, but anyway here's a patch to make the Set.contains() add() and remove() implementations be O(1) (more or less.)
If for 2.0, it'd be nice if Fqn in PojoCache could be arbitrary types, then there wouldn't be any reason to "toString" on the Long.
To fix the List implementation, I guess I would consider two cases separately. There's the LinkedList and RandomAccess styles of Lists. For LinkedList, you wouldn't have to worry about get(int i) being O(1) so removes in the middle could be fast. Could you change the implementation to detect and match closely what the user used?
> Refactor the current Collection classes (list and set)
> ------------------------------------------------------
>
> Key: JBCACHE-485
> URL: http://jira.jboss.com/jira/browse/JBCACHE-485
> 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
>
> Attachments: set.diff
>
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
>
> Current implementation of Collection uses direct coupling to the cache store indices. E.g., we map them into subtree according to index ordering. This is not very desirable for performance reason. We should consider to provide a indirect mapping such that it is considered a graph instead of ordered tree.
> Or we should investigate whether it is possible to use a proxy operates on java.util.* classes such that we don't need to have our own implementation. The JDK lincense aside, ArrayList, e.g., uses an internal transient array. Is it possible to "aspectize" on that array 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
19 years, 6 months
[JBoss JIRA] Created: (JBCACHE-812) Enable JGroups multiplexer integration in a 1.4.x release
by Brian Stansberry (JIRA)
Enable JGroups multiplexer integration in a 1.4.x release
---------------------------------------------------------
Key: JBCACHE-812
URL: http://jira.jboss.com/jira/browse/JBCACHE-812
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Manik Surtani
For 1.4.0.GA, the JGroups mux integration was disabled pending resolution of service view issues in the JG multiplexer code. With JG 2.4 these issues are resolved, so the mux integration can be enabled. We'll want this in a 1.4.x release so it can be used in a 4.x JBoss AS.
Note that the mux integration uses reflection, so having this enabled does not mean JBC requires JGroups 2.4. But, a JBC release with it enabled should probably ship with either a) a pre-mux JG release, ie. 2.2.9.x (currently 2.2.9.2 is included in Branch_1_4_0) or b) JG 2.4 or later, which has the mux issues resolved.
--
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
[JBoss JIRA] Resolved: (BPEL-84) Provide an initial release that works with jbossws
by Alejandro Guizar (JIRA)
[ http://jira.jboss.com/jira/browse/BPEL-84?page=all ]
Alejandro Guizar resolved BPEL-84.
----------------------------------
Resolution: Done
Run target "main" in src/test, followed by "one-test". The output of a successful run is shown below:
-bash-2.05b$ ant -Dtest=org.jboss.test.ws.jaxrpc.samples.wsbpel.hello.BpelHelloTestCase one-test
Buildfile: build.xml
one-test:
[junit] Running org.jboss.test.ws.jaxrpc.samples.wsbpel.hello.BpelHelloTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 18.991 sec
> Provide an initial release that works with jbossws
> --------------------------------------------------
>
> Key: BPEL-84
> URL: http://jira.jboss.com/jira/browse/BPEL-84
> Project: JBoss jBPM BPEL
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Engine
> Reporter: Thomas Diesler
> Assigned To: Alejandro Guizar
> Fix For: jBPM BPEL 1.1 beta 1
>
> Attachments: jbpm.bpel.guide.pdf
>
>
> The bpel release that I am looking for should be independent of Apache Axis and have the integration points to the tools layer sufficiently abstracted so that it can use wstools
--
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