Use facelets as you think it *should* look:
<div class="addItemTable">
<ul class="addItem">
<li><h:commandLink action="#{globalOptionsMgr.addOption}"
value="LABEL" /></li>
</ul>
</div>
Since it doesn't use JSP and therefore JSP tags, there is no need for
verbatim components, as all the source is JSF source.
There are many advantages to facelets. The 3 biggest IMO are
performance, no verbatim tags needed and templating.
Since HTML is really XML (well XHTML is at least), it should not be
necessary to relax the XML parser.
-Andrew
On 8/3/07, Bryan Basham <[EMAIL PROTECTED]> wrote:
> Thanks for the suggestion. I've never used facelets, so would you
> be willing to sketch how this chunk of code would look using that
> technology?
>
> Is there any other solution without using facelets? For example, is
> there a JSP (or Jasper) configuration that will relax the parser?
>
> Thanks,
> Bryan
>
> Andrew Robinson wrote:
> > Use Facelets instead of JSP. You will not need verbatim tags anymore with it
> >
> > On 8/3/07, Bryan Basham <[EMAIL PROTECTED]> wrote:
> >
> >> Hi all,
> >>
> >> I am using JSPX syntax for my JSF pages. I occasionally need to use
> >> raw HTML surrounded by <f:verbatim> tags. However, I am hitting
> >> a problem with the Jasper compiler of these verbatim tags break the
> >> start/end tags of the HTML.
> >>
> >> Here's an example:
> >>
> >> <f:verbatim>
> >> <div class="addItemTable">
> >> <ul class="addItem">
> >> <li></f:verbatim>
> >> <h:commandLink action="#{globalOptionsMgr.addOption}"
> >> value="LABEL" />
> >> <f:verbatim></li>
> >> </ul>
> >> </div>
> >> </f:verbatim>
> >>
> >> The Jasper error I get is:
> >> org.apache.jasper.JasperException:
> >> /dhcp/ConfigureServerOptions.jspx(86,14) The element type "li" must be
> >> terminated by the matching end-tag "</li>".
> >> at
> >> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
> >> at
> >> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:405)
> >> at
> >> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:86)
> >> at
> >> org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:211)
> >>
> >> Does anyone know how to work around this problem?
> >>
> >> Thanks,
> >> Bryan
> >>
> >>
> >>
>
>