2 Replies Latest reply on Mar 4, 2009 9:17 AM by Krzysztof Sobolewski


    Krzysztof Sobolewski Newbie

      There are some "convenience" methods in Cache interface which are "normally" declared in the Node interface. They are not really equivalent, because the versions in Cache are atomic, while those in Node are prone to races in low isolation levels, so I prefer to use the former. The thing is that not all methods have their equivalents in Cache. I especially long for getChildrenNames(Fqn) which is only available in CacheSPI. Why is that? The SPI interfaces are supposed to be "restricted" and not used by client code, but I can't see why this particular method needs to be restricted. Is it by design? Or should I report it as a bug? :)

      [And while you're at it you could also consider Cache.getChildren(Fqn) :)]