If you tested this with a test program that was in the same directory, it is in the same package by default. The default access allows the calls to be accessed by other members of the same package.
CFMX won't see the CFObject call as a call from within the same package and therefore fails. -----Original Message----- From: Joe Eugene [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 12:42 AM To: CF-Talk Subject: Re: CFObject in CFMX Outside of the Package might be right.. but i havent created any packages. > > now take the code.. compile and run it.. you should get the method > > called.. > > No you won't because your class is not public It compiled and ran the code succesfully with (class Simple) on java Simple // no public but CFObject didnt like this. I am not sure.. what your doing.... or are we on the same page here? Joe ----- Original Message ----- From: "Sean A Corfield" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, September 09, 2002 12:15 AM Subject: Re: CFObject in CFMX > On Sunday, September 8, 2002, at 06:01 , Joe Eugene wrote: > > I am not sure if this is the case.. did u see the second post i made to > > Matt? > > Yes. > > > Example > > class Simple { // note no public/private should default to > > public in Java > > No, it is *not* public by default. Such a class is *not* accessible by an > external system. Java requires that you specify "public class Simple" if > you want "Simple" to be accessed outside of that package. > > > now take the code.. compile and run it.. you should get the method > > called.. > > No you won't because your class is not public. > > > remove the main() and call it with <CFOBJECT> it starts to > > complain... > > Of course. You took out a *public* method that accessed the class > *from*within* and didn't leave any public interface. > > > its a real pain to start and stop the server in development. > > /coldfusion stop > /coldfusion start > > Takes a few seconds. Not much of a pain at all. But I agree that > configuring hot load would make it even easier. > > > Well is hot load implemented > > for CF classes.. i mean how is that implemented in CFMX? > > CF checks the timestamp on the *source* .cfm / .cfc file and if it is > newer that the version it has already compiled, it compiles it (to Java > and then compiles the .java to .class) and explicitly reloads the class > files. It can do this because it starts the process off by accessing a > file and can do each step explicitly. This is very different from having a > running Java system and dropping a new .class file in - the JVM does not > normally look at the timestamps every time it invokes a class / method. > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
