[opencms-dev] VFS target "/path/filename.jsp" was alreadyincluded earlier

[mwpowell at adelphia.net]

For the benifit of others here I have a solution and the root cause which was located in the template code. 

This issue developed as I followed the how-to template instructions to the letter. However, this causes certain elements to encounter this recursive treatment when used in conjunction with other jsp pages (as close as I can tell).

Essentially, the how-to instructions call for the inclusion of a tag within the template which includes the template a second time.

<cms:template element="body">
<cms:include element="body" editable="true"/>
<!--some html code here-->
</cms:template>

The second line which uses the cms:include tag is incorrect. I think the example given is trying to demonstrate the ability to include editable elements in the html, but this does not work with jsp pages. 

The correct tags to be used for jsp pages is as follows:

<cms:template element="body">
<!--some html code here-->
</cms:template>

While the how-to examples given may be fine for html pages, jsp pages will always throw an error, becuase it is trying to create an editable element within the jsp page. There should be some sort of explaination on this subject or seperate examples for templates for use in jsp pages.

Many thanks to all those who offered suggestions.


Mike



---- "Christoph P. Kukulies" <kuku at physik.rwth-aachen.de> wrote: 
> On Wed, Feb 01, 2006 at 08:54:36AM +0000, Jonathan Woods wrote:
> > Maybe this is obvious, but... it sounds like some kind of recursion.
> > 
> > Jon 
> > 
> > -----Original Message-----
> > Subject: Re: [opencms-dev] VFS target "/path/filename.jsp" was
> > alreadyincluded earlier
> > 
> > Panos,
> > 
> ...
> > Is there some type of 'global' setting or opencms level setting that I am
> > missing?
> > 
> > I should note that the template seems to be used fine on other html pages,
> > but the jsp page results in the error.
> > 
> > Mike
> 
> I saw this "multiple inclusion" error a couple of times when doing first 
> steps experimenting with jsps.
> 
> Not knowing the exact context under which this happens in your case, 
> I remember that changing the template property and attaching it to a different
> property, like template-elements, was helping in my case. (so to say, abusing
> a property for that purpose).
> 
> You should probably supply more information and an example to
> repeat the effect in case it should be fruitful for others to 
> participate in understanding the problem.
> 
> --
> Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev