Have read a lot
comparing CF to Cocoon, but I have a different need:
I have a client
who is using Cold Fusion. Client wants to start using XML + RDBMS for content
management. Wants to continue using CF for Web. We have no control over this
decision. Their content today doesn't change frequently. Overnight updates are
fine for most data-driven pages for now. (In other words, performance isn't yet
a big deal for them.) Some text content would need to be updated more quickly.
BTW - They do publish rather large, structured docs to their site, which is the
primary justification for the use of XML.
My broad question
is: What's the best way to manage the delivery of XML content to Cold Fusion (in
combo with data from Oracle)? Need to generate CF and plain HTML pages (we are
talking simplistic use of CF here). Definitely want to use XSLT, but its the
larger management issue that concerns me.
More specifically
for this list: Is Cocoon a reasonable choice for this application
(knowing ahead of time that this might be a somewhat goofy, redundant approach)?
One goal is to
choose an approach that will make it easy for CF to go away at the right time,
and that is straightforward in its handling of XML/XSLT/etc. Might still be a
limited number of CF pages that pull data directly from database, but those
could be transitioned over time as the client is convinced.
Thanks,
Lisa
