marc fleury wrote:
> |I think what you need to do is let the CF ask the metadata model for
> |what possible references are available. Then, the metadata model can
> |understand that it may be used in an application and thus ask the other
> |nodes for the complete set of references (or rather, you'd ask the J2EE
> |application metadata, which will ask the nodes).
>
> Agreed, but not part of the "application metadata" as understood by XML. It
> is VM bound and runtime bound.
See previous post. You have unnecessary restrictions with regard to what
metadata is.
> |And then this can easily be extended to a system by letting the J2EE
> |application metadata ask *its* parent, which will be a System metadata
> |object. A nice little tree.
>
> A tree of CLassloaders in the runtime rickard, not a tree of XML information
> :)
I'm not talking about a tree of classloader, I'm not talking about a
tree of XML information, I'm talking about a tree of metadata
information about an application. Period. And at runtime a classloader
is part of that metadata.
> |No, I don't think so. As I have argued in these last posts the metadata
> |model is the spine of all of this. Please don't being this work before
> |it is done (and yes, I know I'm late with it). That will be the
> |best/cleanest/simplest solution IMO.
>
> It is not part of the XML metadata....
Gimme a break... can you please MOTIVATE your opinion instead of just
saying things.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
