You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Gianugo Rabellino <gi...@apache.org> on 2002/08/12 09:42:47 UTC
XLink anyone?
Hi,
I'm experiencing weird problems with XLink while trying to process an
OpenOffice document (yes, I'm working on a filter, hope it might be
useful to all of us).
I'm ending up with a java.lang.StackOverflow error with Cocoon trying to
process an xlink in a (too much) recursive way. I'm trying to understand
where the real problem is, but I'm a bit confused about how (and why,
actually) Cocoon is processing XLinks.
I'm attaching the offending document, which is, BTW, just the example
taken from http://www.chez.com/ebellot/ooo2sdbk/, the tool I'm trying to
"clone" on Cocoon. To reproduce the problem it's enough to have Cocoon
parse the XML:
<match="whatever">
<generate src="content.xml"/>
<serialize/>
</match>
You will see that Cocoon chokes while trying to process the png image
referenced as an xlink. Any clues?
TIA,
--
Gianugo Rabellino
Re: XLink anyone?
Posted by Gianugo Rabellino <gi...@apache.org>.
Joerg Heinicke wrote:
> If you only have
>
> <match="whatever">
> <generate src="content.xml"/>
> <serialize/>
> </match>
>
> Cocoon will only parse the file and serialize it. Where should the
> handling of XLink's come from?
>
> I tested with a 2.0.2-dev version from march. Cocoon chokes only on the
> missing DTD, so I removed the doctype declaration and everything works
> fine.
Hmmm... wait: have you tried the CLI version too? I did the tests on
that, this might be the problem, since the CLI actually deals with
XLinks (in order to process recursively the pages). The problem might be
there. I'll give it a try in a servlet environment, but I still suspect
that a bug is lying around. Can you please try the CLI version?
TIA,
--
Gianugo Rabellino
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: XLink anyone?
Posted by Joerg Heinicke <jo...@gmx.de>.
If you only have
<match="whatever">
<generate src="content.xml"/>
<serialize/>
</match>
Cocoon will only parse the file and serialize it. Where should the handling
of XLink's come from?
I tested with a 2.0.2-dev version from march. Cocoon chokes only on the
missing DTD, so I removed the doctype declaration and everything works fine.
Joerg
Gianugo Rabellino wrote:
> Joerg Heinicke wrote:
>
>> Why should Cocoon choke on parsing an XML file - if it is really one??
>> The parser doesn't know anything about XLink, so I think this can't be
>> the problem. Have a look at the XML. It looks really strange.
>
>
> The parser doesn't. Cocoon does. Have a look at the source, Cocoon
> actually knows about xlink, both as "proper" xlinks (in the xlink:
> namespace) and as "semi" xlinks (the "href" and "src" attributes). The
> problem is that it does it in such a way that makes the app go nuts,
> with a StackOverflow exception and (from a quick and dirty debugging
> session) a set of recursive calls between XLinkPipe(s).
>
>> I downloaded the example SXW from the link you gave, unzipped it and
>> looked at the content.xml (delivered via Cocoon) in Mozilla. Maybe you
>> made an error while unzipping the SXW.
>
>
> So did I, and I double checked, with Mozilla, IE, command line Xerces &
> Xalan... all behaved well, Cocoon being the exception. Try for yourself.
>
> Ciao,
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: XLink anyone?
Posted by Gianugo Rabellino <gi...@apache.org>.
Joerg Heinicke wrote:
> Why should Cocoon choke on parsing an XML file - if it is really one??
> The parser doesn't know anything about XLink, so I think this can't be
> the problem. Have a look at the XML. It looks really strange.
The parser doesn't. Cocoon does. Have a look at the source, Cocoon
actually knows about xlink, both as "proper" xlinks (in the xlink:
namespace) and as "semi" xlinks (the "href" and "src" attributes). The
problem is that it does it in such a way that makes the app go nuts,
with a StackOverflow exception and (from a quick and dirty debugging
session) a set of recursive calls between XLinkPipe(s).
> I downloaded the example SXW from the link you gave, unzipped it and
> looked at the content.xml (delivered via Cocoon) in Mozilla. Maybe you
> made an error while unzipping the SXW.
So did I, and I double checked, with Mozilla, IE, command line Xerces &
Xalan... all behaved well, Cocoon being the exception. Try for yourself.
Ciao,
--
Gianugo Rabellino
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: XLink anyone?
Posted by Joerg Heinicke <jo...@gmx.de>.
Why should Cocoon choke on parsing an XML file - if it is really one?? The
parser doesn't know anything about XLink, so I think this can't be the
problem. Have a look at the XML. It looks really strange.
I downloaded the example SXW from the link you gave, unzipped it and looked
at the content.xml (delivered via Cocoon) in Mozilla. Maybe you made an
error while unzipping the SXW.
Regards,
Joerg
Gianugo Rabellino wrote:
> Hi,
>
> I'm experiencing weird problems with XLink while trying to process an
> OpenOffice document (yes, I'm working on a filter, hope it might be
> useful to all of us).
>
> I'm ending up with a java.lang.StackOverflow error with Cocoon trying to
> process an xlink in a (too much) recursive way. I'm trying to understand
> where the real problem is, but I'm a bit confused about how (and why,
> actually) Cocoon is processing XLinks.
>
> I'm attaching the offending document, which is, BTW, just the example
> taken from http://www.chez.com/ebellot/ooo2sdbk/, the tool I'm trying to
> "clone" on Cocoon. To reproduce the problem it's enough to have Cocoon
> parse the XML:
>
> <match="whatever">
> <generate src="content.xml"/>
> <serialize/>
> </match>
>
> You will see that Cocoon chokes while trying to process the png image
> referenced as an xlink. Any clues?
>
> TIA,
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org