Heres are some things: The big difference is the configuration and the dynamic modularity. You cannot do the same with Cocoon. In order to use Cocoon from the commandline you need to supply an xconf file. This is handled differently in babeldoc:
1. The configuration of babeldoc is "merged" - so you just need to "add" those functions/configurations - you do not need to supply a wholly new (or derived) configuration. Also it makes configuration incremental and overridable. You do not need to crack open babeldoc to override a configuration option. Additionally the configuration data can be stored in a SQL database and accessed just as from XML or properties files. 2. Journaling - Cocoon just has no way of recreating previous processing state. Babeldoc has this built in. You can replay processing. 3. Babeldoc also has a number of text/data to XML conversion pipeline stages. You can convert Excel or EDI or CSV or COBOL copy book data to XML and then process it. Ideal for heterogeneous sites. 4. The scanner - great for unattended systems. Supports CRON-like scheduling. This is not to say that Babeldoc is "better" than Cocoon - its different from Cocoon. Personally I think that they are complementary and I use both daily. I want to focus on XML and document technologies and Cocoon and Babeldoc allow me to do that. regards, Bruce. -----Original Message----- From: Reinhard Poetz [mailto:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 11:40 AM To: [EMAIL PROTECTED] Subject: RE: Babeldoc 1.2.0-RC2 Release From: McDonald, Bruce > Babeldoc is really quit different from Cocoon. Beside that Babeldoc is different (How pipelines are described? Non-XML-data, ...) I don't see any difference between Cocoon used via the command line interface (CLI) and Babeldoc. Or more concrete I don't know what you can do with Babeldoc that you can't do with Cocoon. (But maybe 15 minutes reading the Whitepaper is not enough). Cheers, Reinhard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
