> -----Original Message-----
> From: Marcus Crafter [mailto:[EMAIL PROTECTED]]
> Sent: den 2 november 2001 16:58
> To: [EMAIL PROTECTED]
> Subject: Re: ParentComponentManager & config files
>
> I had thought that using cocoon's CM to manage my application's
> components was the wrong thing to do, because it required
> modifying the
> cocoon.xconf and cocoon.roles files - part of cocoon and not our
> application. Was this assumption false ?
Marcus,
I don't know. I see it not as having my own application separate from
Cocoon, but rather to extend Cocoon. I suppose it is a question of whether
you embed Cocoon in your app or the other way around. I have no idea what
the original intentions were.
> > That said, the string being passed *is* a general string
> argument. You can
> > use it as you see fit. As for the resolving of paths relative
> to the webapp
> > context, currently Cocoon will only honor Loggable and Initializable
> > contracts, but this is not an obstacle - it would be relatively
> simple to
> > make it honor another contract as well, maybe Contextualizable
> (?), and pass
> > the servlet context.
>
> Ok. Thanks for the tip mate - How does this patch look ? :-)
Looks fine to me, BUT: I wonder if there is a way to go "all the way", and
honor all lifestyle interfaces Avalon has bu hijacking a ComponentHandler
from Excalibur or something. I have the feeling that we're currently
re-implementing a ComponentHandler step by step... Maybe that'd be easier,
but then you have to initialize the ComponentHandler, etc... OK, it looks
fine to me. Period.
Now to get a committer interested... (I'm not.)
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
