incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandru Popescu" <>
Subject Re: JCR-Mapper: ClassLoading issues
Date Wed, 06 Sep 2006 09:25:11 GMT
On 9/6/06, Felix Meschberger <> wrote:
> Hi,
> I am new to the JCR-Mapper, so please forgive any stupidity :-)
> I am working on a projects which involves mapping nodes to objects.
> The environment of this project is an OSGi Framework which makes
> extensive use of classloaders and visibility separation.
> Consider now, that I have different classes and their descriptors
> defined in different bundles. It would now be very unpractical to
> export all classes from the defining bundles (which would work in the
> worst case) and even almost impossible to import those classes into
> the bundle, which has the JCR-Mapper classes.
> Currently classes are loaded through Class.forName(String) which just
> takes the class loader of the object placing the call. This call is
> placed from various places though probably, there is some kind of
> central place in the RefelctionUtils class.
> To solve this issue, class loading must probably be completely
> centralized (all users use ReflectionUtils.forName(String)) and
> ReflectionUtils should be somehow configurable to set the classloader
> to use.

This was exactly the reason why I have decided to have this central
place to deal with reflection/CL/etc. I was quite sure that sooner or
later somebody will need better mechanisms and this might be a good
start. I know it is not perfect, but I am sure we can evolve it.

.w( the_mindstorm )p.

> What do you think of this ?
> Regards
> Felix

View raw message