The hbase code calls either classforname or uses the system implied
classloader when it refers to other classes. Maybe there is something there?
Its using the default java classloader (which doesn't have your classpath)
maybe?

On Jul 9, 2009 2:38 PM, "Saptarshi Guha" <saptarshi.g...@gmail.com> wrote:

Hello,
Thanks for the tip. I have added all the jar files in HBASE_HOME and
HBASE_HOME/lib and HBASE_HOME/conf is in the classpath.
Going through the code of Configuration.java and
HBaseConfiguration.java, the latter is a simple subclass and
setClassLoader replaces the classloader with a user supplied one. This
classloader is then used to things like Class.forName(...)

I didn't understand the bit about recursive class loaders, there being
only one right?

Thanks again for the information
Cheers
Saptarshi

On Thu, Jul 9, 2009 at 2:23 PM, Ryan Rawson<ryano...@gmail.com> wrote: > You
need to include every...

Reply via email to