This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 94731 - Designer does not render contents of verbatim tag when inside of anything other than form.
Summary: Designer does not render contents of verbatim tag when inside of anything oth...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Winston Prakash
Depends on:
Reported: 2007-02-06 19:53 UTC by bugbridge
Modified: 2007-04-30 19:01 UTC (History)
2 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-06 19:53:15 UTC
Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: mako_dev; Suggested Target Milestone : Dev

These items should be added to the Status Whiteboard: WAV

Original submitter: gjmurphy

In a new project, drop a group panel component on the designer. Now drop two
verbatim tags, one inside of the panel, one anywhere else on the page. Switch to
JSP view, add the following content to both verbatim tags:

    <b>Some text in bold.</b>

Notice that text inside of panel does not render. Deploy, and compare the

For simple use cases like this, there is a work-around, which is to put the
markup into the "text" attribute of the static text component, and turn off its
"escape" property. However, the complaints that have surfaced on the forum
involve much larger chunks of code. ALso, it is much easier to author markup in
the JSP editor.

Yes, the issue is there, investigating where is the problem.

Evaluation (Entry 2):
It seems that the renderer doesn't provide the needed data.
Run with switch -J-Dcom.sun.rave.css2.FacesSupport=0 
and you'll see there is nothing from the renderer which designer could show.

For form containing group panel with two verbatims, one in the group panel and
one in the form, the renderer returned something like the below, you can see
only one verbatim is returned from the renderer, but nothing for the group
panel, so there is nothing designer could show.

Passing back to components.

[com.sun.rave.css2.FacesSupport #4] Rendered bean=[FacesDesignBean
instanceName:page1 xxx@xxxx
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="">
        <meta content="no-cache" http-equiv="Pragma"/>
        <meta content="no-cache" http-equiv="Cache-Control"/>
        <meta content="no-store" http-equiv="Cache-Control"/>
        <meta content="max-age=0" http-equiv="Cache-Control"/>
        <meta content="1" http-equiv="Expires"/>
            rel="stylesheet" type="text/css"/>
        <script type="text/javascript">
var sjwuic_ScrollCookie = new sjwuic_ScrollCookie('/rave', '/rave/rave');
        <link href="/resources/stylesheet.css" id="link1" rel="stylesheet"
    <body id="body1" style="-rave-layout: grid">
        <form action="/rave/rave" class="form"
enctype="application/x-www-form-urlencoded" id="form1" method="post">
            <span class="rave-uninitialized-text rave-design-border"
id="groupPanel1" style="height: 310px; left: 144px; top: 96px; position:
absolute; width: 392px; ">Group Panel</span>            <input id="form1_hidden"
name="form1_hidden" type="hidden" value="form1_hidden"/>

Evaluation (Entry 3):
This has nothing to do with renderers. Verbatim has no renderer class, only a
tag class.

The problem is that designer works fundamentally differently than a JSP run-time
engine. It does not invoke the tag classes, and so it has notion of the special
tag methods that allow a tag's content to be output at different moments in the
parsing cycle.

I'm not sure that we can even fix this bug, but it would be a good idea
nonetheless if the designer team could familiarize itself with the tag class
methods, to see if we find a way.

Evaluation (Entry 4):
Designer is not the one who simulates JSP runtime engine, or is supposed to know
anything about JSP/JSF. It doesn't invoke renderes etc. It only renders whatever
html(like) output is passed to it.

The designtime structure which is created based on the sources in created in
insync or jsfsupport. Those parts are responsible for creating the model structure.

Passing to insync first.

Also now the flat for seeing the renderer output is changed to:

Evaluation (Entry 5):
Insync only builds the model using DesignBeans which wraps Components.
Apparently the  verbatim tag does not have a corresponding component. That
causes the problem. As per discussions with Gregory, this could be handled at
disgntime similar to the way reqular html tags are handled using the xhtml

Evaluation (Entry 6):
I don't think adding special design-time component and renderer for verbatim is
a complete solution.

As of JSF 1.2, JSF container components may contain other XHTML markup. The
markup need not be inside of a verbatim tag to be rendered correctly. For
example, consider this simple example:

        <h:panelGrid binding="#{Page1.gridPanel1}" id="gridPanel1">
            <webuijsf:button binding="#{Page1.button1}" id="button1" text="Button"/>
                <b>--- inserted in verbatim ---</b>
            <b>--- inserted outside of verbatim ---</b>
            <webuijsf:button binding="#{Page1.button2}" id="button2" text="Button"/>

At design-time, one sees only two buttons. At run-time, one sees:

    inserted in verbatim
    inserted outside of verbatim

The best way to deal with this is probably to imitate the logic used in the
Faces tag classes. The class tag base class, upon encountering literal markup
inside of a container component's tag, creates new children components for the
markup, with transient set to true. This allows everything, components and
non-component markup, to be rendered correctly, in document order, by the
container component.

We could do the same thing in Creator if we added beginRender() and endRender()
methods to MarkupDesignInfo. A check could be made for markup design bean
children that do not correspond to components, and temporary components could be
created for each. A bug has been filed against JSR 273 asking for the addition
of such methods, see

Suggested Fix:
JSF 1.2 runtime solves this problem by creating temporary components for element
children of component elements for which rendersChildren == true. For next
release, we should investigate a different design-time component hierarchy,
where component instances have all the same children as their DesignBeans,
including "component" instances for all MarkupDesignBeans.
Comment 1 Jayashri Visvanathan 2007-04-30 19:01:04 UTC
This involves some architectural changes to the way components are modeled
during design time. So this is not a target for NB 6.0. I am also changing this
to a feature because of the magnitude of the changes involved.