You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "James Carman (JIRA)" <ji...@apache.org> on 2008/02/20 01:16:45 UTC

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

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

James Carman updated WICKET-1358:
---------------------------------

    Attachment: WICKET-1358.patch

Here's what I have in mind.  So far, I've only implemented ApplicationSettings, DebugSettings, and ExceptionSettings, but you'll get the idea of what I'm wanting to do.  I don't want to the rest if you guys don't like the idea in the first place (it takes a bit of time to do this).   If you like the idea, let me know and I'll finish it up and attach a patch.  Thanks. 

> 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
>         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.