Peter Donald wrote:
> Hi,
>
> Which means there no longer needs to be an xml parser or classes in
> ClassPath. Is there anything else that needs to be changed to be more
> lightweight wrt to ContainerKit?
The containerkit package provides a lot of the defintion of the
component contract based on defintions contains within an XML file (the
.xinfo). I'm currently working on a container that is a component and
the services it provides is based on assembly instructions. In this
case, the service information is not inside a .xinfo file - it held
inside an object model in the form of a ComponentInfo instance.
Keeping in mind that that the compoent in question can provide service
information based on static declarations in an assembly file - I need to
figure out how this information can be made available to another
container without supplying a .xinfo file.
I havn't throught about solutions yet because I'm still playing around
at lower levers in containerkit - but I'm interested in any thoughts
about possible solutions. One of the important things is that I want to
be able to use this composition component/container as a service
provider when handling service dependecy resolution.
Cheeers, Steve.
>
>
> Cheers,
>
> Peter Donald
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> "Faced with the choice between changing one's mind,
> and proving that there is no need to do so - almost
> everyone gets busy on the proof."
> - John Kenneth Galbraith
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
