Quoting Flavio Costa <listas-gKsXbHVs43GLjhqoV9UUrw@xxxxxxxxxxxxxxxx>:
> > as far as i'm informed tomcat separates those instances in its own
> > classloaders so it should be possible to have different config instances
> > - correct me, if i'm wrong.
Yes, if you place a chiba.jar copy in every webapp. Sorry for the doubt.
>
> As Tomcat organizes its classloaders, if you place Chiba jar in
> common/lib or shared/lib, probably there will be only one instance. If
> placed in WEB-INF/lib, one instance will be created for every
> application (context).
I agree.
> By the way, I've looked at current Config class and it somewhat
> resembles what I had in mind. As you say, it allows loading the XML
> from package tree or another place. However, we would like to have
> more control over config loading than this. What if instead of
> specifying a XML file, we could give two things: the Config class
> implementation (e.g. br.com.company.mycode.Config) and init-parameters
> which could be read by the Config class as a Map. Of course, for this
> strategy to work the configuration should always be referenced by an
> interface to be implemented by any Config classes, not by a concrete
> class.
Would be a great enhancement. I am extending the Config class too, to allow
loading of ConnectorFactory implementations other than Chiba one.
--
Eduardo Millán
Technical Telecommunications engineer, specialist in Telematics
Java programmer and analyst
ALBA Software: http://www.albasoft.com
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
|
