[
https://issues.apache.org/jira/browse/WICKET-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970804#action_12970804
]
Hudson commented on WICKET-3253:
--------------------------------
Integrated in Apache Wicket 1.4.x #324 (See
[https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/324/])
- Preventing the attempt to resolve the property class for a null target at
AbstractPropertyModel
- Test asserting that there is no problem in working with an
AbstractPropertyModel targeting an IObjectClassAwareModel not initialized with
an known class.
Issue: WICKET-3253
> NPE with nested property models
> -------------------------------
>
> Key: WICKET-3253
> URL: https://issues.apache.org/jira/browse/WICKET-3253
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.14
> Reporter: Tobias Bergman
> Assignee: Pedro Santos
> Fix For: 1.4.15, 1.5-M4
>
> Attachments: wicket-property-model-bug.zip
>
>
> After updated from 1.4.8 to 1.4.14 I got this bug.
> The problem is with nested property models where the "top" model has a null
> model object that is bound to a TextField. You get a NPE when the page is
> rendered. There is a quick workaround by overriding getOjbectClass() on the
> property model.
> I provide a running example of the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
