Re: strange xinclude problem
I have just experienced the same problem when I tried using multiple
xincludes:
The following styleshhet works fine with the first xinclue only but
throws out Failed to execute pipeline.: org.xml.sax.SAXParseException:
Premature end of file. which is probably caused by some sort of problem
with flow control between the two xinclude's
John_
_
xsl:template match = /dailycollection
xsl:for-each select = //@src:key
xsl:element name=a
xsl:attribute name=href
xsl:value-of select=./
/xsl:attribute
table width=100% border=1tr
tdxi:include
href=http://kun.rte.ie:8080/cocoon/{.}#xpointer(//NewsLines/HeadLine)//td
tdxi:include
href=http://kun.rte.ie:8080/cocoon/{.}#xpointer(/NewsML/NewsItem/NewsComponent/NewsItem/NewsComponent/NewsComponent/Metadata/Property[@FormalName='MediaName']/@Value)//td
/tr/table
/xsl:element
/xsl:for-each
/xsl:template
Torsten Knodt wrote:
Hello Albert,
Hello Albert,
thanks for your fast answer.
I've a little strange problem with xinclude. I get a exception with
Premature end of file, but accessing the URI (cocoon://...)
directly works. Has someone a hint where to look at?
Have you checked if it is a well formed xml file?
I've checked it with xmllint, which gives no errors.
Ok then.
When I look into it, it also seems ok.
And it is created via xml serializer, so I don't know, how it shouldn't
be well formed.
The xml serializer doesn't guarantee that the document is well formed,
xmllint does.
You may access it with cocoon:// but not with xinclude
Is it possible to see, where exactly the problem is? A line number or
the element would be a help.
I don't know if a log transformer after the xinclude would be of any
help... If you want to try it put
xsl:transform type=log
xsl:parameter name=logfile value=filename.log/
/xsl:transform
I believe that as it is within a pipe a process will be thrown for each
transform and it is not necessary that one has finished for the other to
be started so you may log only until where it crashed... it's just an
idea..
I've tried it. It looks OK in my opinion. It also ends with an endDocument.
With kind regards
Torsten Knodt
**
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful.
Please note that emails to, from and within RTÉ may be subject to the Freedom
of Information Act 1997 and may be liable to disclosure.
**
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
To follow up. I can confirm that using cocoon:// instead of http://
resolves the issue.
John
I have just experienced the same problem when I tried using multiple
xincludes:
The following styleshhet works fine with the first xinclue only but
throws out Failed to execute pipeline.: org.xml.sax.SAXParseException:
Premature end of file. which is probably caused by some sort of problem
with flow control between the two xinclude's
John_
_
xsl:template match = /dailycollection
xsl:for-each select = //@src:key
xsl:element name=a
xsl:attribute name=href
xsl:value-of select=./
/xsl:attribute
table width=100% border=1tr
tdxi:include
href=http://kun.rte.ie:8080/cocoon/{.}#xpointer(//NewsLines/HeadLine)//td
tdxi:include
href=http://kun.rte.ie:8080/cocoon/{.}#xpointer(/NewsML/NewsItem/NewsComponent/NewsItem/NewsComponent/NewsComponent/Metadata/Property[@FormalName='MediaName']/@Value)//td
/tr/table
/xsl:element
/xsl:for-each
/xsl:template
**
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful.
Please note that emails to, from and within RTÉ may be subject to the Freedom
of Information Act 1997 and may be liable to disclosure.
**
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello John, my original version has many xincludes, but the stripped down test version, with only one xinclude, I'm currently using has also the problem. And I have already used many xincludes. It works. With kind regards Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9WP99vxZktkzSmiwRAnr3AJsGWSPgXde9oM/85GIAS5QI77hgEwCfc2vT wIDZQv3WiZAYoR3q2XtzmYQ= =SpII -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello John, I'm using cocoon://. I hadn't used http://. With kind regards Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9WQAwvxZktkzSmiwRAoGeAJ9zBnIXvakiz4AOsefEtk1Zjxc+9gCeIlJ3 NqwUf7txi6ZxbsYHHQM+/Ik= =+SZb -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi John, I think with code you mean the xml having the xinclude element. Here is it. It's already a stripped down test version. Oh yes, I'm including from the same machine. What I've seen now is, that the content is included, but the error is still there. With kind regards Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9WQzfvxZktkzSmiwRAl0fAJoDqj9sKNvCmitd99e44m6Hrr72KACfVML1 Y9+TrFvbjeGppsOM/oaoifQ= =vhMh -END PGP SIGNATURE- ?xml version=1.0 encoding=UTF-8? links xmlns=http://hallo/content; xmlns:xlink=http://www.w3.org/1999/xlink; ilink xlink:href=index.xml xlink:type=simple xi:include xmlns:xi=http://www.w3.org/2001/XInclude; href=cocoon://content/index.xml/ /ilink /links - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I've a little strange problem with xinclude. I get a exception with Premature end of file, but accessing the URI (cocoon://...) directly works. Has someone a hint where to look at? Have you checked if it is a well formed xml file? You may access it with cocoon:// but not with xinclude Thanks in advance Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9V9/QvxZktkzSmiwRAvsZAJ948lKGIu1DBt0o+BPXwMUOz7vf9gCfQkhb zADDRBhALxLqO/497dfr2As= =nYuh -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Albert Cervera Areny Dept. Informàtica Sedifa, S.L. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
Can you post some code, I would say that this is more than likely a syntax problem. I'm using xinclude in 2.03 and it works a treat. Are you including via http from a different machine? or is it a local include? Torsten Knodt wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I've a little strange problem with xinclude. I get a exception with Premature end of file, but accessing the URI (cocoon://...) directly works. Has someone a hint where to look at? Thanks in advance Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9V9/QvxZktkzSmiwRAvsZAJ948lKGIu1DBt0o+BPXwMUOz7vf9gCfQkhb zADDRBhALxLqO/497dfr2As= =nYuh -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please note that emails to, from and within RTÉ may be subject to the Freedom of Information Act 1997 and may be liable to disclosure. ** - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Albert, thanks for your fast answer. I've a little strange problem with xinclude. I get a exception with Premature end of file, but accessing the URI (cocoon://...) directly works. Has someone a hint where to look at? Have you checked if it is a well formed xml file? I've checked it with xmllint, which gives no errors. When I look into it, it also seems ok. And it is created via xml serializer, so I don't know, how it shouldn't be well formed. You may access it with cocoon:// but not with xinclude Is it possible to see, where exactly the problem is? A line number or the element would be a help. With kind regards Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9V+5RvxZktkzSmiwRAre3AJ4/EBzlUWkJZ0F273c/yMGlgaoBXwCfUjki W/m+rF+EDWTzvTnN8TrTMXc= =5lJV -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Albert, thanks for your fast answer. I've a little strange problem with xinclude. I get a exception with Premature end of file, but accessing the URI (cocoon://...) directly works. Has someone a hint where to look at? Have you checked if it is a well formed xml file? I've checked it with xmllint, which gives no errors. Ok then. When I look into it, it also seems ok. And it is created via xml serializer, so I don't know, how it shouldn't be well formed. The xml serializer doesn't guarantee that the document is well formed, xmllint does. You may access it with cocoon:// but not with xinclude Is it possible to see, where exactly the problem is? A line number or the element would be a help. I don't know if a log transformer after the xinclude would be of any help... If you want to try it put xsl:transform type=log xsl:parameter name=logfile value=filename.log/ /xsl:transform I believe that as it is within a pipe a process will be thrown for each transform and it is not necessary that one has finished for the other to be started so you may log only until where it crashed... it's just an idea.. With kind regards Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9V+5RvxZktkzSmiwRAre3AJ4/EBzlUWkJZ0F273c/yMGlgaoBXwCfUjki W/m+rF+EDWTzvTnN8TrTMXc= =5lJV -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Albert Cervera Areny Dept. Informàtica Sedifa, S.L. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange xinclude problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Albert, Hello Albert, thanks for your fast answer. I've a little strange problem with xinclude. I get a exception with Premature end of file, but accessing the URI (cocoon://...) directly works. Has someone a hint where to look at? Have you checked if it is a well formed xml file? I've checked it with xmllint, which gives no errors. Ok then. When I look into it, it also seems ok. And it is created via xml serializer, so I don't know, how it shouldn't be well formed. The xml serializer doesn't guarantee that the document is well formed, xmllint does. You may access it with cocoon:// but not with xinclude Is it possible to see, where exactly the problem is? A line number or the element would be a help. I don't know if a log transformer after the xinclude would be of any help... If you want to try it put xsl:transform type=log xsl:parameter name=logfile value=filename.log/ /xsl:transform I believe that as it is within a pipe a process will be thrown for each transform and it is not necessary that one has finished for the other to be started so you may log only until where it crashed... it's just an idea.. I've tried it. It looks OK in my opinion. It also ends with an endDocument. With kind regards Torsten Knodt -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9WA1TvxZktkzSmiwRAhJrAJ9VoGCvdxdPEkes9K131Hb+tAwHkgCaAoHJ ybjIEHr4d8cW/XzznRQKJ3o= =LOj0 -END PGP SIGNATURE- - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
