At 03:10 AM 6/28/2002 +0200, you wrote:
>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.
So the component is dynamically generated with a corespondingly dynamically
generated info?
>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 am not sure it is possible unless we start defining Factorys for Avalon
components. For a factory you pass in a implementation key (usually
classname) and aquire an instance of type. The factory would also expose
the MetaInfo associated with type.
This is where we are going in Myrmidon-land. Largely this is so we can have
one type masqurade as another type. ie Ant1 tasks pretend to be Ant2 tasks,
XML Templates pretend to be Tasks etc.
Some people have asked in past to have objects in different frameworks
(WebServices in particular) to be exposed as Avalon components. With a
factory in place we could have a webservice treated exactly like a normal
Avalon component or whatever.
Anyways it is something to experiment with but I am not sure we can yet
standardize on any such technique yet until it has been played with a bit
more.
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]>
