I think you've got it right in your earlier conclusions, Steve. When it comes to using Java functionality from within CF, such as only "undocumented" from the perspective of a CF person learning about them from the CF docs. They're the same, real java methods available with any Java class and CF is indeed using the real Java classes under the covers (particularly with respect to things like strings, integers, etc.)
As for whether things could change, that has only to do with whether the JVM changes underneath the CF server (whether by your CF Admin doing it manually, which they can, or by way of a new CF version having a new JVM version built-in). But as for the kind of methods being discussed here, it would be very unlikely to change. That's the benefit (and point) of publicly documented APIs in the Java class library: you should be able to rely on them and know that they'd only change if they absolutely must. Going back to the "documentation" aspect, such changes would be very well-documented in the Java API docs for the version you're running. If you need to know what JVM you're running on currently (under CF), I'm sure Someone here can remind you of the couple of lines of CFML code (calling the java library) to report it. It's also reported in the CF Admin in the JVM settings page (and overall "settings summary" page). /Charlie http://www.carehart.org/blog/ -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, December 06, 2006 9:23 AM To: cfaussie Subject: [cfaussie] Is there such a thing as "undocumented features" now? Was just reading back on one of the other topics and noticed the disclaimer "This is an undocumented function so use at own risk" relating to some JAVA snippets. Does this really apply now? In the past, the disclaimer was more in relation to actual coldfusion functions like the service factory stuff that adobe may decide to change (yes i know there is an admin api now) When it comes to using JAVA to do some grunt work, can it be classified as an undocumented feature? My thoughts are no. If coldfusion allows us to access JAVA and any of its functionality, why should we be discouraged to use them? I guess from an application level, as new JAVA releases come out, the new releases of cf should be accomodating these changes so the core cf code wont break. That said, what is the likely hood of core JAVA functions changing or being removed without backwards compatability taken into account? I would have thought not much. So for someone who is looking at gettinginto the JAVA side of things to extend coldfusion, from a product perspective, how worth while is it investing time into JAVA based on any futher incompatabilities between coldfusion/java, and java/java updates? Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
