<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=564321020-18052006><FONT face=Arial size=2>I'm using 6.2.1, and
I'm trying to nest one <contentload> tag within another. I've come
across what seems to be a fairly widely met bug which means that under certain
common circumstances you just can't:</FONT></SPAN></DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial size=2><A
href="http://www.nabble.com/forum/Search.jtp?query=nested+contentload&forum=654">http://www.nabble.com/forum/Search.jtp?query=nested+contentload&forum=654</A></FONT></SPAN></DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial size=2>Has anyone solved
this or found a good workaround? I would happily load XML content
directly, but I need the direct-edit machinery for my users.</FONT></SPAN></DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial size=2>I have an XML
resource with its template-element property set to a JSP template which works
fine under othe circumstances. The outer <contentload> has a
'singleFile' collector, and there are two inner collectors, one after the
other. They're collector implementations of my own class, but I'm fairly
sure that's not where the problem is (though I'd be happy to find any
mistake!). The immediate symptom of the problem is that the second inner
(nested) contentload section doesn't produce any content. On trying to
find out why, I see that an exception has been raised; and on tracking things
down with a debugger, it looks as though (i) OpenCms has recursed and is loading
the original page again, and (ii) the ${opencms.uri} parameter to the outer
collector, when it's called again, is yielding the VFS path to the resource's
JSP template! (That's what gives rise to the eventual Exception - the
template is of course not valid XML.)</FONT></SPAN></DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial
size=2>Jon</FONT></SPAN></DIV>
<DIV><SPAN class=564321020-18052006><FONT face=Arial
size=2></FONT></SPAN> </DIV></BODY></HTML>