Re: ColdFusion 5 and Java Object Instantiation

2005-01-26 Thread Barney Boisvert
The point of my first email was that in reality, nothing happens when you call createObject. The object isn't instantiated until the first method call. All that happens with createObject is that CF makes the assumption that it will probably need to instantiate the named class at some point in the

Re: ColdFusion 5 and Java Object Instantiation

2005-01-26 Thread Barrett Nuzum
Thanks for the response, Barney. >Instantiation of Java objects happens at the first method call, NOT at >the createObject call. I misspoke. I'm instantiating with createObject, and then it barfs when I perform the method call. >Now that that's out of the way, I bet the problem you're having

Re: ColdFusion 5 and Java Object Instantiation

2005-01-26 Thread Barney Boisvert
Instantiation of Java objects happens at the first method call, NOT at the createObject call. The reason is so that you can call the init() method with parameters, which in turn calls the constructor. So a "proper" java object instantiation looks like this: The .init() is optional if you don't

ColdFusion 5 and Java Object Instantiation

2005-01-26 Thread Barrett Nuzum
Hi gang. We've got a ColdFusion 5.1 server, and we're trying to add some functionality using Java objects and the CFOBJECT tag. Now, I've got two classes that I've written, and seem to work fine. If I execute them as Java Applications on my localhost, they run ***perfectly***. On the CF server