On 07/12/2012 08:14, David Crossley wrote:
I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.
https://issues.apache.org/jira/browse/FOR-1240
Hooray, it works.
That's very good news!
As explained there it would also be good to upgrade so
I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.
https://issues.apache.org/jira/browse/FOR-1240
Hooray, it works.
As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some
Peter Hunsberger wrote:
> We've had to do that on Cocoon 2.x in the past when we had a mix of XSLT
> 1.0 and XSLT 2.0 stylesheets. With XSLT 3.0 coming along you may in fact
> need three xslt processors in a single application...
I remembered stuff from the old C-2.1 docs.
Do Google:
site:cocoon
[
https://issues.apache.org/jira/browse/COCOON-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526130#comment-13526130
]
David Crossley commented on COCOON-2332:
It would be much better to find the actu
[
https://issues.apache.org/jira/browse/COCOON-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526126#comment-13526126
]
David Crossley commented on COCOON-2332:
Forrest documentation
http://forrest.apa
[
https://issues.apache.org/jira/browse/COCOON-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526123#comment-13526123
]
David Crossley commented on COCOON-2332:
These are the links from Samples. The UR
David Crossley created COCOON-2332:
--
Summary: find the missing documentation for the Validation Block
Key: COCOON-2332
URL: https://issues.apache.org/jira/browse/COCOON-2332
Project: Cocoon
We've had to do that on Cocoon 2.x in the past when we had a mix of XSLT
1.0 and XSLT 2.0 stylesheets. With XSLT 3.0 coming along you may in fact
need three xslt processors in a single application...
Peter Hunsberger
On Thu, Dec 6, 2012 at 6:44 PM, Mansour Al Akeel
wrote:
> Ok, I see what you
Ok, I see what you mean now.
Just out of curiosity, why would anyone need to use more than one xslt
processor in one application ??
Thank you.
On Thu, Dec 6, 2012 at 2:50 AM, Robby Pelssers wrote:
> You missed the point Mansour... I meant simultaneously in 1 pipeline.
>
> But thx for thinking a
If I am not wrong, you can always change the implementation for the
xslt processor in the final WAR file by setting:
META-INF/services/javax.xml.transform.TransformerFactory
This is simple and clean.
On Wed, Dec 5, 2012 at 5:21 AM, Robby Pelssers wrote:
> I did some investigation into this ma
10 matches
Mail list logo