David Nuescheler wrote
<pointless-rant>
Carsten says:
For instance, if you have a non-jcr-resource this resource ...
Can we please not use that as an argument... I really think
we should focus on the real use-cases we have at hand.
I know I sound like a broken record regarding the abstraction
of Sling from JCR. Getting access to session and node is
just the beginning.
Personally, I think it makes little sense to promote abstraction on
the Sling API layer, if we re-introduce all the JCR dependencies
"rightfully" and based on use-cases through the back door into
all the scripting layers.
I guess what beats me is, why we can't build abstraction into the
system as we go along and just cover our current needs for now.
YAGNI. Scratch your own itch. Flexibility Syndrome.
</pointless-rant>
I think you missinterpreted my comment and quoted my statement out of
context.
Anyways, it seems we have a solution now that we can all agree on - and
that's the important part :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
