Hi Christophe, No problem, I will patch all Class.forName(String) uses to use ReflectionUtils and I add setter/getter to RelfectionUtil to implant a custom class loader used by the ReflectionUtils.forName() method.
While I tend to think, that classloader configuration of a static utility method this is not the best solution possible, I have no better one at hand right now. Will do the patches and create an issue. Regards Felix On 9/6/06, Christophe Lombart <[EMAIL PROTECTED]> wrote:
On 9/6/06, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi, > > I am new to the JCR-Mapper, so please forgive any stupidity :-) > You are welcome > 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. > > What do you think of this ? > I understand your problem and your solution. Can you contribute something :-) ? I have no time to work on this. Thanks ! -- Best regards, Christophe
