I'd bet if you dug down through the exception stack, you'd find the
true culprit, somewhere inside getPageMenuNames(). Probably an NPE.
On 8/14/05, Alan Chandler <[EMAIL PROTECTED]> wrote:
> I have hit an error which seems strange, since its the second occurance of the
> same sort of thing in the component template. Any ideas where I should look
> for the source of this error?
>
> The error is
>
> Unable to read OGNL expression '<parsed OGNL expression>' of
> [EMAIL PROTECTED]/$Border]: pageMenuNames
>
>
> This is from my border component with Border.html having the following line
>
> <span jwcid="[EMAIL PROTECTED]" source="ognl:pageMenuNames"
> value="ognl:pageName">
>
> getPageMenuNames is declared in my Border.java file thusly
>
> public String[] getPageMenuNames()
> {
> return getAppPropertySource().getPropertyValue("menu-items").split("
> ",0);
> }
>
>
> What makes this more strange is that earlier in the template I have almost the
> same thing :-
>
> <span jwcid="[EMAIL PROTECTED]" source="ognl:appMenuNames"
> value="ognl:appName">
>
> with getAppMenuNames defined in the Border.java file in almost the same way
> thusly
>
> public String[] getAppMenuNames()
> {
> return _appNames;
> }
>
> --
> Alan Chandler
> http://www.chandlerfamily.org.uk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
