On Thu, May 27, 2004 at 04:54:54PM +0200, Sylvain Wallez wrote:
> Ugo Cei wrote:
>
> >Sylvain Wallez wrote:
> >
> >>>- Drop that Excalibur datasource. Components that need a DS should
> >>>get one provided by the container via JNDI. If we don't have a
> >>>container (running via the CLI, for instance), let the environment
> >>>provide one and bind it to a JNDI namespace.
> >>
> >>
> >>Mmmhh... defining the JNDI datasources is container-specific, and
> >>therefore makes the applications not self-contained. Furthermore,
> >>subsitemaps (and blocks in the future) can come with their own
> >>datasources used locally. I'm not sure this is compatible with the
> >>global declaration induced by JNDI.
> >
> >
> >Subsitemaps can define local datasources? Really? I tried to, in the
> >past, but could never make this work. Now I'm not interested anymore,
> >since I always use Hibernate and not XSP.
>
>
> <map:components>
> <datasources>
> <jdbc name="local-ds">
> <url>jdbc:blah</url>
> </jdbc>
> </datasources>
> </map:components>
WOW SHIT ! :)
Couldn't express it better. Right now I am also using Hibernate but at my XSP
times when XConfToolTask was too much for me, configuring cocoon.xconf by hand
everytime I upgraded was a real nightmare.
Is it possible to place custom Avalon components here also ?
LG
PS. cocoon really needs more documentation
--
__
| / \ | Leszek Gawron // \\
\_\\ //_/ [EMAIL PROTECTED] _\\()//_
.'/()\'. Phone: +48(501)720812 / // \\ \
\\ // recursive: adj; see recursive | \__/ |
