Quoting Nic Ferrier ([EMAIL PROTECTED]):
> I'm wih Jon most of the way here... to be honest I can't see much
> difference between:
>
> $substitution
>
> or
>
> <substitution/>
Do you see a difference here:
<a href="$substitution">$substitution</a>
versus
<a href="<substitution/>"><substitution/></a>
Your only option really if you want to do it in an XML friendly way is
to define it as an entity, and write this:
<a href="&substitution;">&substitution;</a>
but if you try and use an XML parser alone to catch this stuff, it does
become problematic. For example
<option name="hello" value="world" &selected;>
versus
<option name="hello" value="world" $selected>
While you can solve these problems in many cases, you eventually wind up
with a big headache at some point.
However, if it's really important to you, you can plug and play with
WebMacro's parser. It's not integral to the application, and can be
replaced with an XML parser if you like with probably less than 500
lines of code.
Justin
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
