On Thursday 27 June 2002 03:42 am, 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. > > 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. > > The separation between assembly and metainfo is still a little clouded > in my head, so...
On the "changing at runtime" bit wrt Cocoon. What changes is the sitemap, but the sitemap is its own container. If you modify the sitemap, the existing container is discarded and a new one is created. Thus it is still at container startup. However, dynamically adding components would be huge. I know this is something Jason Van Zyl is looking for/towards. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
