On Fri, 16 Aug 2002, Steve Downey wrote:
> > This really seems to pick the best APIs for the job.
> > It's a good idea to use JNDI for configuration storing indeed, as it
> > allows enterprise scale deployments, and seems generally better suited
> > than JMX.
> >
> > Remy
> >
> >
> To the exten
>
>
>>
>>
>> What do you think ?
>
>
> I love it :)
>
> This really seems to pick the best APIs for the job.
> It's a good idea to use JNDI for configuration storing indeed, as it
> allows enterprise scale deployments, and seems generally better suited
> than JMX.
>
> Remy
>
>
To the extent th
[EMAIL PROTECTED] wrote:
> After a lot of thinking and searching, I found a solution that
> I think will work well. If you like it - I'll need some help from
> Remy to implement it. If you don't like it - I'm waiting for
> a better one...
>
> There are 3 major parts:
> 1. Config storage. Current
Craig R. McClanahan wrote:
> (Breathing a sigh of relief that I don't actually have to *implement* this
> stuff, but hoping to contribute a little anyway :-)
Well, the fact that I don't have to implement much is a relief for me too...
Both the API and a lot of drivers ( including xml file ) are
s List <[EMAIL PROTECTED]>
> To: List Tomcat-Dev <[EMAIL PROTECTED]>
> Subject: [5] Config
>
> After a lot of thinking and searching, I found a solution that
> I think will work well. If you like it - I'll need some help from
> Remy to implement it. If you don't like
After a lot of thinking and searching, I found a solution that
I think will work well. If you like it - I'll need some help from
Remy to implement it. If you don't like it - I'm waiting for
a better one...
There are 3 major parts:
1. Config storage. Currently that's server.xml.
2. Configuring v
