jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Re: Analyzing the Jackrabbit architecture
Date Tue, 10 Jan 2006 09:26:07 GMT

On 1/10/06, Tobias Bocanegra <tobias.bocanegra@day.com> wrote:
> i think, it is vice versa. the classes in the state package depend on
> the *Id classes.

Ah, my mistake, I got the directions mixed up. The problem (the state
-> core dependency, caused in part by the *Id classes) is the same

> as for the API (and/or a possible jcr-283 extension) we could get rid
> of the very loosly defined UUID of type String and probably introduce
> the NodeId, PropertyId, ItemId and make it part of the jcr API. i
> would love to have:
> Session.getNode(NodeId id) and Node.getId()
> so if i would need to move the *Id classes, i would put them to
> org.apache.jackrabbit.* and make them part of the (yet non-existent
> :-) API.

Sounds good.


Jukka Zitting

Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftmanship, JCR consulting, and Java development
View raw message