You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/13 15:23:23 UTC

[jira] [Closed] (TAP5-618) Provide more options to extend BeanModelImpl?

     [ https://issues.apache.org/jira/browse/TAP5-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-618.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Provide more options to extend BeanModelImpl?
> ---------------------------------------------
>
>                 Key: TAP5-618
>                 URL: https://issues.apache.org/jira/browse/TAP5-618
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Alfie Kirkpatrick
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> I recently wanted to provide a subclass of this class. It provides some useful code to handle the reordering / including of properties from the bean but I wanted to construct my own implementation of PropertyModel within it. I could override the add(...) methods but the properties field is private so it didn't get me very far. Simply making this protected or providing a getter / setter would do it.
> I ended up having to copy and paste the whole class which is kind of ok. I've just done it for a JCR backend and now want to do it again for a dynamic Hashmap backing class for a dynamic search form.
> I realise this is in the internal package so you might not be happy to open this up...
> Regards, Alfie.



--
This message was sent by Atlassian JIRA
(v6.2#6252)