From sylvain.wallez@anyware-tech.com Tue Dec 5 08:43:37 2000 Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 39323 invoked from network); 5 Dec 2000 08:43:37 -0000 Received: from unknown (HELO mail.anyware-tech.com) (213.11.20.188) by locus.apache.org with SMTP; 5 Dec 2000 08:43:37 -0000 Received: from anyware-tech.com ([10.0.0.1]) by mail.anyware-tech.com (8.11.0/8.8.7) with ESMTP id eB58e0P07917 for ; Tue, 5 Dec 2000 09:40:01 +0100 Message-ID: <3A2CAA2C.D566B4EB@anyware-tech.com> Date: Tue, 05 Dec 2000 09:41:16 +0100 From: Sylvain Wallez Organization: Anyware Technologies X-Mailer: Mozilla 4.7 [fr] (WinNT; I) X-Accept-Language: fr,en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: XObject References: <3A2BF017.1060507@apache.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Jeremy Quinn a écrit : > > At 20:27 +0100 04/12/00, Ricardo Rocha wrote: > >Robin Green wrote: > > > > > >> Come on, let's vote on this. > > > >+1 for org.apache.cocoon.xml.XObject with toSax() and toDom() > > OK. > > So change the capitalisation on the method names as well? No, please. If we follow JDK naming conventions, methods should be named toSAX and toDOM. All acronyms are upper case and a lot of methods have been deprecated in the past for changing for example "Url" to "URL". > > >[but sans toString()] > > I think I added that in a TagLib to get around a problem in the > xsp:attribute template in xsp-java.xsl, when you try to use a tag that > outputs XObjects to set the attribute. > > > String.valueOf() > > > Let's try and fix the xsp:attribute template instead :) > > What I like about XObject is I want to be in a situation whereby more than > just strings can get passed from one tag to another via nesting different > taglibs. We have several choices of what can get passed around, so what do > you choose to implement, in the hope the other taglib has sent it to you? > Node, NodeList, XObject, DocumentFragment, String, ContentHandler? You > would end up replicating most of the code in xspExpr in XSPPage.java in > each of your Tags. Encouraging the use of XObject simplifies the job of > making more powerful TagLibs IMHO. > > For instance the FP TagLib is tied to only manipulating files. If FP (or > something like it) could just concentrate on XML manipulations and rely on > other TagLibs for storage and retrieval it could be more flexible. > > >Jeremy Queen wrote: > > Umm, that's Quinn actually ;) > > > > Ricardo, are you lurking? > > > >Yes :-) > > Great to hear from you :) > > regards Jeremy > -- > ___________________________________________________________________ > > Jeremy Quinn Karma Divers > webSpace Design > HyperMedia Research Centre > > > -- Sylvain Wallez Anyware Technologies