Leo Simons wrote:
>
> On Thu, 2002-06-27 at 09:11, Peter Donald wrote:
> > At 08:57 AM 6/27/2002 +0200, you wrote:
> > > > With enough annotations you could almost validate the entire sitemap prior
> > > > to deploying it which would probably save a lot of headaches over time.
> > >
> > >is the current metainfo material you guys are writing startup-only? It
> > >has been said cocoon's sitemap changes at runtime
> >
> > And I would put it to you that it doesn't. The other Leo has said much the
> > same thing.
The sitemap may change at runtime, but anytime it changes, it restarts.
So, from a component assembly point of view, it doesn't change.
For example, we were careful *not* to allow the pipelines to be
constructed with run-time information. They are just choosen with that
information, but all the pipelines are assembled and prepared before the
request comes.
Then, for productivity issues, we made it possible for the sitemap to
restart when the sitemap.xmap files change on disk. This is a feature
for development, we suggest to turn it off on production.
> 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 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?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
