Michael Wechner wrote:
> > For example, suppose you have something like this
> >
> >
> > http://www.w3.org/xinclude/2000"; src="blah.inc"/>
> > http://apache.org/cocoon/include"; src="blah.inc"/>
> >
>
> >
> > the first tag should *not* be processed by Cocoon, even by an
> > 'including'
Carsten, Conal,
> > But actually my question is about caching of the DirectoryGenerator and
> > sub-classes. It seems to me that these transfomers should also be
> > cacheable;
> > maybe this is just an oversight too? Or is there something tricky
> > I haven't
> > forseen? ;-)
> AFAIK, the direct
Your solution sounds fine to me too.
Michael Wechner wrote:
>
>
> Stefano Mazzocchi wrote:
>
>> Mattam wrote:
>>
>>> Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
>>>
>>> |
>>> | Two almost identical transformers are confusing me.
>>> | What is the difference between the two?
>>> | Shoul
rmer to IncludeTransformer
> > 3) make IncludeTransformer work just on a cocoon-specific namespace
> >
> > what do you think?
>
>
> I think that we should leave XInclude transformer in.
> Many people think Cocoon is hard to learn. Having as many references
as
> po
ld *not* be processed by Cocoon, even by an
> 'including' transformer.
>
> So, IMO, the best long term solution would be:
>
> 1) deprecate both XIncludeTransformer and CIncludeTransformer
> 2) change CIncludeTransformer to IncludeTransformer
> 3) make IncludeTra
Stefano Mazzocchi wrote:
> Mattam wrote:
>
>>Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
>>
>>|
>>| Two almost identical transformers are confusing me.
>>| What is the difference between the two?
>>| Should one be deprecated?
>>|
>>| I'd vote for the one which implements the W3C XInclude
e future for browsers implementing XInclude
> on the client side.
>
In some cases this is true, but not in all. Imagine, fetching a distant
XML document containing xinclude commands. For processing it you need these
extra pieces of information, so you have to include the referenced documen
On Wednesday, June 12, 2002, at 09:10 PM, Stefano Mazzocchi wrote:
> So, IMO, the best long term solution would be:
>
> 1) deprecate both XIncludeTransformer and CIncludeTransformer
> 2) change CIncludeTransformer to IncludeTransformer
> 3) make IncludeTransformer work just on a cocoon-specif
Mattam wrote:
>
> Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
>
> |
> | Two almost identical transformers are confusing me.
> | What is the difference between the two?
> | Should one be deprecated?
> |
> | I'd vote for the one which implements the W3C XInclude spec closest.
> | Maybe it sho
Carsten wrote:
> Ok, first question: for what version are you planning to add
> the caching?
> If for 2.0.2/2.0.3 than the Cacheable interface is the right
> one, if you
> are planning it for 2.1 than CacheableProcesingComponent is
> the correct
> one.
Hmmm ... I haven't looked at 2.1 ... I t
Conal Tuohy wrote:
>
> I've just been looking at "inclusion" recently and noticed that
> the cinclude
> transformer had caching but the xinclude transformer didn't, and
> I wondered
> if there was some arcane reason or was it just a historial
> accide
I've just been looking at "inclusion" recently and noticed that the cinclude
transformer had caching but the xinclude transformer didn't, and I wondered
if there was some arcane reason or was it just a historial accident ;-) And
BTW I think Carsten is right - the inclusion c
>
> Carsten? Donald? Why we have two transformers?
> :)
>
I don't remember the exact reason, but I think Stefano brought this up
originally.
The xinclude transformer implements the xinclude spec, but the cinclude
transformer was invented to bring an easier and more intui
> From: Ivelin Ivanov [mailto:[EMAIL PROTECTED]]
>
> Vadim Gritsenko wrote:
> >>From: Mattam [mailto:[EMAIL PROTECTED]]
> >>
> >>Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
> >>
> >>|
> >>| Two almost identical transformers are confusing me.
> >>| What is the difference between the two?
> >>
Vadim Gritsenko wrote:
>>From: Mattam [mailto:[EMAIL PROTECTED]]
>>
>>Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
>>
>>|
>>| Two almost identical transformers are confusing me.
>>| What is the difference between the two?
>>| Should one be deprecated?
>>|
>>| I'd vote for the one which impleme
IIRC the current XInclude transformer does not support caching.
Geoff Howard
> -Original Message-
> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, June 09, 2002 2:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: XInclude Transformer vs CInlude Transformer
> From: Mattam [mailto:[EMAIL PROTECTED]]
>
> Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
>
> |
> | Two almost identical transformers are confusing me.
> | What is the difference between the two?
> | Should one be deprecated?
> |
> | I'd vote for the one which implements the W3C XInclude sp
> From: Mattam [mailto:[EMAIL PROTECTED]]
> Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
>
> |
> | Two almost identical transformers are confusing me.
> | What is the difference between the two?
> | Should one be deprecated?
> |
> | I'd vote for the one which implements the W3C XInclude spe
Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]:
|
| Two almost identical transformers are confusing me.
| What is the difference between the two?
| Should one be deprecated?
|
| I'd vote for the one which implements the W3C XInclude spec closest.
| Maybe it should take the best of the other on
Two almost identical transformers are confusing me.
What is the difference between the two?
Should one be deprecated?
I'd vote for the one which implements the W3C XInclude spec closest.
Maybe it should take the best of the other one.
--
-= Ivelin =-
--
Hello!
I saw that Cocoon 2 has an XInclude Transformer.
Can anyone tell me if this can be used and if so, how do you parse a
simple xml file, that contains an tag?
Nicu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
gzilla/show_bug.cgi?id=3785
xinclude transformer doesn't resolve relative urls correctly
Summary: xinclude transformer doesn't resolve relative urls
correctly
Product: Cocoon 2
Version: 2.1alpha CVS
Platform: Other
O
22 matches
Mail list logo
