Hi!
My intention is to create separate threads for each of the categories described in the initial mail.
The main goal would be to be able to conclude on each thread which is the best approach to be taken.
Having in mind this, I would like to have you comments and opinions about the component mapping i
was suggesting previously.
tia,
./alex
--
.w( the_mindstorm )p.
ps: I will start another thread to deal with Christophe's enhancement.
#: Christophe Lombart changed the world a bit at a time by saying (astral date:
1/12/2006 11:17 AM) :#
Hi Alex,
I'm also interesting by this kind of features. Here are my comments.
On 1/12/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
Hi!
I've started thinking about possible extension of the current
supported mapping strategies. The directions I am investigating right
now are including:
- component mapping
ok what about the following issue :
http://issues.apache.org/jira/browse/GRFT-54.
- relations
Can you give more info. What kind of relations ? Are you speaking
about object associations ?
- inheritance
... and interface. It should be nice to make query based on interface
and of course ancestor class.
- spreaded
Can you give more info ?
So far (and indeed the easiest one) are the component mappings: they
allow mapping the properties of a child object to the properties of
the current working node. In the JCR world, a very good example of
this are the mixins. Introducing a mixin to a node may add a set of
properties that the user can manipulate with the help of a single
entity.
Such an entity doesn't have any restrictions upon it (no path
required, as it doesn't live by itself, no limitation in children,
anything).
Please let me know what do you think about this.
In the future episodes I will try to address the remaining areas.
cheers,
./alex
--
.w( the_mindstorm )p.
--
Best regards,
Christophe
