Please look into the generated java code. There
should be no space between <util:expr>
and <xsp:expr>. The reason is that the whitespace
is not ignored and during compilation of the XSP, the method calls that gets
generated from <util:expr>
<xsp:expr> will erroneous. Regds, Chiths accordia,
inc 650
279 1137 The information contained
in this communication is intended solely for the use of the individual or
entity to whom it is addressed and others authorized to receive it. It may
contain confidential or legally privileged information. If you are not the
intended recipient you are hereby notified that any disclosure, copying,
distribution or taking any action in reliance on the contents of this
information is strictly prohibited and may be unlawful. If you have received
this communication in error, please notify us immediately by responding to this
email and then delete it from your system. -----Original Message----- Thanks, it works! Can you spot the difference between
the two code fragments? The first one works, the second does not. This works: === <?xml
version="1.0"?> === This does not: === <?xml
version="1.0"?> === There is a single space between
<util:expr> and <xsp:expr> in the second one. Touchy, touchy! ;-) Thanks again. Larry If u use just xsp:expr,
it will treat the o/p as parsed
string , if you require the contents to be treated as a XML fragment,
you need to do as listed below Include util logic sheet and use the <util:* >tags === <?xml
version="1.0"?> </page></xsp:page> |
- RE: Help: xml from a class with XSP (thanks..and a note) Larry Meadors
- Chitharanjan Das