Re: Tracking down an elusive error during migration to 1.3
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 suddenly broken. I can think of only two possibilities: wicket 1.2 didn't use classloaders correctly, and pax wicket compensated for this. So, when the classloader issues were fixed in 1.3, pax wicket no longer works. Or, Classloaders in 1.2 were working just fine, but were broken in the 1.3 branch. I have too many other things to do right now, and the pax wicket developer is always being put on other projects, so hasn't had time to look into this, either. Once we get the classloader problem fixed, I'll get back to this. I still have a strong suspicion that the two are related. If it's not, then I guess it would be worthwhile to create a quickstart. Thanks for checking in! On Thu, 2007-09-13 at 10:14 -0700, Eelco Hillenius wrote: 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 additional commands, e-mail: [EMAIL PROTECTED]
Re: Tracking down an elusive error during migration to 1.3
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 additional commands, e-mail: [EMAIL PROTECTED]
RE: Tracking down an elusive error during migration to 1.3
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 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.. I managed to find the class of the source of the problem, and it seems to be internal to Wicket. org.apache.wicket.authentication.panel.SignInPanel The form in this class (in wicket-auth-roles) uses this: /** El-cheapo model for form. */ private final ValueMap properties = new ValueMap(); And declares the property like this: add(username = new TextField(username, new PropertyModel(properties, username))); I'm guessing that the Exception is due to either some kind of change in ValueMap, or a change in the property resolver... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tracking down an elusive error during migration to 1.3
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 Vaynberg [EMAIL PROTECTED] wrote:
you wrote it! :)
-igor
On 9/5/07, Johan Compagner [EMAIL PROTECTED] wrote:
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);
}
we try to TEST if we can find it, and then do a debug log if we still
can't
find it
after that we will see that it is a map and fallback on that.
johan
On 9/5/07, David Leangen [EMAIL PROTECTED] wrote:
Migrating from 1.2 to 1.3.
I've been trying to track down the cause of the following error.
Since this is using reflection, I'm not getting any useful line
numbers
or direct information on the cause.
If anybody can shed some light on this for me, I'd really appreciate
it!
All I know is that it happens at render time when visiting one of the
components, but it's difficult to find the exact component.
java.lang.NoSuchMethodException:
org.apache.wicket.util.value.ValueMap.isUsername()
at java.lang.Class.getMethod(Class.java:1581)
at
org.apache.wicket.util.lang.PropertyResolver.findGetter(
PropertyResolver.java:501)
at
org.apache.wicket.util.lang.PropertyResolver.getGetAndSetter(
PropertyResolver.java:317)
...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tracking down an elusive error during migration to 1.3
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. org.apache.wicket.authentication.panel.SignInPanel The form in this class (in wicket-auth-roles) uses this: /** El-cheapo model for form. */ private final ValueMap properties = new ValueMap(); And declares the property like this: add(username = new TextField(username, new PropertyModel(properties, username))); I'm guessing that the Exception is due to either some kind of change in ValueMap, or a change in the property resolver... On Tue, 2007-09-04 at 21:28 -0700, Igor Vaynberg wrote: 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 the cause of the following error. Since this is using reflection, I'm not getting any useful line numbers or direct information on the cause. If anybody can shed some light on this for me, I'd really appreciate it! All I know is that it happens at render time when visiting one of the components, but it's difficult to find the exact component. java.lang.NoSuchMethodException: org.apache.wicket.util.value.ValueMap.isUsername() at java.lang.Class.getMethod(Class.java:1581) at org.apache.wicket.util.lang.PropertyResolver.findGetter (PropertyResolver.java:501) at org.apache.wicket.util.lang.PropertyResolver.getGetAndSetter(PropertyResolver.java:317) ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tracking down an elusive error during migration to 1.3
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: Thanks. I managed to find the class of the source of the problem, and it seems to be internal to Wicket. org.apache.wicket.authentication.panel.SignInPanel The form in this class (in wicket-auth-roles) uses this: /** El-cheapo model for form. */ private final ValueMap properties = new ValueMap(); And declares the property like this: add(username = new TextField(username, new PropertyModel(properties, username))); I'm guessing that the Exception is due to either some kind of change in ValueMap, or a change in the property resolver... On Tue, 2007-09-04 at 21:28 -0700, Igor Vaynberg wrote: 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 the cause of the following error. Since this is using reflection, I'm not getting any useful line numbers or direct information on the cause. If anybody can shed some light on this for me, I'd really appreciate it! All I know is that it happens at render time when visiting one of the components, but it's difficult to find the exact component. java.lang.NoSuchMethodException: org.apache.wicket.util.value.ValueMap.isUsername() at java.lang.Class.getMethod(Class.java:1581) at org.apache.wicket.util.lang.PropertyResolver.findGetter (PropertyResolver.java:501) at org.apache.wicket.util.lang.PropertyResolver.getGetAndSetter( PropertyResolver.java:317) ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tracking down an elusive error during migration to 1.3
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);
}
we try to TEST if we can find it, and then do a debug log if we still can't
find it
after that we will see that it is a map and fallback on that.
johan
On 9/5/07, David Leangen [EMAIL PROTECTED] wrote:
Migrating from 1.2 to 1.3.
I've been trying to track down the cause of the following error.
Since this is using reflection, I'm not getting any useful line numbers
or direct information on the cause.
If anybody can shed some light on this for me, I'd really appreciate it!
All I know is that it happens at render time when visiting one of the
components, but it's difficult to find the exact component.
java.lang.NoSuchMethodException:
org.apache.wicket.util.value.ValueMap.isUsername()
at java.lang.Class.getMethod(Class.java:1581)
at
org.apache.wicket.util.lang.PropertyResolver.findGetter(
PropertyResolver.java:501)
at
org.apache.wicket.util.lang.PropertyResolver.getGetAndSetter(
PropertyResolver.java:317)
...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tracking down an elusive error during migration to 1.3
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 the cause of the following error. Since this is using reflection, I'm not getting any useful line numbers or direct information on the cause. If anybody can shed some light on this for me, I'd really appreciate it! All I know is that it happens at render time when visiting one of the components, but it's difficult to find the exact component. java.lang.NoSuchMethodException: org.apache.wicket.util.value.ValueMap.isUsername() at java.lang.Class.getMethod(Class.java:1581) at org.apache.wicket.util.lang.PropertyResolver.findGetter( PropertyResolver.java:501) at org.apache.wicket.util.lang.PropertyResolver.getGetAndSetter( PropertyResolver.java:317) ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
