> From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > > From: Peter Donald [mailto:[EMAIL PROTECTED]] > > > > Hi, > > > > I just went to redo the excalibur projects documentation and > > found that it is > > extremely complex to setup and use. You have to go download a > > 14MB file and > > do all sorts of munging to get things working and it is in no > > way shape or > > easy. Even then it spits out mountains of debug and warnings > > about things > > that I am not using etc. > > > > Compare this to Anakia > > > > <taskdef name="anakia" > > classname="org.apache.velocity.anakia.AnakiaTask"/> > > > > <anakia basedir="${xdocs.src}" destdir="${docs.dir}/" > > extension=".html" > > style="./site.vsl" > > projectFile="stylesheets/project.xml" > > includes="**/*.xml" > > lastModifiedCheck="true" > > templatePath="my/path/stylesheets" > > > </anakia> > > I hear your pain. Cocoon also has heard the cry, and is working > on making a minimal solution that does not have a 14 MB chunk to > download.
If I can participate in discussion... Cocoon itself takes one floppy; the rest are Avalon, Xerces, Xalan, Batik and FOP. I see that Xerces and Xalan already part of Avalon, and Avalon itself is obviously present. If you want SVG and/or PDF, Batik and FOP adds 3.8Mb. This sums up to adding one floppy of Cocoon JARs to the Avalon CVS, and not a 14Mb chunk... Hope I did not missed the point here. Vadim > In essence they are wanting to componentize web applications > so that you have the Cocoon core, and whatever component you need. > > For us, this would be the Jakarta styling component.... > > The process is not finished yet, and may take some time. > > Here is the bottom line: > > 1) Cocoon is a powerful concept--esp. for dynamic information. > 2) Cocoon is very heavy for the command line. > 3) All we need is XSLT and FOP--we have defined "pipelines" > > For the short term, I would not be offended if we used the > <style/> tag for straight XSLT transformations (our resulting > info would be pretty much XHTML 1.0 compliant (except we may have > some additional tags...) > > We could theorhetically generate the PDF by directly invoking > FOP to generate it. For our HTML docs, this approach would be > the least painful. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
