Re: Tracking down an elusive error during migration to 1.3

2007-09-20 Thread David Leangen
I'm still waiting for the classloader problem to be fixed. There is no point putting this into a quickstart project since this won't reproduce the same classloader issues. We don't yet know if it's a problem with wicket or pax wicket. Since there were no issues with 1.2, it's strange that 1.3 is

Re: Tracking down an elusive error during migration to 1.3

2007-09-13 Thread Eelco Hillenius
Is there a possibility that this issue could be related to a classloading issue that I'm having? You could try to write a test case or quickstart project that shows this. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For

RE: Tracking down an elusive error during migration to 1.3

2007-09-12 Thread David Leangen
Is there a possibility that this issue could be related to a classloading issue that I'm having? On Fri, 2007-09-07 at 07:21 +0900, David Leangen wrote: Johan, Anything I can do to help isolate the problem? I'm using trunk, btw... not the case that David has.. If i write a test

Re: Tracking down an elusive error during migration to 1.3

2007-09-06 Thread Johan Compagner
not the case that David has.. If i write a test case for the ValueMap and i get and put username in it everything works. Ofcourse if i set the debug logging level then i get a debug warning because we do log there when we couldn't find a get or a is property method.. johan On 9/6/07, Igor

Re: Tracking down an elusive error during migration to 1.3

2007-09-05 Thread Matej Knopp
Looks like a bug in property resolver that it doesn't handle maps properly. Johaaan? -Matej On 9/5/07, David Leangen [EMAIL PROTECTED] wrote: Thanks. I managed to find the class of the source of the problem, and it seems to be internal to Wicket.

Re: Tracking down an elusive error during migration to 1.3

2007-09-05 Thread Johan Compagner
thats odd ValueMap is just a hashmap so why it wants to get a username is strange testing.. johan On 9/5/07, Matej Knopp [EMAIL PROTECTED] wrote: Looks like a bug in property resolver that it doesn't handle maps properly. Johaaan? -Matej On 9/5/07, David Leangen [EMAIL PROTECTED] wrote:

Re: Tracking down an elusive error during migration to 1.3

2007-09-05 Thread Johan Compagner
is also something really going wrong?? because 501 is this: try { method = clz.getMethod(is + name, null); } catch (Exception e) { log.debug(Cannot find getter + clz + . + expression, e); }

Re: Tracking down an elusive error during migration to 1.3

2007-09-04 Thread Igor Vaynberg
looks like a propertymodel misbehaving somewhere. set a breakpoint on that exception. when it is thrown you can walk up the stack and see what model/component is causing this. -igor On 9/4/07, David Leangen [EMAIL PROTECTED] wrote: Migrating from 1.2 to 1.3. I've been trying to track down