Mikolaj Rydzewski wrote:
> Ingo Siebert wrote:
>> I see one additional problem. If I deploy two different versions of
>> the web app on the same tomcat, it is not possible configurate them
>> separately.
>>
>> That's important for me, because I have only a limited number of
>> servers and I have to deploy more than one version at the same time.
>>
>> Any additional ideas?
>
> Don't you like JNDI?
>
> For example with data sources: you configure every webapp to use
> java:comp/env/jdbc/ds to get DataSource reference. On container level
> you either specify different DataSource per webapp (thus they won't be
> any conflict) or you can create several definitions, like:
> java:comp/env/jdbc/ds1, java:comp/env/jdbc/ds2, etc. and use
> ResourceLink to link them together.
Yes, I'm unsure if this is a very good solution for me.
I primary configuration values are many but simple string values like a
JDBC-URL or JDBC-Options. I think the complete abstraction of the
DataSource is not necessary for me. I've seen it at Apache Continuum and
I think it was a little bit unhandy.
JNDI is an additional complexity to my app. It feels wrong to use JNDI
only to get a simple file path or a base file path.
If I want to deploy my web app to another container like tomcat, does
all container provide JNDI and are all containers compatible? I have no
experience with that, but it's an possible cause of defect.
Do you think I can safely use JNDI and never get any problem?
Ingo
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
