On Nov 20, 2007 10:58 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Let us keep the Resource completely abstract...
I like that.
> ... public interface JcrResource extends Resource {
> Node getNode();
> }..
Ok
>... public interface MappedResource extends Resource {
> Object getObject();
> }..
Ok - I'd call that OcmMappedResource maybe, as "mapped" is a kinda generic name.
>... This would allow for other resources such as a FileResource or an
> URLResource (hold on, there is an actual use case....
I was going to say "that's nice even though we don't have a use case
right now", so if we have one that's even better
>... For microsling, we can then safely assume, that the Resource is always a
> JcrResource...
ok
>... WDYT ?..
I'm +1 on the proposed changes.
-Bertrand