To: users@cocoon.apache.org
Subject: Re: Cocoon 2.1.9 and Saxon 9.6
On 06/05/2016 13:17, Gary Larsen wrote:
Thanks. Was trying to avoid adding a jar.
Im guessing it would look something like this:
URI(source.getURI()).toASCIIString()
new URI(
"file:/C:/a-test
2/netvisn-server-c10
)
throws URISyntaxException
Isn't it possible to just rename the "a-test 2" folder as "a-test2"? ;-)
Regards.
*From:*Francesco Chicchiriccò [mailto:ilgro...@apache.org]
*Sent:* Friday, May 06, 2016 7:02 AM
*To:* users@cocoon.apache.org
*Subject:* Re: Cocoon 2.1.9 and Saxon
@cocoon.apache.org
Subject: Re: Cocoon 2.1.9 and Saxon 9.6
On 06/05/2016 12:51, Gary Larsen wrote:
Hi,
Thanks for the response. I get the space to %20, but have not figured out
where to change the code in Cocoon.
Using this from the stack trace
rror2html.xsl
..which I would hardly qualify as a valid URI :-)
Regards.
*From:*Francesco Chicchiriccò [mailto:ilgro...@apache.org]
*Sent:* Friday, May 06, 2016 2:51 AM
*To:* users@cocoon.apache.org
*Subject:* Re: Cocoon 2.1.9 and Saxon 9.6
On 05/05/2016 18:49, Gary Larsen wrote:
Hi,
icchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, May 06, 2016 2:51 AM
To: users@cocoon.apache.org
Subject: Re: Cocoon 2.1.9 and Saxon 9.6
On 05/05/2016 18:49, Gary Larsen wrote:
Hi,
In order to support JDK 8 it was necessary to update to SaxonHE 9. (cant
remember exactly why right no
On 05/05/2016 18:49, Gary Larsen wrote:
Hi,
In order to support JDK 8 it was necessary to update to SaxonHE 9.
(can’t remember exactly why right now)
New problem is that when the Cocoon app is installed on a path with
spaces (say ‘a-test 2’) there’s a new exception:
(DefaultXMLizer.java:128)
at
org.apache.cocoon.components.xslt.TraxProcessor.sourceToSAX(TraxProcessor.ja
va:303)
at
org.apache.cocoon.components.xslt.TraxProcessor.getTransformerHandlerAndVali
dity(TraxProcessor.java:241)
>From the Saxon website it seems the URI check
Hi Mansour,
I figured you were going to ask that question. In fact I'd reason the same way.
Normally I stick with 1 and only one XSLT processor (Saxon) as it implements
XSLT2.0 while Xalan does not. But I have a use case where indentation of the
output is important. Saxon can do
.
But thx for thinking along.
Robby
-Original Message-
From: Mansour Al Akeel [mailto:mansour.alak...@gmail.com]
Sent: Thursday, December 06, 2012 5:00 AM
To: users@cocoon.apache.org
Cc: d...@cocoon.apache.org
Subject: Re: using both Xalan and Saxon with C3
If I am not wrong, you can
or the one that is reused between concurrent transformations (e.g. xalan
can be used in this mode but it fails with very complex namespaces,
the latest release of xalan handles it correctly though :)
or the one that is the most robust but a bit slower (saxon?)
And use whatever one you want in any match
though :)
or the one that is the most robust but a bit slower (saxon?)
And use whatever one you want in any match of pipeline.
Greetings,
-Greg
2012/12/7 Mansour Al Akeel mansour.alak...@gmail.com
Ok, I see what you mean now.
Just out of curiosity, why would anyone need to use more
...
Robby
-Original Message-
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Tuesday, December 04, 2012 2:21 PM
To: d...@cocoon.apache.org; users@cocoon.apache.org
Subject: using both Xalan and Saxon with C3
Hi guys,
Just wondering how I would configure a C3 project so I could
.
Just thinking out loud here...
Robby
-Original Message-
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Tuesday, December 04, 2012 2:21 PM
To: d...@cocoon.apache.org; users@cocoon.apache.org
Subject: using both Xalan and Saxon with C3
Hi guys,
Just wondering how I
: Re: using both Xalan and Saxon with C3
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
Hi guys,
Just wondering how I would configure a C3 project so I could use both Xalan and
Saxon from my sitemap and java
I currently took the approach to just create a file
META-INF/services/javax.xml.transform.TransformerFactory
With following content:
net.sf.saxon.TransformerFactoryImpl
Van: Francesco Chicchiriccò ilgro...@apache.org
currently there is no implementation of a Saxon-based transformer in Cocoon
3: there is, of course, an XSLT transformer under cocoon-sax [2].
Please fill a JIRA issue on [1] as feature request.
Done.
Huib.
On 25/11/2011 23:33, Huib Verweij wrote:
Hi,
anyone know how to use Saxon as a transformer in Cocoon 3.0? I looked
at cocoon-sample but could not find an example of how to do that.
Google can't find anything either.
Hi,
currently there is no implementation of a Saxon-based transformer
Hi,
anyone know how to use Saxon as a transformer in Cocoon 3.0? I looked at
cocoon-sample but could not find an example of how to do that. Google can't
find anything either.
Hartelijke groet,
Huib Verweij
is not
available. But that will change soon :-)
b. Any ambiguity in template selection (normally a recoverable warning
if you run Saxon from the command line) returns the Ambiguous...
message as an error. Is this configurable? (ie get Saxon to not pass an
error status to Cocoon, but just log
On 17/12/10 08:43, Johan Cwiklinski wrote:
Hello,
[...]
Here is our configuration:
[...]
Hope that could help you :)
Thanks very much, that did it. It was unclear from the docs where you
put the name of the .jar file (saxon9) and where you just put the name
saxon.
One thing that switching
) and where you just put the name
saxon.
One thing that switching to Saxon has done is reveal the holes in my
XSLT :-)
a. If a URI call to Cocoon to retrieve a web page through a Tidy
pipeline (to make it XML) returns an empty file (really null, not even
an empty root element), Xalan treats
the two files (commenting out the Xalan
entries):
- cocoon.xconf:
component logger=core.xslt
role=org.apache.excalibur.xml.xslt.XSLTProcessor/saxon
class=org.apache.cocoon.components.xslt.TraxProcessor
parameter name=use-store value=true/
parameter
Tomcat but I'm not aware of how to restart Cocoon itself.
///Peter
-Original Message-
From: Peter Flynn [mailto:pfl...@ucc.ie]
Sent: Thursday, December 16, 2010 9:58 AM
To: users@cocoon.apache.org
Subject: Switching to Saxon
I just tried this, but there seems to be a lack of up
to Saxon
On 16/12/10 16:23, Schmitz, Jeffrey A wrote:
Taking a quick look, that looks like the same as I did, although I'm
using a saxon9he.jar file. To ask maybe a dumb question, did you
restart Cocoon after adding the jar?
No, I assumed any change would force Tomcat to reread it all.
I
):
- cocoon.xconf:
component logger=core.xslt
role=org.apache.excalibur.xml.xslt.XSLTProcessor/saxon
class=org.apache.cocoon.components.xslt.TraxProcessor
parameter name=use-store value=true/
parameter name=transformer-factory
value
@cocoon.apache.org
Subject: Switching to Saxon
I just tried this, but there seems to be a lack of up-to-date details
on
doing this in Cocoon 2.1.11 with saxon9. Following the assorted web
pages for earlier versions, I got as far as adding saxon9.jar to
Cocoon's WEB-INF/lib and editing
Hi all,
I know you can call static java methods from xslt and even construct new java
objects. But that happens NOT to match my use case.
Short description of my use case:
I have a datasheetbuilder bean defined in my applicationContext:
bean id=datasheetBuilder
think it's a pretty cool solution (workaround) to get performance boosts in
batch processing.
Kind regards,
Robby Pelssers
-Original Message-
From: Robby Pelssers [mailto:robby.pelss...@ciber.com]
Sent: Tuesday, March 09, 2010 4:41 PM
To: users@cocoon.apache.org
Subject: Saxon extensions
I can't give you a performance comparison but I'm always sticking with
SAXON. I'm very happy with it's performance and I've done quite a few
projects.
And one big benefit is that saxon allows me to write xslt in a more
compact way.
Kind regards,
Robby
-Original Message-
From: Kamal
Another topic I would like to point out regarding saxon :
If you like to take advantage of the advanced features of saxon you may leave
the area of free licenses.
And to my experience, saxon's commercial licensing model is unhandable for open
source projects.
Greetings
Andreas
Hi,
I am trying to improve performance for Cocoon. I noticed that XSLT
seems to take a bit of processing time (not lots, but significant to
consider).
Can anyone who is using Saxon for XSLT processing tell me if there is an
improvement in performance (versus using Xalan)? It would be nice
. juillet 2009 18:55
To: Steven D. Majewski; users@cocoon.apache.org
Subject: Re: clueless newbie attempting Saxon, xslt2
On Thu, Jul 23, 2009 at 11:12 AM, Steven D. Majewskisd...@virginia.edu wrote:
If you followed the instructions on that page literally, then the saxon
transformer is going
By the way...
I was just scanning those instructions... I think if you followed them
up you should at least change following line
map:transform src=home.xsl type=xslt2/
Into
map:transform src=home.xsl type=saxon/
Cheers,
Robby
-Original Message-
From
=home.xsl type=xslt2/
Into
map:transform src=home.xsl type=saxon/
Rather than change the user's data, should I instead name Saxon
something else in the top level sitemap.xmap?
Can I call it more than once? Currently in sitemap.xmap I have:
map:transformer name=saxon pool-grow=2
On Thu, Jul 23, 2009 at 11:12 AM, Steven D. Majewskisd...@virginia.edu wrote:
If you followed the instructions on that page literally, then the saxon
transformer is going to be named saxon , not xslt2 :
In my top-level sitemap.xmap, I had this clause (literally lifted from
the instructions I
I don't know if this matters or not, forgive me if the question is dense...
When I built SaxonB, I ended up with .jar files with names all
beginning with saxon9. If I'm referring to saxon in my
sitemap.xmap or my WEB-INF/cocoon.xmap, will Cocoon fail to find that
application
WITH BUFFERING MODE
Calling endElement with uri = loc=table raw=table
I'm really banging my head on this, so any help would be greatly appreciated.
Thanks,
Jeff (see exception below)
org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName
of each element
)
org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName
of each element
at
net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingContentHandler.java:391)
at
net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:277
, here:
http://hcmc.uvic.ca/blogs/index.php?blog=11p=2595more=1c=1tb=1pb=1
(Click through the redirect defeat message if you want to see the crib
sheet I'm working from.)
I have Saxon 9 built, and its .jar files copied into the Cocoon
WEB-INF/lib directory.
I have the user's application
, you'll probably find your problem.
Craig
Abbas Mousavi wrote:
Hi All
newly I replaced Xalan with Saxon, to use some of its features. It works
well
with all of my stylesheets but does not works with stylesheets that use
cocoon:// protocol to access some xml files.
I think that saxon
On Wed, Dec 31, 2008 at 2:11 AM, Mark Lundquist m...@wrinkledog.com wrote:
...Cocoon is serving a web page with a bunch of occurrences of the ndash
character (Unicode #8211). These displayed correctly with the old Saxon,
but now with the new version they instead look like this:
â
On Dec 31, 2008, at 1:25 AM, Bertrand Delacretaz wrote:
On Wed, Dec 31, 2008 at 2:11 AM, Mark Lundquist m...@wrinkledog.com
wrote:
...Cocoon is serving a web page with a bunch of occurrences of the
ndash
character (Unicode #8211). These displayed correctly with the old
Saxon,
but now
Hi All,
I have a Cocoon 2.1.8 application using Saxon, and after a very long
time with no problems, we just stumbled upon a bug in the (now rather
old) version of Saxon that we were using. So I downloaded the latest
Saxon distribution and swapped out the Saxon JAR, and... problem
We had problems with the XmlFileInputModule when having Saxon in the
classpath [4]. The reason for that is that both Xalan and Saxon set
the TransformerFactoryImpl via META-INF/services/
javax.xml.transform.TransformerFactory [1] (Java Services API) and
Saxon was in the load order before
an
internal server error every other request and finally it refused to work at
all. It's the exact same war-file I'm deploying it's the same VM, same
version of Tomcat.
The log-file mentions faillure to load net.sf.saxon.TransformerFactoryImpl,
but I haven't configured my project to use Saxon anywhere. I
map:transformer name=xslt-saxon pool-grow=2 pool-max=32
pool-min=8
src=org.apache.cocoon.transformation.TraxTransformer
use-request-parametersfalse/use-request-parameters
use-browser-capabilities-dbfalse/use-browser-capabilities-
db
xslt-processor-rolesaxon/xslt-processor
Hi Sylvian,
have you tried to add the component to your sitemap.xmap?
cheers
Sylvain Desvé schrieb:
Hi,
I followed the tutorials at http://cocoon.apache.org/1370_1_1.html to
create my first Cocoon application. It worked fine.
But now I need to use Saxon instead of Xalan because my XSLT
I tried it. My sitemap.xmap looks like the following :
map:sitemap ...
map:components
map:transformers default=xslt
map:transformer name=xslt-saxon pool-grow=2 pool-max=32
pool-min=8
src=org.apache.cocoon.transformation.TraxTransformer
use-request-parametersfalse/use
map:transformers default=xslt
map:transformer name=xslt-saxon pool-grow=2 pool-max=32
pool-min=8
src=org.apache.cocoon.transformation.TraxTransformer
use-request-parametersfalse/use-request-parameters
use-browser-capabilities-dbfalse/use-browser-capabilities-db
sitemap.xmap and added a component :
map:components
map:transformers default=xslt
map:transformer name=xslt-saxon pool-grow=2 pool-max=32
pool-min=8
src=org.apache.cocoon.transformation.TraxTransformer
use-request-parametersfalse/use-request-parameters
use-browser
Hi,
I followed the tutorials at http://cocoon.apache.org/1370_1_1.html to
create my first Cocoon application. It worked fine.
But now I need to use Saxon instead of Xalan because my XSLT files are
using XSLT 2.0 features. I found how to do that at http://wiki.apache.org/cocoon/Saxon
instructions (intended for the serialiser) and remain
escaped. Changing the XSLT processor to Saxon does not set Saxon as the
serialiser. If anyone knows how to do that, it would be useful info for
the Saxon page on the Cocoon Wiki.
Just for reference, I encountered this problem with Saxon 8
Hi Slav,
see here: http://wiki.apache.org/cocoon/Saxon
I am running Saxon 9b on 2.1.11 without trouble. I did not have to
remove META-INF from the jar as stated in the article.
Regards,
Johannes
Vyacheslav Sedov schrieb:
Hello!
I need replace Xalan with Saxon in Cocoon (since i use XSLT 2.0
Hello!
I need replace Xalan with Saxon in Cocoon (since i use XSLT 2.0), but
can`t find step by step manual.
With best wishes,
Slav
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Alberto,
this seems to me like a classloading problem. Probably you have
conflicting jars running at the same time in your environment.
Gr.
Reijn
On Mon, 2008-02-11 at 18:49 +0100, Alberto Brosich wrote:
I'm using cocoon 2.1.11 with java 1.6. I defined the saxon transformer
and I use
I'm using cocoon 2.1.11 with java 1.6. I defined the saxon transformer
and I use it in some pipelines. Running it in the embedded jetty works
all fine but after installing the war under tomcat I get the following
error:
java.lang.IllegalArgumentException: Unknown type of result: class
Hi List,
Thanks in advance for any help. I've been playing around with cocoon 2.2,
and need to use XSLT 2.0 for a transformation. After scouring the web I
can't figure out how to integrate Saxon into the new cocoon model. So far
I've created a few Blocks as per the 2.2 tutorials using maven
Spencer Tickner pisze:
Hi List,
Thanks in advance for any help. I've been playing around with cocoon
2.2, and need to use XSLT 2.0 for a transformation. After scouring the
web I can't figure out how to integrate Saxon into the new cocoon model.
So far I've created a few Blocks as per
where the oracle
and odbc classes are listed?
- [Saxon] how do I replace the xalan integration wiht Saxon 8.9.03?
I apologize if I have missed the documentation on this -- I have searched
for discussion groups, books etc.
1. There is a fop-ng block on the trunk. It *might* be as simple
?
- [Saxon] how do I replace the xalan integration wiht Saxon 8.9.03?
I apologize if I have missed the documentation on this -- I have searched
for discussion groups, books etc.
ErstwhileIII
the oracle and odbc classes are listed?
* [Saxon] how do I replace the xalan integration wiht Saxon 8.9.03?
I apologize if I have missed the documentation on this -- I have
searched for discussion groups, books etc.
ErstwhileIII
Hi Joseph,
Attached you'll find a serializer for fop 0.93
Thanks. Yes, I have also compiled the saxon from svn and it worked.thank again.Askild Aaberg Olsen [EMAIL PROTECTED] wrote: Askild Aaberg Olsen wrote: Abbas Mousavi wrote: Hi all recently, there were some posts about integrating Saxon 8.8 to cocoon 1.2.9. and there is no clear answer on the list
Hi allrecently, there were some posts about integrating Saxon 8.8to cocoon 1.2.9. and there is no clear answer on the list. I have also this problem.Is there anyone on the list that used Saxon 8.8with cocoon 1.2.9 successfully? Is this a problem in saxon? or cocoon?Askild Aaberg Olsen [EMAIL
Hi,
I'm trying to use saxon as my XSLT processor instead of Xalan (for
now, in the matching instead of as the default), and
I'm getting the following error:
Message: Lookup of transformer 'xslt-saxon' failed at map:transform
type=xslt-saxon -
file:/C:/webserver_new/cocoon-2.1.8/build
Abbas Mousavi wrote:
Hi all
recently, there were some posts about integrating Saxon 8.8
to cocoon 1.2.9. and there is no clear answer on the list.
I have also this problem.
Is there anyone on the list that used Saxon 8.8
with cocoon 1.2.9 successfully? Is this a problem in saxon? or cocoon
Askild Aaberg Olsen wrote:
Abbas Mousavi wrote:
Hi all
recently, there were some posts about integrating Saxon 8.8
to cocoon 1.2.9. and there is no clear answer on the list.
I have also this problem.
Is there anyone on the list that used Saxon 8.8
with cocoon 1.2.9 successfully
Antonio Gallardo wrote:
Askild Aaberg Olsen escribió:
Jose Miguel Vieira wrote:
Hello,
I’m trying to add saxon 8.8 to cocoon 2.1.9 installed under tomcat 5.5.
We use Saxon 8.7.3 as described the Cocoon Wiki (remember to remove
the META-INF directory), but had no success with 8.8
Hello,
Im trying to add saxon 8.8 to cocoon 2.1.9 installed
under tomcat 5.5.
I followed the instruction in cocoon wiki (http://wiki.apache.org/cocoon/Saxon):
1. Copied saxon jar files into WEB-INF/lib
2. Added a new component to cocoon.xconf:
component
class
Jose Miguel Vieira wrote:
Hello,
I’m trying to add saxon 8.8 to cocoon 2.1.9 installed under tomcat 5.5.
We use Saxon 8.7.3 as described the Cocoon Wiki (remember to remove the
META-INF directory), but had no success with 8.8 (but not a
nullpointerexception)
Askild
Askild Aaberg Olsen escribió:
Jose Miguel Vieira wrote:
Hello,
I’m trying to add saxon 8.8 to cocoon 2.1.9 installed under tomcat 5.5.
We use Saxon 8.7.3 as described the Cocoon Wiki (remember to remove
the META-INF directory), but had no success with 8.8 (but not a
nullpointerexception
Hi Allnewly I replaced Xalan with Saxon, to use some of its features. It works wellwith all of my stylesheets but does not works with stylesheets that usecocoon:// protocol to access some xml files.I think that saxon uses the same URI Resolver as other cocoon components, Is it wrong?
All-new
On 8/29/06, Abbas Mousavi [EMAIL PROTECTED] wrote:
...I replaced Xalan with Saxon, to use some of its features. It works
well with all of my stylesheets but does not works with stylesheets that use
cocoon:// protocol to access some xml files...
Saxon shouldn't make a difference about
...I replaced Xalan with Saxon, to use some of its
features. It works
well with all of my stylesheets but does not works with
stylesheets that use
cocoon:// protocol to access some xml files...
?? I do not understand this anyway? You are fetching some xml blocks within xsl
with cocoon
I use cocoon protocol to read some small bit of data to my stylesheet from an xml file, I know that it can be done with include transformer, but this is not the problem, I want to know "why saxon can not recognize urls starting with cocoon://Ard Schrijvers [EMAIL PROTECTED] wrote: ...I rep
yes, I am reading the xml by document functionfor example document('cocoon://path/to/some/xml.file');Bertrand Delacretaz [EMAIL PROTECTED] wrote: On 8/29/06, Abbas Mousavi <[EMAIL PROTECTED]> wrote: ...I want to know "why saxon can not recognize urls starting with cocoon://In the XS
...I want to know why saxon can not recognize urls
starting with cocoon://
In the XSLT document() function, you mean?
Never noticed this function in XSLT...
Then again, why would Saxon know about the cocoon:// protocol. Xalan perhaps
happens to know, since it is an apache XSLT
Ard Schrijvers a.schrijvers at hippo.nl writes:
...I want to know why saxon can not recognize urls
starting with cocoon://
In the XSLT document() function, you mean?
Never noticed this function in XSLT...
Then again, why would Saxon know about the cocoon:// protocol. Xalan
Abbas Mousavi wrote:
Hi All
newly I replaced Xalan with Saxon, to use some of its features. It
works well
with all of my stylesheets but does not works with stylesheets that use
cocoon:// protocol to access some xml files.
I think that saxon uses the same URI Resolver as other cocoon
On Aug 29, 2006, at 7:39 AM, Askild Aaberg Olsen wrote:
My experience is that if the referenced pipeline fails, Saxon reports
this as unkown protocol cocoon, or something similar.
That is exactly right.
Try invoking the pipeline directly from your browser (if the pipeline
is not internal
/snip
A bit wild guessing, isn't it? ;)
Kind of, yes :-)))
AFAIK there is something like URLHandlers which have to be
registered on the
XSLT processor - but I actually never worked with that API
directly, so I do not
really know. What I wonder about is that Saxon behaves
: Xinclude transformer has changed behaviour with Saxon
8.7.1+
Hi Philip--
I apologize it took so long, but I tried out your testcase and was able
to verify the problem exists in the current SVN version. Would you
please open a JIRA issue at http://issues.apache.org/jira/browse/COCOON
containing
Antonio Gallardo wrote:
Hi Philip,
Did you test the svn 2.1.x branch? There are some fixes for the XInclude
transformer that might help you:
http://issues.apache.org/jira/browse/COCOON-1489
http://issues.apache.org/jira/browse/COCOON-1110
http://issues.apache.org/jira/browse/COCOON-1753
, Cocoon 2.1.8, Tomcat 5.5 and Saxon 8.6.1 or 8.7
configured as the default XSLT transformer I was able to embed
xi:include instructions within source documents and have Cocoon's
Xinclude processor resolve the URL (relative to the source document)
correctly.
e.g.
xi:include href=../../content/resources
and Saxon 8.6.1 or 8.7
configured as the default XSLT transformer I was able to embed
xi:include instructions within source documents and have Cocoon's
Xinclude processor resolve the URL (relative to the source document)
correctly.
e.g.
xi:include href=../../content/resources/site/login.xml
I have previously posted regarding this problem, and have been rather
busy since then, but this time I have an example test case for someone
to mull over.
With Windows XP sp2, Cocoon 2.1.8, Tomcat 5.5 and Saxon 8.6.1 or 8.7
configured as the default XSLT transformer I was able to embed
xi:include
Without knowing what Saxon interfaces are being called here, I'm afraid I
can't help much.
Michael Kay
http://www.saxonica.com/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Fennell, Philip
Sent: 19 June 2006 12:39
To: users@cocoon.apache.org
Sorry,
First time I mailed this it bounced so I sent it again without the
attachment.
So hopefully here is the attachment for the Xinclude problem but this
time as a tar.gz.
Regards
Philip Fennell
xinclude.tar.gz
Description: xinclude.tar.gz
I was previously using Saxon 8.6 as the default XSLT processor and I
make use of the XInclude transformer as follows:
Sitemap fragment
map:match pattern=content/resources/site/*.html
map:generate type=request src=content/resources/site/{1}.xml/
map:transform src=system
If I recall correctly, it is correct to resolve against the source document's locationI thought that too, which made me ask the question in the first place.I followed your link to bugzilla but could not see the relevance.
Either something has been added to or taken away from Saxon
Fennell, Philip wrote:
I was previously using Saxon 8.6 as the default XSLT processor and I
make use of the XInclude transformer as follows:
Sitemap fragment
map:match pattern=content/resources/site/*.html
map:generate type=request src=content/resources/site/{1}.xml
Jason,
My guess is that Saxon 8.6 was actually performing the XInclude
inclusions,
not the xinclude transformer, since as far as I know the transformer
doesn't
have a concept of source document location and resolves relative
paths from
the sitemap context. Perhaps something changed
Fennell, Philip wrote:
Jason,
My guess is that Saxon 8.6 was actually performing the XInclude
inclusions,
not the xinclude transformer, since as far as I know the transformer
doesn't
have a concept of source document location and resolves relative
paths from
the sitemap context
[mailto:[EMAIL PROTECTED]
Sent: 09 May 2006 15:52
To: users@cocoon.apache.org
Subject: Re: Cocoon's Xinclude behaviour changed with Saxon 8.7.1 - Why?
Fennell, Philip wrote:
Jason,
My guess is that Saxon 8.6 was actually performing the XInclude
inclusions,
not the xinclude transformer
Hello,
I can configure Saxon 8 (XSLT2) as the core.xslt-processor using the
following mark-up in cocoon.xconf:
component logger=core.xslt-processor
role=org.apache.excalibur.xml.xslt.XSLTProcessor/saxon
class=org.apache.excalibur.xml.xslt.XSLTProcessorImpl
parameter name=use-store
,
CN
Hello xsl users.
I'm using saxon8 with cocoon 2.1.7. and i can't get rid of
the following
exception:
org.xml.sax.SAXException: Saxon requires an XML parser that
reports the
QName of each element
Browsing the web and i found this never answered post in the cocoon
mailing list:
http
is necessary from the cocoon list as well.
Note that i'm using a xsl files from the cforms examples provided with
cocoon.
TIA,
CN
Hello xsl users.
I'm using saxon8 with cocoon 2.1.7. and i can't get rid of
the following
exception:
org.xml.sax.SAXException: Saxon requires an XML parser
,
CN
Hello xsl users.
I'm using saxon8 with cocoon 2.1.7. and i can't get rid of
the following
exception:
org.xml.sax.SAXException: Saxon requires an XML parser that
reports the
QName of each element
Browsing the web and i found this never answered post in the cocoon
mailing list:
http
Le 14 mai 05, à 00:11, Gregor J. Rothfuss a écrit :
...we use it in production and found it to be lots faster than xalan
(no surprise there). saxon8 is much stricter about XSL syntax than
xalan, so you may have to do some small modifications to your
stylesheets to comply, but saxon has very
to comply, but saxon has very good error reporting, so
that is easy...
Same here, also using saxon8 in production, very happy with it.
There's some info at http://wiki.apache.org/cocoon/Saxon
-Bertrand
Same her, performant and stable.
In addition, you can use the features of XSLT2.0 (not a complete
Le 14 mai 05, à 00:11, Gregor J. Rothfuss a écrit :
...we use it in production and found it to be lots faster than xalan
(no surprise there). saxon8 is much stricter about XSL syntax than
xalan, so you may have to do some small modifications to your
stylesheets to comply, but saxon has
1 - 100 of 186 matches
Mail list logo
