> From: Baer Peter [mailto:[EMAIL PROTECTED]]
<snip/> > One problem here, is apparently that Cocoon can't be started ouf of > the box without running into problems, as, eg, the example applications > use SVG etc. Please separate Cocoon and sample webapp shipped with Cocoon. Sample webapp should be tried in the development environment, where (if your dev. env. is Linux) X is supposed to be started, so no problem will be encountered with the samples. And when you deploy your own applications build on Cocoon, you should think of deployment dependencies: Batik is dependent on the AWT, and you have several options to run AWT: - X server, - Xvfb, - PJA. AFAIU, it is not expected to deploy sample application in the production environment. Don't you think? > Wouldn't it be a good idea to separate the stuff depending > on X / AWT from the rest, so that one could, at least, get Cocoon up and > running, and add the rest later? BTW, this is already on the todo list. Check out todo.xml or todo.html > Think that would help newbies and upgraders from C1! Agreed, <rant>but I still don't get why people are installing sample webapp on the production servers.</rant> Regards, Vadim > > Regards > -- > +-------------------------------+-------------------------------------+ > | Peter C. A. Bär | Siemens Business Services & Co. OHG | > | Fon +49.911.654-2387 | Von-der-Tann-Str. 30-31 | > | Fax +49.911.654-2108 | 90439 Nürnberg | > | | Deutschland | > +-------------------------------+-------------------------------------+ > | >>> mailto:[EMAIL PROTECTED] <<< | > +---------------------------------------------------------------------+ --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
