[ loading jdbc drivers ]
> > We could do both. Check ContextClassLoader first and then revert to
> > Class.forName() if that fails. Would that work for you?
>
>
> I think that this is the correct behavior. However, if the
> ContextClassLoader had the system ClassLoader as its parent, reverting
> to Class.forName() is irrelevant. If the system ClassLoader is not the
> parent of the ContextClassLoader, perhaps it should be.
My experience with context classloader was that it was not good enough for situations
where the
jar containing the needed classes were highly variable during the lifetime of block.
With org.apache.avalon.cornerstone.services.store.ObjectRepository, we added a
ClassLoader param
to the get() to allow some help for the deserializer.
It worked well, but may not apply to this situation (a far more stable situation than
the above).
Regards,
- Paul H
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
