You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2007/04/19 11:20:15 UTC

[jira] Commented: (WICKET-6) Configuration of app mode isn't customisable

    [ https://issues.apache.org/jira/browse/WICKET-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489976 ] 

Jean-Baptiste Quenot commented on WICKET-6:
-------------------------------------------

Can't you just override init() and call configure() according to your Spring configuration?  That's what we do.  There's always the need to override init() anyway, as DEVELOPMENT or DEPLOYMENT is not sufficient in most cases, often other settings need to be tweaked.

> Configuration of app mode isn't customisable
> --------------------------------------------
>
>                 Key: WICKET-6
>                 URL: https://issues.apache.org/jira/browse/WICKET-6
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.2.2, 1.2.3, 1.3, 2.0
>            Reporter: Alastair Maw
>         Assigned To: Alastair Maw
>            Priority: Minor
>             Fix For: 1.3
>
>
> Everything else in wicket is programatically configurable apart from DEPLOYMENT or DEVELOPMENT app modes. I can't set System properties due to security constraints, and I don't want to have to set things up in web.xml because it's tedious and I already have which deployment ID I'm using configured somewhere else, using Spring.
> I talked to ivaynberg about this on ##wicket, and we reckon Application should have an abstract getConfigurationMode():String function, which is overridden in WebApplication and PortletApplication appropriately, to replicate current functionality. The default implementations should /not/ be final, so you can override them to pull the config from wherever you like.
> If anyone has any objections to changing things to work like this, please shout now, otherwise I will supply a patch for 1.x and trunk shortly.

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