Hi all,
IMHO, Avalon is concentrating too much from the POV of the Container and not very much from POV of the Application Integrator (AI).
Perhaps this is so due to the perception that AI have a lot of time to create an application using the blocks available, and that he/she doesn't really need any powerful tools. I beg to differ, as I have expressed many times before.
In order to be able to create tools for the AI, we have to define a specification on how the Component Author (CA) is to package the component(s), and it is my intention with this RT to kick off such a discussion.
Eventually, once this specification is nailed down, I and/or others can start on powerful tools, not only for the AI but also for the CA. We will kill two flies in one go, so to speak.
So, what is the problem??
Avalon today is 100% about CODE and METADATA.
Avalon shy away from all kind of RESOURCES, whether they are pertinent to the Avalon context or not. I don't know if this intentional or not.
In any event, a COMPONENT consists of all of the above, and if one or the other is completely missing, it is not a component anymore.
<snip/>
All of these things work together, so I guess the question here is what whould we work towards? Gettting 70% on everything and then filling in the details?
As to how to manage the JARs and resources I do have some thoughts of my own. I will be reading the entire RT in detail, but have not had the time to yet. Initial thought: use the JMX Advanced Dynamic Loading mechanism to resolve these things.
When I have read the proposal in detail, I can present some more focused comments.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
