You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/11/20 19:39:13 UTC

[jira] Commented: (WICKET-1358) Make Application Class More Bean-ish

    [ https://issues.apache.org/jira/browse/WICKET-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934164#action_12934164 ] 

Hudson commented on WICKET-1358:
--------------------------------

Integrated in Apache Wicket 1.5.x #535 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/535/])
    fixed WICKET-1358 Make Application Class More Bean-ish
Issue: WICKET-1358


> Make Application Class More Bean-ish
> ------------------------------------
>
>                 Key: WICKET-1358
>                 URL: https://issues.apache.org/jira/browse/WICKET-1358
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.1
>            Reporter: James Carman
>            Assignee: Juergen Donnerstag
>             Fix For: 1.5-M4
>
>         Attachments: WICKET-1358.patch
>
>
> The Application class has getters for properties like applicationSettings and securitySettings.  Couldn't we make those properties writable also?  I realize that the internal implementation might have to change a bit.  Currently, the Settings class implements all of those interfaces and it uses a single instance of Settings by default.  The reason that I want this is so that I can set up my Application object in Spring and access it via wicket-spring.  The current implementation of Application doesn't facilitate the "set up" part very well.

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