Content Application Developer Manual / Version 2310
Table Of Contents
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
cae.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 comment behind each
fragment also contains the time it took (in milliseconds) to render the fragment including its children. 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]
-->
<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]
took 31ms
-->
</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]
took 58ms
-->
</li>
