sounds good to me ;)
> > ...Let us keep the Resource completely abstract...
> I like that.
+1
> > ... public interface JcrResource extends Resource {
> > Node getNode();
> > }..
> Ok
can we make it "NodeResource" ?
> >... public interface MappedResource extends Resource {
> > Object getObject();
> > }..
> Ok - I'd call that OcmMappedResource maybe, as "mapped" is a kinda generic
> name.
sounds good.
i would probably propose:
public interface ObjectMappedNodeResource extends NodeResource {
}
> >... For microsling, we can then safely assume, that the Resource is always a
> > JcrResource...
> ok
sounds like a good approach.
regards,
david
