On Monday 14 April 2008 16:13, Rickard Öberg wrote: > Niclas Hedhman wrote: > > meaning that from a Binding, it is currently not possible to traverse up > > the Binding tree, hence not possible to create the URI path. > > Oooh, now I get it. You want to be able to *ask* a Binding for its path, > rather than create it manually during output. > > I think the solution is something in between: the toURI method should > take a URI prefix, like so: > URI toURI(URI prefix) > > this way each artifact is responsible for adding its part without having > the burden to know how to fit itself into the bigger picture, which it > can't. This burden is on the client, which should hold the entire context.
I understand why you say this, but it feels strange. Especially at the moment, when every replicated Composite and its part is a new instance. If it is not a new instance for every occurence, then shouldn't (for instance) CompositeModel have a getCompositeResolution() method? I think there is something wrong somewhere... just can't put my finger on it yet. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
