Re: Using Saxon transformer together with Xalan and XSLTC

2003-06-30 Thread Peter Velychko 
Hi,

PV I try to use Saxon 7.6 together with Xalan
PV There is the following warning in the logs when I try to place
PV saxon.jar to WEB-INF/lib:

PV Date:   Mon Jun 30 14:01:53 EEST 2003 (1056970913164)
PV Thread: PoolThread-4
PV Message #:  1
PV Level:  WARN
PV NDC:
PV Category:   sitemap.serializer.xhtml
PV Message:Cannot know if transformer needs namespaces attributes - assuming 
NO.
PV Location:   
org.apache.avalon.framework.logger.LogKitLogger.warn(LogKitLogger.java:159)
PV Thrown:
PV org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName of 
each element
PV at net.sf.saxon.event.ContentEmitter.getNameCode(ContentEmitter.java:170)
PV at net.sf.saxon.event.ContentEmitter.startElement(ContentEmitter.java:128)
PV at 
org.apache.cocoon.serialization.AbstractTextSerializer.needsNamespacesAsAttributes(AbstractTextSerializer.java:341)
PV at 
org.apache.cocoon.serialization.AbstractTextSerializer.configure(AbstractTextSerializer.java:268)
PV at 
org.apache.cocoon.serialization.XMLSerializer.configure(XMLSerializer.java:76)
PV ...

PV The result is the HTML and XHTML serializers work properly only after
PV Saxon transformer. They work incorrectly after XSLT and Xalan
PV transformers (f.e. the attribute href isn't generated, although as
PV far as I've found the xml-s after all transformers are the same).

My apologies, but the same is the input xml. The output xml-s are
different:

for Saxon -
?xml version=1.0 encoding=UTF-8?
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en
head
titleSamples/title
meta http-equiv=Content-Type content=text/xhtml; charset=UTF-8/
link href=/styles/main.css type=text/css rel=stylesheet/
/head
body
h1List/h1
p xmlns= class=block2
Sample 1 - 
a href=examples/linotype/view/a
/p
p xmlns= class=block2
Sample 2 - 
a href=examples/charts/view/a
/p
/body
/html


for Xalan -
?xml version=1.0 encoding=UTF-8?
html xmlns=http://www.w3.org/1999/xhtml;
head xmlns=http://www.w3.org/1999/xhtml;
title xmlns=http://www.w3.org/1999/xhtml;Samples/title
meta xmlns=http://www.w3.org/1999/xhtml/
link xmlns=http://www.w3.org/1999/xhtml/
/head
body xmlns=http://www.w3.org/1999/xhtml;
h1 xmlns=http://www.w3.org/1999/xhtml;List/h1
p xmlns=http://www.w3.org/1999/xhtml; xmlns=
Sample 1 - 
a xmlns=http://www.w3.org/1999/xhtml; xmlns=view/a
/p
p xmlns=http://www.w3.org/1999/xhtml; xmlns= xmlns=
Sample 2 - 
a xmlns=http://www.w3.org/1999/xhtml; xmlns= xmlns=view/a
/p
/body
/html

So there is duplicating xmlns attributes in XML generated by Xalan.

PV My emviroment is Win2000, jdk1.4.1_02, Jetty4.2.9, Cocoon2.1m3-dev


-- 
Best regards,
 Petermailto:[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Using Saxon transformer together with Xalan and XSLTC

2003-06-30 Thread J.Pietschmann 
Peter Velychko wrote:
So there is duplicating xmlns attributes in XML generated by Xalan.
Could it be that the AElfred parser from the saxon jar kicks in?
IT is known to report namespace attributes differently than Xerces
which may cause hickups in some Xalan versions (unfortunately,
this is a dark corner in the SAX spec).
Try to remove the services entry from the saxon jar and see whether
the problem persists. it this fails, see whether you can import the
XML parser functionality from the servlet container rather than the
webapp lib.
OTOH, it could be the XML parser imported from the servlet container
which causes problems. Try to use the Xerces component instead of the
SAXParser component to exclude this possiblity.
J.Pietschmann

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]