Sylvain Wallez wrote:
I don't like all those static methods that hardcode more and more logic,
and even less when they lookup some components...
Why aren't these methods part of a CocoonResolver component that would
extend Excalibur's SourceResolver with some XML-related features ?
You
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
I don't like all those static methods that hardcode more and more logic,
and even less when they lookup some components...
Why aren't these methods part of a CocoonResolver component that would
extend Excalibur's SourceResolver with some
Sylvain Wallez wrote:
I don't know if this should be an independent component, or one that
extends the SourceResolver.
Ah ok, by independent component I meant a component that extends
perhaps the SourceResolver component from Avalon, but can still be
looked up using a component manager. So
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
I don't know if this should be an independent component, or one that
extends the SourceResolver.
Ah ok, by independent component I meant a component that extends
perhaps the SourceResolver component from Avalon, but can still be
looked up
There is already such a component, the cinclude transformer uses this
for the caching. It should be easy to use that component in the
xinclude transformer as well.
PS: Could you please not include the PGP signature in your posts to
this list. It makes reading your mails very hard. Thanks.
On Sunday 01 June 2003 15:47, Carsten Ziegeler wrote:
CZ There is already such a component, the cinclude transformer uses this
CZ for the caching. It should be easy to use that component in the
CZ xinclude transformer as well.
Yes, I know. But it'S still to much coding for it in the
Torsten Knodt wrote:
Yes, I know. But it'S still to much coding for it in the
CIncludeTransformer.
Components which need the content of a source, should simply get
it, and not
think about caching. It's not their job. Caching is needed in to
many places.
All places which use sources,
Torsten Knodt wrote:
On Sunday 01 June 2003 15:47, Carsten Ziegeler wrote:
CZ There is already such a component, the cinclude transformer uses this
CZ for the caching. It should be easy to use that component in the
CZ xinclude transformer as well.
Please, add a blank line before the reply, this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have looked at cocoon caching and it seems, that components do the caching
for sources, DOM's and SAX events on their own. I wanted to make XInclude
transformer cacheable, but this would only double code. Now I'm thinking of
moving this somewhere
