Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 91382 invoked from network); 30 Sep 2003 17:39:52 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 30 Sep 2003 17:39:52 -0000 Received: (qmail 70074 invoked by uid 500); 30 Sep 2003 17:39:38 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 70013 invoked by uid 500); 30 Sep 2003 17:39:38 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 70000 invoked from network); 30 Sep 2003 17:39:38 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 30 Sep 2003 17:39:38 -0000 Received: (qmail 1464 invoked by uid 50); 30 Sep 2003 17:42:39 -0000 Date: 30 Sep 2003 17:42:39 -0000 Message-ID: <20030930174239.1463.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 20185] - [PATCH] TidySerializer X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20185 [PATCH] TidySerializer ------- Additional Comments From oleg.dulin@opence.net 2003-09-30 17:42 ------- Something like this would make far more sense as a generator. Consider this scenario. There is an existing web application A written using unstructured jsp/html. It works perfectly fine, but there is a requirement to build a new application B that must integrate with A and even reuse some of the pages. A dwcision was made to use Cocoon... TidyGenerator could be used to aggregate pages from A.