Ben, I'm using generic Objects in Fqn's in the DistributedState-Implementation I'm
currently working on. If I stay on this path this will not just be rarely used case
I know it's not easy implement configuration for eviction-policies that support this
or cache-loaders, but I'm shure we can
getRegion does a similar test, should it be fixed as well?
instead of all the (repeated) string concatenations, would it be better to have
Region.getFqn() return a string that's always terminated by /?
-l
View the original post :
it would be better design if Region.getFqn() returns an Fqn not a String so we could
use Fqn.isChildOf(Fqn) instead of String.startsWith()
BtW: Fqn are not just concatenated Strings - In the longrun we have to find a way to
configure Regions for eviction based on reall (Object-based) Fqn's.
norbert wrote : it would be better design if Region.getFqn() returns an Fqn not a
String so we could use Fqn.isChildOf(Fqn) instead of String.startsWith()
|
| BtW: Fqn are not just concatenated Strings - In the longrun we have to find a way
to configure Regions for eviction based on
currently, Fqn.isChildOf is broken. if you attempt to check to see if a *parent* is
the child of a *child* you'll get an exception:
a = Fqn.fromString(/a)
| b = Fqn.fromString(/a/b)
| b.isChildOf(a)
| 1
| a.isChildOf(b)
| Traceback (innermost last):
| File console, line 1, in ?
1. OK, I have now appended automatically the region fqn with a separator so that
should solve this problem. A better solution is fqn.toString() is appended
automatically with separator as well. But I need to look at it closer.
2. Fqn.isChildOf bug is fixed.
3. Use of Fqn construction with
Yes, you are right. This can be a problem. :-) It's been fixed.
Thanks for the effort,
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3850153#3850153
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3850153
