I had a quick look at the code to see if there was
a simple way to resolve:
http://issues.apache.org/jira/browse/TRINIDAD-708
... and, ouch, not really. The problem's not so much
on the XMLMenuModel side of things, but the
MenuContentHandlerImpl and MenuNode code,
where we have:
- A
That was what I thought too. When I saw the code, my first reaction was uh-oh.
Perhaps the key can be changed to be based on the source instead of a
request-global key?
On 9/13/07, Adam Winer [EMAIL PROTECTED] wrote:
I had a quick look at the code to see if there was
a simple way to resolve:
On 9/13/07, Andrew Robinson [EMAIL PROTECTED] wrote:
That was what I thought too. When I saw the code, my first reaction was uh-oh.
Perhaps the key can be changed to be based on the source instead of a
request-global key?
Easy enough from the XMLMenuModel side - but how well does that
work
I have 2 controls backed by an XmlMenuModel, a main menu and a help
context menu. When I only had one menu, my code was working. When I
introduced the 2nd model, I started getting this exception:
java.lang.NullPointerException
at
I changed the managed-bean-scope to request for both, seeing that in
the developer guide, but it doesn't affect this code.
Is there some odd requirement that there can only be one XmlMenuModel
per application?
-Andrew
On 9/12/07, Andrew Robinson [EMAIL PROTECTED] wrote:
I have 2 controls
On 9/12/07, Andrew Robinson [EMAIL PROTECTED] wrote:
I changed the managed-bean-scope to request for both, seeing that in
the developer guide, but it doesn't affect this code.
Is there some odd requirement that there can only be one XmlMenuModel
per application?
There definitely shouldn't be
6 matches
Mail list logo
