If you observe an error on a page, it is sometimes not obvious which view has rendered the
particular fragment of the page. In order to ease debugging, you can set the flag
view.debug.enabled=true in the application.properties file
of your preview web application. If this flag is set, the CAE renders comments with meta
information about the content bean and the view before and behind each fragment of a page. The
output looks like this:
<li class="titlestory first" >
<!--
BEGIN
com.coremedia.blueprint.cae.contentbeans.CMArticleImpl$$[id=454]
asTitleStory webapp resource
view[/WEB-INF/templates/sites/media/com.coremedia.blueprint.common.contentbeans/CMTeasable.asTitleStory.jsp]
-->
<a href="/blueprint/servlet/media/diving/454">
<div class="img-box">
<!--
BEGIN
com.coremedia.blueprint.cae.contentbeans.CMPictureImpl$$[id=446]
null webapp resource
view[/WEB-INF/templates/sites/media/com.corcom.coremedia.blueprint.common.contentbeans.Picture.jsp]
-->
<script type="text/javascript">
com_coremedia_createContextInfo('PBE4',446,null,'mouse',true,null);
</script>
<span data-image-rwd="image-rwd" class="image-rwd">
<span data-max-width="320" data-src="..."> </span>
</span>
<!--
END
com.coremedia.blueprint.cae.contentbeans.CMPictureImpl$$[id=446]
null webapp resource
view[/WEB-INF/templates/sites/media/com.coremedia.com.coremedia.blueprint.common.contentbeans]
-->
</div>
<h4>Scuba diving the underwater adventure</h4>
</a>
<!--
END
com.coremedia.blueprint.cae.contentbeans.CMArticleImpl$$[id=454]
asTitleStory webapp resource
view[/WEB-INF/templates/sites/media/com.coremedia.blueprint.common.contentbeans/CMTeasable.asTitleStory.jsp]
-->
</li>
 |  |  |
 |