Jung, Eric wrote:
The reason I think it would be harder is because since Contexts are not thread-safe, you shouldn't store the Context from the ctor in a class member. You should re-acquire the Context before doing a "set", thus guaranteeing thread-safety. However, if only the Context is passed to the ctor, you won't have enough information to re-acquire the Context before set.
I'm not sure to understand how fetching the context on every "set" will make the operation thread safe. Anyway this may not be an issue right now since JNDIConfiguration is read only.
-Eric p.s. can you point me to the Jakarta page that details how to supply a patch? I know I've seen it before, just can't remember where...also, should I open a bugzilla ticket for this?
Yes you can open a bug for this. I think the page you are looking for is this one:
http://jakarta.apache.org/commons/patches.html
Emmanuel Bourg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
