At 12:33 PM 6/27/2002 +0200, you wrote:
> > hmm. It seems to me that it would be a valid use case to have the
> > Assembly Profile change at runtime, and not the metainfo itself. ie:
> > drop in a new component at runtime (say through jmx or a commandline
> > tool like the axis package has), and the profile changes.
>
> >From what I understand, component metadata is there to stay
hopefully.
>and to be
>somehow embedded/hardwired into the component behavior (using
>XDoclet-generated code wrapping, proxying (that would be slower),
>specific bytecode extensions of whatever comes next). Is this assumption
>correct?
I am not sure what you mean. Currently we just generator XML descriptors
and the container reads descriptor and interprets the ComponentInfo as
appropraite. We could generate wrapping code but not sure where it would be
used exactly.
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]>
