But what's the difference if CF changes vs java changing?  I don't
understand how that's any better.  You still have to change code to match
the new features if CF changes behavior just like you would if the java code
changed.

And as Dave mentioned, as far as the stability of java APIs goes, the xml
ones are a pretty safe bet. :)

Roland

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Barry Beattie
Sent: Friday, March 17, 2006 2:05 AM
To: [email protected]
Subject: Re: [CFCDev] Appending XML:

thanx for making your code available for english speakers, Massimo -
and point taken (ditto Roland)

but this brings up another area: how much java "additions" get added
to CF before the whole setup gets unwieldy? Sure, you can abstract
enough Java into CF to do specific jobs but heaven help you 12 months
later if the underlying java classes get changed (look at the comments
in that Spike article I mentioned where his unofficial work-around
breaks with CF7).

so CFDocument is built on the iText libraries. But at least you know
that when the  next version of CF comes out, any useage of iText
updates have been carefully considered and controlled by the CF
engineers (at Adobe) after extensive testing (you'd hope anyway) and
Adobe would give it their blessing. You personally wouldn't have to
manage this process. It removes some of the risk that managers feel
when considering CF over other platforms (like ASP.NET).

There's nothing stopping Adobe from (officially) creating an API into
these java libraries. the difference is that they'd manage it, not you
or the people after you

I'm sorry to take this into an off-topic area but (according to Hal
Helms at cfobjective -
http://www.remotesynthesis.com/blog/index.cfm/2006/3/16/Positioning-ColdFusi
on-in-the-Marketplace
) CF is still seen as a risk (mostly due to ignorance) compared ot the
like of ASP.NET (where it all comes from one vendor). And I've seen
this from experiance with former bosses having grave misgivings in the
long term viability of Java "add-ons" being introduced into large
turn-key CF apps - to them it's yet another thing to worry about.

In short, there's no problem adding additional Java functionality to
CF but it's far better it's done under the auspices of Adobe, not some
developer ready to move to the next project.

so...(at the risk sounding like a stuck record)
"what enhancements to XML the next version of CF might have?"

just my 2c. I'll shut up now.



On 3/17/06, Massimo Foti <[EMAIL PROTECTED]> wrote:
> > All I'm saying is that it would be nice to have DOM methods -
> > something towards the W3C's object model standards
>
> Just invoke the Java parser to get a DOM object:
> http://www.cfmentor.com/code/index.cfm?action=script&id=127
>
> ----------------------------
> Massimo Foti
> Tools for ColdFusion and Dreamweaver developers:
> http://www.massimocorner.com
> ----------------------------
>
>
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
>
> An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
>
>
>


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]







----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to