Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 71629 invoked by uid 500); 6 Nov 2001 20:42:30 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 71617 invoked from network); 6 Nov 2001 20:42:30 -0000 Message-Id: <200111062042.fA6KgZD11619@orion.rgv.hp.com> X-Mailer: exmh 2.2 06/23/2000 with XEmacs 21.4.4 on Linux 2.4.13 From: Ovidiu Predescu To: Sylvain Wallez Cc: cocoon-dev@xml.apache.org Subject: Interpreted sitemap [was Re: Jo! & WAR file apps] In-Reply-To: Your message of "Tue, 06 Nov 2001 17:42:20 +0100." <3BE812EC.F2ED057E@anyware-tech.com> X-Url: http://www.geocities.com/SiliconValley/Monitor/7464/ X-Image-Url: http://www.geocities.com/SiliconValley/Monitor/7464/ovidiu.tiff X-Face: ?(@Y~qjBA}~8ZMh5gM4{Q{bE_*:sCJ3@Z?{B*Co=J!#8bb~-z?-0._vJjt~MM59!MjxG%>U 5>MW^2-\7~z04buszR^=m^U|m66>FdR@cFwhb;.A(8*D.QmLkK]z,md0'HiOE\pyeiv_PACR+P:Cm. wq_%l':E:q]g-UCc>r&s@BVo'kFN;(\9PF22Myg5w%nUBWQ6MJJ#qL#w>2oxckP'H:\$9F"mxsz]Dg k{1`fTcP'Y$CgGnc^paTV$dzhVX+;(U$;Eb)P<>G)g) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Nov 2001 12:42:35 -0800 Sender: ovidiu@orion.rgv.hp.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sylvain, On Tue, 06 Nov 2001 17:42:20 +0100, Sylvain Wallez wrote: > Also, if you find the sitemap "too proprietary", you can write your own > pipeline assembly language : the sitemap has recently been decorrelated > from the Cocoon class so that you can use your own implementation of > Processor : I'm currently writing a new interpreted implementation of > the sitemap that could be the foundation of future other pipeline > assembly languages. This sounds very interesting, can you give us some hints on your approach? I've been thinking to start working on such a beast for a while, but was busy with other stuff at work. One of the my requirements for this re-implementation is to allow things other than SAX events to flow on the pipeline. I'm specifically thinking of Java objects that could represent the incoming HTTP request as an object, for unorthodox types of processing. Of course the interfaces of the components in the pipeline have to be compatible for such an approach to work. My thoughts were to take the Ant XML->Java conversion engine, extend it to use the SAX2 API, and create Avalon components that represent the pipeline. The Ant engine is indeed a very simple, yet powerful and extensible way to create a hierarchy of Java objects from an XML document. Could you describe a bit your approach? Regards, -- Ovidiu Predescu http://orion.rgv.hp.com/ (inside HP's firewall only) http://sourceforge.net/users/ovidiu/ (my SourceForge page) http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org