James; This behavior comes from the JSP engine. The issue is that the
newlines at the end of tags are part of the template and therefore
appear in the output file. The common solution is to extend JSP tags
across newlines. For example, the following will render JSP in one
line:
This is a bunch of text that will appear <c:if test='${true}'
><sparql:out node="${aRow.age}"/></c:if
> in one line
-- Scott
On Nov 3, 10:54 pm, jlapalme <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We have experimented alot with the JSPs tags in order to generate
> documentation fom our ontology. We have notice that most (if not all)
> of the JSPs tags generate when processed generate alot of unwanted
> line breaks. Would its be possible to correct this ?
> One would expect that the JSP tags would have no effect on the
> outputed text, only the result of the JSP tags. For example, if you
> use a choose tag and you put each when on a different line for
> readability. Even if only one when is taken, all the whens will
> generate an empty line.
>
> Cheers,
>
> James
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TopBraid Composer Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---
