URL Factory vs Source Handler
Hi, From cocoon.xconf : !-- URL Factory: The url factory adds special url protocols to the system, they are then available inside Cocoon, e.g. as a source argument for one of the sitemap components. -- !-- Source Handler: The source handler adds special url protocols to the system, they are then available inside Cocoon, e.g. as a source argument for one of the sitemap components. -- ok, so how do I choose between URL Factory and Source Handler ? Is the only difference that SourceS are dom/sax compliants when resources can be anything ? Is it only possible to use a Source via SourceFactory registered with its protocol in the SourceHandler or are there other ways ? (and if answer==yes, how come that there is no SitemapSourceFactory ? special case due to SitemapSource loaded to early and then using a default protocol ?) Is there any other starting point for coding my first Source than cocoon SourceS' sources ? thx, fabien. - 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]
Re: URL Factory vs Source Handler
TREGAN Fabien wrote: Hi, From cocoon.xconf : !-- URL Factory: The url factory adds special url protocols to the system, they are then available inside Cocoon, e.g. as a source argument for one of the sitemap components. -- !-- Source Handler: The source handler adds special url protocols to the system, they are then available inside Cocoon, e.g. as a source argument for one of the sitemap components. -- ok, so how do I choose between URL Factory and Source Handler ? Is the only difference that SourceS are dom/sax compliants when resources can be anything ? Use the SourceHandler. Cocoon has donated the Source resolving code to Avalon Excalibur, and they have cleaned it up and made it more general purpose. Cocoon will be using the Excalibur version of source resolving, and URL Factory will go away. Is it only possible to use a Source via SourceFactory registered with its protocol in the SourceHandler or are there other ways ? (and if answer==yes, how come that there is no SitemapSourceFactory ? special case due to SitemapSource loaded to early and then using a default protocol ?) Is there any other starting point for coding my first Source than cocoon SourceS' sources ? thx, fabien. - 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] -- They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin - 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]
RE: URL Factory vs Source Handler
-Original Message- From: TREGAN Fabien [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 25, 2002 4:43 PM To: '[EMAIL PROTECTED]' Subject: RE: URL Factory vs Source Handler TREGAN Fabien wrote: ok, so how do I choose between URL Factory and Source Handler ? The source resolving of Cocoon was donated to avalon excalibur and was there redefined for general purpose. Currently we are in the process of installing the avalon excalibur source resolving. This will replace the source handler, too. ok, but for now, SourceS extends XMLizable, so if URL disapear, how will reader get non-xml datas ? Or will there be a change to AbstractSAXSource so it implements both Source and XMLIzable (and to Source so it no longer extends XMLizable) ? Yes, the new Source interface does not extend XMLizable anymore. Carsten - 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]
