I wondered that as I was typing it. I was referring to a problem reported
earlier by Andrew Court. Turns out it was a Long comparison that was the
problem, not String comparison. Here's the thread.
http://old.nabble.com/1.5.4-upgrade-and-layout-component-problem-to30211356.html#a30211356
<http://old.nabble.com/1.5.4-upgrade-and-layout-component-problem-to30211356.html#a30211356>
-Ben
2010/12/28 Grzegorz Krugły <[email protected]>
> W dniu 28.12.2010 18:22, Ben Gunter pisze:
> > The only thing I know of that you won't be able to do is something
> > like <c:if test="${'1' == someLayoutComponent}">...</c:if> where you
> > try to treat the layout component contents as a String in an EL
> > expression. They were actually Strings before, but now they're
> > instances of LayoutComponentRenderer.
>
> Just out of pure curiousity since I'm not comparing like that anywhere
> -- wouldn't it still work since LayoutComponentRenderer.toString() will
> get called? == in EL calls String.equals AFAIK.
>
>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
