Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 72189 invoked by uid 500); 5 Sep 2001 08:04:39 -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 72156 invoked from network); 5 Sep 2001 08:04:39 -0000 From: "Carsten Ziegeler" To: Subject: AW: [C2][VOTE] Sync C2.0 and C2.1 branches Date: Wed, 5 Sep 2001 10:05:33 +0200 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal In-Reply-To: <999676607.3b95dabf61269@mail.otego.com> X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.5 |September 22, 2000) at 05.09.2001 10:04:44, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.5 |September 22, 2000) at 05.09.2001 10:04:44, Serialize complete at 05.09.2001 10:04:44 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Giacomo Pati wrote: > > Quoting Gianugo Rabellino : > > > On Wed, Sep 05, 2001 at 08:38:55AM +0200, Giacomo Pati wrote: > > > > > 1) XML:DB Generators - There are two generators in C2.1 for > > > > > dealing with data from XML:DB data > > > > > sources > > > > +0 (These are additional components which do not affect the core) > > > > > > +0 as well. Yes, they don't affect the core. But as it is an XML > > stream comming > > > from an xmldb what about making it a protocl > > (dbxml:/db/mydocs/foo[is='bar'])? > > > > More than willing to add this feature, but I need to look deep inside > > Cocoon internals to understand exactly how to do it. Any starting > > points? :) > > I'm not sure if the URLFactory is still the way to go since we > have the Source > interface (Carsten?). > There are two possibilities: The URLFactory and the SourceFactory. If your protocol can be mapped to an existing (= from the jdk supported protocol), e.g. to http, you can simply implement a URL factory. The URLFactory would create e.g. from dbxml:/hallo the real URL "http://dbserver/hallo". Examples for this a the Resource and the Context factory. If this is not possible, you have to implement a SourceFactory which does not create java.net.URL objects but org.apache.cocoon.environment.Source objects. Examples for this are the SourceHandlerImpl and the CocoonSourceFactory. The Source interface is very simple and straightforward, you can look at the URLSource implementation. Carsten > Giacomo > > > > > Ciao, > > > > -- > > Gianugo Rabellino > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > > For additional commands, email: cocoon-dev-help@xml.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org