You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Juan Jose Pablos <ch...@apache.org> on 2005/04/07 10:14:33 UTC
Re: X-Versions supported by Forrest
Ferdinand Soethe wrote:
> How can I find out which versions of X-standards are supported in
> Forrest processing. For example is it XPATH 1 or 2?
>
> --
> Ferdinand Soethe
>
>
>
we are using xalan-2.6.1 and that support xpath v1
Cheers,
Cheche
Re: X-Versions supported by Forrest
Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
>
> Thanks, all of you. Now I understand where to look and how to read
> that.
>
> David Crossley wrote:
>
> DC> We had a recent discussion that we need to have a document
> DC> that describes all of this, but no-one has done it.
>
> Have made a note to do that ...
I didn't mean to imply that anyone in particular
should do it.
Thanks anyway and thanks for the other contributions
that you have made via Jira. Those patches certainly help.
--David
Re: X-Versions supported by Forrest
Posted by Ferdinand Soethe <sa...@soethe.net>.
Thanks, all of you. Now I understand where to look and how to read
that.
David Crossley wrote:
DC> We had a recent discussion that we need to have a document
DC> that describes all of this, but no-one has done it.
Have made a note to do that ...
--
Ferdinand
Re: X-Versions supported by Forrest
Posted by David Crossley <cr...@apache.org>.
Antonio Gallardo wrote:
> Ferdinand Soethe dijo:
>
> > So am I correct to assume that Forrest will always use the latest
> > stable release of cocoon (which will always use the latest stable
> > release of xalan) or how is this decided?
>
> We try to stick with this as long as posible. But the reality sometimes is
> not exactly as you described above. Also in Cocoon, there is the same
> policy to use stable "official" releases of the libs. But sometimes we
> need to use a CVS (SVN) version because it fix an important issue. As a
> sample take the current xalan version we use now in forrest:
>
> xalan-2.6.1-dev-20041008T0304.jar
>
> here, "20041008T0304" means we use a xalan built from the CVS. The CVS
> snapshot was from 2004-10-08 Time 03:04 UTC.
>
> This was done because there was an important bugfix for forrest and this
> is the same xalan version shipped currently with cocoon.
This needs clarification. We don't use a stable release
of Cocoon. We use trunk (currently 2.2). We don't stay
on the bleeding edge however. We use a svn revision
that works for us, and update forrest's Cocoon occasionally.
Cocoon has a general policy to use only released
versions of supporting products. At Forrest we don't
have this restriction.
> > I other words is there an easy way to find out what modules are used
> > in any given Forrest release?
>
> If by modules you mean "jars", then see:
>
> http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/
Yes, the best way is to look at your own local version
of forrest in the ./lib/ directories.
> Also there is an important dir "cocoon_upgrade" and see the readme:
>
> http://svn.apache.org/viewcvs.cgi/forrest/trunk/etc/cocoon_upgrade/
>
> > If not, wouldn't this be a useful thing
> > to report somewhere?
>
> If the above don't answer the question, then we need to publish more info.
> :-)
>
> WDYT?
We had a recent discussion that we need to have a document
that describes all of this, but no-one has done it.
--David
Re: X-Versions supported by Forrest
Posted by David Crossley <cr...@apache.org>.
Antonio Gallardo wrote:
> Juan Jose Pablos dijo:
> > Antonio Gallardo wrote:
> >> On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo:
> >>>I other words is there an easy way to find out what modules are used
> >>>in any given Forrest release?
> >>
> >>
> >> If by modules you mean "jars", then see:
> >>
> >> http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/
> >>
> >
> > Maybe we need something like:
> > http://svn.apache.org/repos/asf/cocoon/trunk/lib/jars.xml
>
> Do you mean something like:
>
> http://cocoon.apache.org/2.1/installing/jars.html
Which is automatically built from the file that
Cheche mentioned.
> If yes, we can borrow it from cocoon! ;-)
However we use Cocoon 2.2 version, so that file
does not necessarily relate.
--David
Re: X-Versions supported by Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
On Mar, 12 de Abril de 2005, 14:45, Juan Jose Pablos dijo:
> Antonio Gallardo wrote:
>> On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo:
>>>I other words is there an easy way to find out what modules are used
>>>in any given Forrest release?
>>
>>
>> If by modules you mean "jars", then see:
>>
>> http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/
>>
>
> Maybe we need something like:
> http://svn.apache.org/repos/asf/cocoon/trunk/lib/jars.xml
Do you mean something like:
http://cocoon.apache.org/2.1/installing/jars.html
If yes, we can borrow it from cocoon! ;-)
Best Regards,
Antonio Gallardo.
Re: X-Versions supported by Forrest
Posted by Juan Jose Pablos <ch...@apache.org>.
Antonio Gallardo wrote:
> On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo:
>>I other words is there an easy way to find out what modules are used
>>in any given Forrest release?
>
>
> If by modules you mean "jars", then see:
>
> http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/
>
Maybe we need something like:
http://svn.apache.org/repos/asf/cocoon/trunk/lib/jars.xml
Re: X-Versions supported by Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
On Mar, 12 de Abril de 2005, 12:01, Ferdinand Soethe dijo:
>
> Antonio Gallardo wrote:
>
> AG> Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT
> AG> processor. Saxon supports xpath v2. That means is posible to use xpath
> v2
> AG> right now in forrest.
>
> Thanks. That is good to know. If I really need XPath 2 I'll try to figure
> out how.
I believe it is not too dificult:
http://wiki.apache.org/cocoon/Saxon
> But I think I'd rather stick with the standard distribution as
> long as I can.
:-)
> So am I correct to assume that Forrest will always use the latest
> stable release of cocoon (which will always use the latest stable
> release of xalan) or how is this decided?
We try to stick with this as long as posible. But the reality sometimes is
not exactly as you described above. Also in Cocoon, there is the same
policy to use stable "official" releases of the libs. But sometimes we
need to use a CVS (SVN) version because it fix an important issue. As a
sample take the current xalan version we use now in forrest:
xalan-2.6.1-dev-20041008T0304.jar
here, "20041008T0304" means we use a xalan built from the CVS. The CVS
snapshot was from 2004-10-08 Time 03:04 UTC.
This was done because there was an important bugfix for forrest and this
is the same xalan version shipped currently with cocoon.
> I other words is there an easy way to find out what modules are used
> in any given Forrest release?
If by modules you mean "jars", then see:
http://svn.apache.org/viewcvs.cgi/forrest/trunk/lib/
Also there is an important dir "cocoon_upgrade" and see the readme:
http://svn.apache.org/viewcvs.cgi/forrest/trunk/etc/cocoon_upgrade/
> If not, wouldn't this be a useful thing
> to report somewhere?
If the above don't answer the question, then we need to publish more info.
:-)
WDYT?
Best Regards,
Antonio Gallardo
Re: How to use a different transformer
Posted by Antonio Gallardo <ag...@agssa.net>.
Ferdinand Soethe wrote:
>My main question really is:
>
>Would I only have to replace (in sitemap.xmap)
>
>
>
>><map:transformers default="xslt">
>>
>>
>
>with
>
>
>
>><map:transformers default="xslt-saxon">
>>
>>
>
>to use Saxon in as default in all my my Forrest-transformations? Is it
>that easy?
>
Hi:
Sorry for my late reply.
To be 100% you are using saxon, I will suggest also to rename the saxon
transformer to "xslt". That way you will not need to change nothing in
the code.
Also check if in other parts of the code is not used "xsltc" or "xalan".
Best Regards,
Antonio Gallardo.
Re: How to use a different transformer
Posted by Ross Gardler <rg...@apache.org>.
Ferdinand Soethe wrote:
>
>
>
>
>
>
>
>
> David Crossley wrote:
>
>>There is not much core Cocoon documentation about replacing
>>Xalan with Saxon, but there is a useful page at
>>http://wiki.apache.org/cocoon/Saxon
>
>
>>Remember that with the power of the Cocoon sitemap
>>you can use the default Xalan for most processing
>>and just use Saxon for certain pipelines. Or use
>>Saxon for everything.
>
>
> Thanks for the links. I had already found most of them but I'm not
> sure how everything fits together.
>
> My main question really is:
>
> Would I only have to replace (in sitemap.xmap)
>
>
>><map:transformers default="xslt">
>
>
> with
>
>
>><map:transformers default="xslt-saxon">
>
>
> to use Saxon in as default in all my my Forrest-transformations? Is it
> that easy?
It should be, just try it and let us know if it is ;-)
Ross
Re: How to use a different transformer
Posted by Ferdinand Soethe <fe...@apache.org>.
David Crossley wrote:
> There is not much core Cocoon documentation about replacing
> Xalan with Saxon, but there is a useful page at
> http://wiki.apache.org/cocoon/Saxon
> Remember that with the power of the Cocoon sitemap
> you can use the default Xalan for most processing
> and just use Saxon for certain pipelines. Or use
> Saxon for everything.
Thanks for the links. I had already found most of them but I'm not
sure how everything fits together.
My main question really is:
Would I only have to replace (in sitemap.xmap)
> <map:transformers default="xslt">
with
> <map:transformers default="xslt-saxon">
to use Saxon in as default in all my my Forrest-transformations? Is it
that easy?
--
Ferdinand Soethe
Re: How to use a different transformer
Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
> Thanks for any help on this.
There is not much core Cocoon documentation about replacing
Xalan with Saxon, but there is a useful page at
http://wiki.apache.org/cocoon/Saxon
Remember that with the power of the Cocoon sitemap
you can use the default Xalan for most processing
and just use Saxon for certain pipelines. Or use
Saxon for everything.
-David
How to use a different transformer (Was Re: X-Versions supported by Forrest)
Posted by Ferdinand Soethe <fe...@apache.org>.
> Ferdinand Soethe wrote:
>> Antonio Gallardo wrote:
>> Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT
>> processor. Saxon supports xpath v2. That means is posible to use xpath v2
>> right now in forrest.
> Thanks. That is good to know. If I really need XPath 2 I'll try to figure out
> how. But I think I'd rather stick with the standard distribution as
> long as I can.
OK, time to follow up on this. I now do need XPATH and XSLT2 and
would like to use Saxon instead.
As far as I understand sitemap.xmap configures
> <map:transformers default="xslt">
Which I read as saying that the default transformer is xslt (further
down resolved to org.apache.cocoon.transformation.TraxTransformer)
and also offers Saxon as an alternative
> <map:transformer name="xslt-saxon"
> pool-grow="2" pool-max="32" pool-min="8"
> src="org.apache.cocoon.transformation.TraxTransformer">
> <use-request-parameters>false</use-request-parameters>
> <use-browser-capabilities-db>false</use-browser-capabilities-db>
> <xslt-processor-role>saxon</xslt-processor-role>
> </map:transformer>
So my conclusion would be that I'd only have to replace
> <map:transformers default="xslt">
with
> <map:transformers default="xslt-saxon">
to use Saxon in my Forrest.
However in main\webapp\WEB-INF\xconf\forrest-core.xconf I found
> <!--+
> | XSLT Processor
> |
> | 'incremental-processing' (only works with Xalan) allows the XSLT
> | processor to start the output of the transformation as soon as possible.
> | if set to false, the transforer waits until the end of the
> | transformation to deliver the output.
> | WARNING: * if you enable incremental-processing, you should be aware of
> | the following bug:
> | http://issues.apache.org/bugzilla/show_bug.cgi?id=13186
> | * incremental-processing creates an additional, non-pooled thread.
> | * using incremental-processing does not save memory, the input
> | tree will still be build completely.
> | * incremental processing is a 'static' thing in Xalan: if you
> | enable it on one xslt-processor, enable it on all.
> +-->
> <xslt-processor logger="core.xslt-processor">
> <parameter name="use-store" value="true"/>
> <parameter name="incremental-processing" value="false"/>
> </xslt-processor>
>
> <!--+
> | XSLT Processor using xsltc from Xalan
> | For Interpreted Xalan use:
> | <transformer-factory>org.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
> +-->
> <component class="org.apache.excalibur.xml.xslt.XSLTProcessorImpl" logger="core.xslt-processor" role="org.apache.excalibur.xml.xslt.XSLTProcessor/xsltc">
> <parameter name="use-store" value="false"/>
> <parameter name="transformer-factory" value="org.apache.xalan.xsltc.trax.TransformerFactoryImpl"/>
> </component>
>
> <!--+
> | Xalan XSLT Processor
> +-->
> <component class="org.apache.excalibur.xml.xslt.XSLTProcessorImpl" logger="core.xslt-processor" role="org.apache.excalibur.xml.xslt.XSLTProcessor/xalan">
> <parameter name="use-store" value="false"/>
> <parameter name="incremental-processing" value="false"/>
> <parameter name="transformer-factory" value="org.apache.xalan.processor.TransformerFactoryImpl"/>
> </component>
>
> <!--+
> | Saxon XSLT Processor
> | For old (6.5.2) Saxon use:
> | <parameter name="transformer-factory" value="com.icl.saxon.TransformerFactoryImpl"/>
> | For new (7+) Saxon use:
> | <parameter name="transformer-factory" value="net.sf.saxon.TransformerFactoryImpl"/>
> +-->
> <map:transformers default="xslt">
and I'm not sure how these are related. Do I need to worry about that
at all.
And will setting the default transformer also make Forrest use
it for processing XPATH expression (because I see that the above
mentioned file configures that separately)
<!-- Xpath Processor: -->
<xpath-processor class="org.apache.excalibur.xml.xpath.XPathProcessorImpl" logger="core.xpath-processor"/>
Thanks for any help on this.
--
Ferdinand Soethe
Re: X-Versions supported by Forrest
Posted by Ferdinand Soethe <sa...@soethe.net>.
Antonio Gallardo wrote:
AG> Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT
AG> processor. Saxon supports xpath v2. That means is posible to use xpath v2
AG> right now in forrest.
Thanks. That is good to know. If I really need XPath 2 I'll try to figure out
how. But I think I'd rather stick with the standard distribution as
long as I can.
So am I correct to assume that Forrest will always use the latest
stable release of cocoon (which will always use the latest stable
release of xalan) or how is this decided?
I other words is there an easy way to find out what modules are used
in any given Forrest release?
If not, wouldn't this be a useful thing
to report somewhere?
Thanks,
Ferdinand Soethe
Re: X-Versions supported by Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
On Mar, 12 de Abril de 2005, 9:46, Ferdinand Soethe dijo:
>
> Juan Pablos wrote:
>
> JJP> we are using xalan-2.6.1 and that support xpath v1
>
> Thanks! Any idea when this will change to support xpath v2? There are
> soo many useful functions in it.
Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT
processor. Saxon supports xpath v2. That means is posible to use xpath v2
right now in forrest.
Best Regards,
Antonio Gallardo.
Re: X-Versions supported by Forrest
Posted by Juan Jose Pablos <ch...@apache.org>.
Ferdinand Soethe wrote:
> Juan Pablos wrote:
>
> JJP> we are using xalan-2.6.1 and that support xpath v1
>
> Thanks! Any idea when this will change to support xpath v2? There are
> soo many useful functions in it.
This is what I have found:
http://marc.theaimsgroup.com/?t=106206477300001&r=1&w=2
saxon support xpath 2.0 BTW
>
> --
> Ferdinand Soethe
>
>
>
Re: X-Versions supported by Forrest
Posted by Ferdinand Soethe <sa...@soethe.net>.
Juan Pablos wrote:
JJP> we are using xalan-2.6.1 and that support xpath v1
Thanks! Any idea when this will change to support xpath v2? There are
soo many useful functions in it.
--
Ferdinand Soethe