Joerg Heinicke wrote:
To the others: Is there any reason this transformer is in the batik
block? AFAICS it has nothing to do with batik and is a really simple
transformer.
It was moved into batik block by mistake (the only its usage was in svg
welcome page). Its place is in core, really.
Vad
Sebastian Klamar wrote:
Hi,
is there any special intension (configure component once, run many times
with less if's for performance issues?) to configure the extract-uri
and extract-element for the FragmentExtractorTransformer (batik
block) inside instead of to to make them known via
s?
I have a
On 24.11.2003 23:04, Sebastian Klamar wrote:
* Joerg Heinicke [2003-11-24 20:33 +0100] wrote:
The change would be really easy as you can see if you have a look at
other transformers that are izable - something I could
even do ;-) But I don't have that much time at the moment.
I've done the c
* Joerg Heinicke [2003-11-24 20:33 +0100] wrote:
> The change would be really easy as you can see if you have a look at
> other transformers that are izable - something I could
> even do ;-) But I don't have that much time at the moment.
I've done the changes locally. I could post a bugzilla r
On 24.11.2003 16:45, Sebastian Klamar wrote:
Hi,
is there any special intension (configure component once, run many times
with less if's for performance issues?) to configure the extract-uri
and extract-element for the FragmentExtractorTransformer (batik
block) inside instead of to to make them
Hi,
is there any special intension (configure component once, run many times
with less if's for performance issues?) to configure the extract-uri
and extract-element for the FragmentExtractorTransformer (batik
block) inside instead of to to make them known via
s?
I have a sitemap where I need th
