> Hi Adam,
G'day mate.
> Keeping it 100% cf is definately a plus, but the line between java and cf
> has become somewhat blurry in recent times.
Yeah. I steer clear of things like leveraging the fact that a string in CF
is a java.lang.String, and there's a bunch of interesting Java methods I
can use instead of the CF offerings. But only because people have said
"ooh, it's naughty to use 'undocumented' methods".
Actually I guess the string example is not a good one... maybe consider the
fact that a query is a java class of type coldfusion.sql.QueryTable, and
that has a bunch of good methods in it. Suggesting to use those has been
frowned on because they're "undocumented", which is pretty much just an
annoying standpoint. If we're not supposed to use them, maybe they
shouldn't be created as PUBLIC, which kind of suggests anyone *is* allowed
to use them? Dunno.
I wish MM would just document them and be done with it.
But back to the original point I was going to make... I class this solution
as different from that, because it's not leveraging anything sneaky: CF
encourages the use of Java in that there's createObject("java",...), and
it's not like it requires any knowledge of Java to use (other than where to
find the API docs ;-)
I definitely need to spend more time looking @ them docs...
--
Adam
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
