PROTECTED]
Sent: Thursday, September 13, 2007 4:00 PM
To: CF-Talk
Subject: Re: java classloader
Dan -
You shouldn't move the JavaLoader .jar files around, they should stay in the
way they were originally downloaded in.
Mark
On 9/14/07, Kris Jones [EMAIL PROTECTED] wrote:
Did the java classpath
:[EMAIL PROTECTED]
Sent: Thursday, September 13, 2007 4:00 PM
To: CF-Talk
Subject: Re: java classloader
Dan -
You shouldn't move the JavaLoader .jar files around, they should stay in the
way they were originally downloaded in.
Mark
On 9/14/07, Kris Jones [EMAIL PROTECTED] wrote:
Did
Did the java classpath on the machine change?
I'm using the javaclass loader to load a meta-data reader for some jpegs.
It seems no matter where I put the .jar for the class loader I get the
following exception:
message: com.compoundtheory.classloader.NetworkClassLoader
type:
Dan -
You shouldn't move the JavaLoader .jar files around, they should stay
in the way they were originally downloaded in.
Mark
On 9/14/07, Kris Jones [EMAIL PROTECTED] wrote:
Did the java classpath on the machine change?
I'm using the javaclass loader to load a meta-data reader for some
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
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
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.Class);
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
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 or
9 matches
Mail list logo
