You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2016/12/05 14:59:58 UTC

[jira] [Resolved] (WICKET-6291) PropertyResolver.destroy for specifc getter/setter

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

Sven Meier resolved WICKET-6291.
--------------------------------
    Resolution: Not A Problem
      Assignee: Sven Meier

Please use the indicated solution. 

> PropertyResolver.destroy for specifc getter/setter
> --------------------------------------------------
>
>                 Key: WICKET-6291
>                 URL: https://issues.apache.org/jira/browse/WICKET-6291
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 8.0.0-M2
>            Reporter: Socheat KHAUV
>            Assignee: Sven Meier
>
> I am using wicket for CMS, and wicket pages is updated during runtime for both html file and java file, and java file is compile on the fly, PropertyResolver cache will be out of date when a new java file is compiled and loaded, lucky PropertyResolver.destroy is provided, but it clean all setters and getters, it would be nice to a destroy method just to clean a specific setter or getter for a specific class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)