Same causes, same consequences ...
Since our migration from Tap4.1.1 to 4.1.2 (and 4.1.3) we get the same
error stack as Malin.
I have just parsed our code and found exactly what Malin describes :
@Persist("session")
public abstract void setSearch(IAlert search);
public abstract IAlert getSearch();
public void search() {
...
}
except that search is not an eventlistener but a simple function of our
class.
And the search property is also used by ognl in our html pages.
Stephane.
Malin Ljungh a écrit :
I finally found it!
I would say the issue is not in my code - I consider this a bug (?)
This was the problem:
I have an If component bound to the "showLoginForm" property - thus I have
getter and setters "boolean getShowLoginForm" and
"setShowLoginForm(boolean)".
Also, I have (in the same component) a DirectLink with listener bound to
method "showLoginForm" (in the same component class as the getters and
setters mentioned above).
Seems like it's some kind of name collision here. If I rename the listener
to for example "showLoginFormAction" I get rid of the stack trace.
Should I file the ticket in the OGNL Jesse?
I'm not sure where this belongs...
/Malin
On 10/12/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I meant to say a ticket here: http://jira.opensymphony.com/browse/OGNL
On 10/12/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
It's a bug in the ognl expression compiler, would you mind filing a
ticket with the specifics for me? (expression, object types and
values of the types involved)
It reverts back to normal OGNL reflection when it hits these but still
logs them so that it's hopefully annoying enough that people report
them.
On 10/12/07, Malin Ljungh <[EMAIL PROTECTED]> wrote:
Thanks Ken!
As you say, the issue must be in my code. Sadly the message does not
give me
any clue about what or where.
So - it's in the ognl somewhere - that's a start! I guess I'll just
have to
try blockwise comment out code do trace the error.
'Nice weekend to you all!
Malin
On 10/12/07, Ken nashua <[EMAIL PROTECTED]> wrote:
Dude,
The issue is in your code trust me (now I wish I could say the same
about
my code). Your referencing an OGNL variable with wrong case or
something
like that or semantically it is not constructed properly in order to
follow
thru with the processing.
What is happening is the OGNL expression compiler is attempting to
compile
your ognl expression. Now Thats as flat as it gets.
Why is it failing? Look at my first statement. Examine your
expressions.
Some expressions are blocked from being compiled due to @If
conditions and
so forth so the app will run and look fine but as you begin to open
up these
case blocks, then the fun starts...
Best regards
Ken in nashua
_________________________________________________________________
Boo!Scare away worms, viruses and so much more! Try Windows Live
OneCare!
http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
