cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Engelhart <>
Subject Re: JDOM import and Cocoon 1.8
Date Wed, 07 Nov 2001 18:09:51 GMT

Yes the XSP processor uses DOM to process the page so the Document 
instance is created automatically.
Since you haven't instantiated any JDOM classes I'm not sure why it's 
getting hung up but it's clearly getting confused about what Document 
object you're referencing when trying to compile your XSP into a java 
class.   My suggestion still stands to put the full package name in the 
xsp:include or don't bother using the <xsp:include> and if you need a 
JDOM  class, always call it by the package name.   Try that and let us 
know how it works.


On Wednesday, November 7, 2001, at 12:59 PM, Ted Mead wrote:

> Mike,
> I haven't instantiated any Document classes yet, but apparently the XSP
> processor has.  I'm not sure what I'm doing wrong that the XSP processor
> doesn't differentiate between org.w3c.dom.Document and 
> org.jdom.Document.  I
> have only used the <xsp:include> statement and have not used the jdom
> classes yet in any other way.  Any ideas?
> Thanks,
> Amy

Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message