commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject [beanutils] statics [WAS Re: [digester] collections and default for useThreadClassLoader]
Date Sat, 07 Dec 2002 09:10:47 GMT
On Saturday, December 7, 2002, at 06:50 AM, Costin Manolache wrote:

<snip>

> There is also the issue of statics ( which become very visible when
> you move stuff to the top loader), and the issue of security - which is
> particularily important for beanutil and probably in collections
> ( i.e. - if things are cached - can an application access other
> application's data ? Is there any thread that may change the
> security context ? )

(now is probably a good time to raise something that's been in the air for 
a little while.)

at the moment, beanutils is composed of static methods. the caching is 
also static.

one effect of this is that there is only one global set of converters. 
another is that the cached data has to be shared globally.

it might make more sense to have concrete objects. caches and other data 
would be stored with each instance. the current static methods would then 
call a static instance.

users would then be free to continue to use the convenient static methods 
or they could create an instance and use that instead.

- robert


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message