Re: OGNL && causes weird erro

[Jesse Kuhnert <jk...@gmail.com>]

Replace && with &&

On 10/17/06, Gareth <g0...@yahoo.co.uk> wrote:
>
>
>
>
> 46<component id="skillSoughtRow" type="SkillSoughtRow">
> 47      <binding name="skill" value="currentSkill"/>
> 48      <binding name="editable" value="SkillSoughtToEdit lt 0 ||
> currentSkill.index != SkillSoughtToEdit"/>
> 49 <binding
> name="actionsDisabled" value="ognl: addingOrAmendingSought &&
> (currentSkill.index != SkillSoughtToEdit)"/>
> 50</component>
>
> Causes:
>
> org.apache.tapestry.util.xml.DocumentParseException
>
>
>
>                         Unable to read context:/WEB-INF/AmendDetails.page:
> The entity name must immediately follow the '&' in the entity reference.
>
>
>
>
> Any ideas?
>
>
>
>
>
> ___________________________________________________________
> Now you can scan emails quickly with a reading pane. Get the new Yahoo!
> Mail. http://uk.docs.yahoo.com/nowyoucan.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com