I retest of javaloader version 2
HelloWorld = loader.create("org.hsqldb.jdbcDriver");
hello = HelloWorld.init();
loads fine and I can see the object but
class = createObject("java", "java.lang.Class").forName("
org.hsqldb.jdbcDriver");
still blows up
class = createObject("java", "java.lang.Cl
It's the only logical solution. I think my code is out there on the net and
it might have cost me some
dollars because the problem had to do with JDBC drivers and I am assuming
the other classloaders still can't do JDBC but maybe they can do it now,
darn.
Wishlist for CF 8: A way report a JDBC con
Going to try Dan's suggestion. If that still doesn't work I will post some
code.
~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your
Without the error, and/or some sort of testbed to look at, it becomes
hard to debug.
Regards,
Mark
On 10/4/06, Dan Plesse <[EMAIL PROTECTED]> wrote:
> It could be the order in which you loaded everything. You have to load the
> jars first then the classes.
>
> The second issue could be the level
It could be the order in which you loaded everything. You have to load the
jars first then the classes.
The second issue could be the level or depth of the classloader might be too
shallow.
~|
Introducing the Fusion Authority Qu
Was wondering if anyone had worked with JavaLoader.cfc (see:
www.compoundtheory.com) or the Java ClassLoaders in general.
I am working with Apache Lucene and Coldfusion. I've written some Java classes
that extend some of Lucene's. When I try to load my classes with JavaLoader.cfc
I get an erro
6 matches
Mail list logo
