You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Makundi (JIRA)" <ji...@apache.org> on 2008/08/25 18:49:44 UTC

[jira] Created: (WICKET-1802) Propertyresolver could be more informative

Propertyresolver could be more informative
------------------------------------------

                 Key: WICKET-1802
                 URL: https://issues.apache.org/jira/browse/WICKET-1802
             Project: Wicket
          Issue Type: Improvement
          Components: wicket
    Affects Versions: 1.4-M3
            Reporter: Martin Makundi


WicketMessage: no set method defined for value: true on object: ...
     at org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1107)

In case there is a getter method defined, it would significantly help debugging to display the get method name in the exception.

I suggest fixing the problem with:

- 					" on object: " + object);
+                                      " on object: " + object + " while respective getMethod being " + getMethod.getName());


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-1802) Propertyresolver could be more informative

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg updated WICKET-1802:
----------------------------------

    Fix Version/s:     (was: 1.4-RC1)
                       (was: 1.3.5)

> Propertyresolver could be more informative
> ------------------------------------------
>
>                 Key: WICKET-1802
>                 URL: https://issues.apache.org/jira/browse/WICKET-1802
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4-M3
>            Reporter: Martin Makundi
>            Assignee: Johan Compagner
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> WicketMessage: no set method defined for value: true on object: ...
>      at org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1107)
> In case there is a getter method defined, it would significantly help debugging to display the get method name in the exception.
> I suggest fixing the problem with:
> - 					" on object: " + object);
> +                                      " on object: " + object + " while respective getMethod being " + getMethod.getName());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (WICKET-1802) Propertyresolver could be more informative

Posted by "Johan Compagner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Compagner closed WICKET-1802.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4-M4
                   1.3.5
         Assignee: Johan Compagner

applied to 1.3 and 1.4

> Propertyresolver could be more informative
> ------------------------------------------
>
>                 Key: WICKET-1802
>                 URL: https://issues.apache.org/jira/browse/WICKET-1802
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4-M3
>            Reporter: Martin Makundi
>            Assignee: Johan Compagner
>             Fix For: 1.3.5, 1.4-M4
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> WicketMessage: no set method defined for value: true on object: ...
>      at org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1107)
> In case there is a getter method defined, it would significantly help debugging to display the get method name in the exception.
> I suggest fixing the problem with:
> - 					" on object: " + object);
> +                                      " on object: " + object + " while respective getMethod being " + getMethod.getName());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (WICKET-1802) Propertyresolver could be more informative

Posted by "Martin Makundi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Makundi reopened WICKET-1802:
------------------------------------


Hi!

I still get this kind of 'blind' exception not displaying the 'expression' that is related to the cause:

2009-03-02 13:22:28,481 12495061 [btpool0-106] ERROR RequestCycle  - Can't convert null value to a primitive class: boolean for setting it on wicket.quickstart.models.ReportingRangeModel@5d637a9e
org.apache.wicket.util.convert.ConversionException: Can't convert null value to a primitive class: boolean for setting it on wicket.quickstart.models.ReportingRangeModel@5d637a9e
       at org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1090)
       at org.apache.wicket.util.lang.PropertyResolver$ObjectAndGetSetter.setValue(PropertyResolver.java:582)
       at org.apache.wicket.util.lang.PropertyResolver.setValue(PropertyResolver.java:136)
       at org.apache.wicket.model.AbstractPropertyModel.setObject(AbstractPropertyModel.java:169)
       at org.apache.wicket.Component.setDefaultModelObject(Component.java:2947)
       at org.apache.wicket.markup.html.form.FormComponent.updateModel(FormComponent.java:1149)
       at org.apache.wicket.markup.html.form.Form$FormModelUpdateVisitor.component(Form.java:223)
       at org.apache.wicket.markup.html.form.FormComponent.visitComponentsPostOrderHelper(FormComponent.java:495)
       at org.apache.wicket.markup.html.form.FormComponent.visitComponentsPostOrderHelper(FormComponent.java:474)
       at org.apache.wicket.markup.html.form.FormComponent.visitComponentsPostOrder(FormComponent.java:451)
       at org.apache.wicket.markup.html.form.Form.internalUpdateFormComponentModels(Form.java:1947)
       at org.apache.wicket.markup.html.form.Form.access$300(Form.java:139)
       at org.apache.wicket.markup.html.form.Form$19.component(Form.java:1932)
       at org.apache.wicket.markup.html.form.Form$19.component(Form.java:1928)
       at org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:859)
       at org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:874)
       at org.apache.wicket.markup.html.form.Form.updateNestedFormComponentModels(Form.java:1926)
       at org.apache.wicket.markup.html.form.Form.updateFormComponentModels(Form.java:1916)
       at org.apache.wicket.markup.html.form.Form.process(Form.java:957)
       at org.apache.wicket.markup.html.form.Form.process(Form.java:905)
       at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:873)
       at org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:132)

It should say which expression was attempted.

> Propertyresolver could be more informative
> ------------------------------------------
>
>                 Key: WICKET-1802
>                 URL: https://issues.apache.org/jira/browse/WICKET-1802
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4-M3
>            Reporter: Martin Makundi
>            Assignee: Johan Compagner
>             Fix For: 1.3.5, 1.4-RC1
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> WicketMessage: no set method defined for value: true on object: ...
>      at org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1107)
> In case there is a getter method defined, it would significantly help debugging to display the get method name in the exception.
> I suggest fixing the problem with:
> - 					" on object: " + object);
> +                                      " on object: " + object + " while respective getMethod being " + getMethod.getName());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.