David Nuescheler wrote:
Hi guys,
I agree with Lars.
on top of that I would like to mention the following things:
(1) I feel like with a getChildren() method we slowly see
parts of the Node interface sneak in through the back door.
I think it is fairly public that I am not a big fan of the abstraction
from Node but now that we have the abstraction I think we should
even think of Resources that do not even the concept of a hierarchy.
Exactly :) We should not try to add all stuff we know from jcr to the
resource interface. Therefore things like listChildren should not be
part of Resource.
(2) I would really like to table the sling API discussions for a while
and let us all gather some experience with what we have before we
we start modifying the API. From my personal perspective the
constant change in the sling API is the biggest problem for the
few early adopters we have.
Big +1
Now, coming back to the issue which started this, I can only repeat what
I said several weeks (or is it months?) ago: why not adding a "node"
variable to the available variables of the script?
Then you can simply do a:
if ( node != null ) {
node.getNodes();
// do whatever you want with your node
} else {
// well, what do you want to do here?
}
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
