Wow. That's good trivia for future reference.
That was the exact output from my JVM, I wonder why I didn't get the full path. Next time I need to use that feature either it will be there (newer JVM or ???) or else I'm going to track down why it's not because - you're right - that would have solved my problem much sooner.
As my EE friend always harps, "It's all about visibility".
-Robin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015316#4015316
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015316
PojoCache isn't optimized for attaching strings using putObject(). I'm not an official developer, but I know PojoCache is designed for lightweight replication and is not optimized for attachment speed.
I know PojoCache isn't trying to be the fastest for this sort of use case. There is the TreeCache class for this use case instead. PojoCache's advantages are allowing you to store complex object trees and fine-grained replication.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015300#4015300
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015300