> >If you look at the provided C1 docs this was different before.
> >
> How is this different ? The examples do not embed markup as far as your
> example, but they state that " the |<xsp:logic>| element allows for the
> arbitrary nesting of other markup without the need to "prematurely"
> close it"
>
> And the example below this sentence clearly shows that text nodes in
> embedded markup aren't Java code :
>
> <table>
> <xsp:logic>
> for (int i = 0; i < countries.length; i++) {
> <tr>
> <td>
> <xsp:expr>countries[i].getName()</xsp:expr>
> </td>
> <td>
> <xsp:expr>countries[i].getCurrency()</xsp:expr>
> </td>
> </tr>
> }
> </xsp:logic>
> </table>
>
> Notice the <xsp:expr> inside the <td> : if they weren't present,
> "countries[i]..." wouldn't be considered as Java code and thus inserted
> as is in the produced document.
>
> And this is what makes XSP more XML-ish than other dynamic page
> languages : in the XML tree, the <tr> in the above sample are _inside_
> the <xsp:logic>, which is more in accordance with the page logic than
> what you would do with JSP, where there would be 2 java code blocs _at
> the same level_ as the <tr>.
Hm... damn - you are right ;)
I recalled it differently...
> >3) what's the more desired behaviour
> >
> IMO the desired behaviour is the one we have today : as soon as you put
> markup in an <xsp:logic>, you leave Java code to go back to XML content.
Ok, I will shut up then ;)
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
