[WICKET-6] Configuration of app mode isn't customisable

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0 branch (discontinued), 1.2.2, 1.2.3, 1.3.0-beta1
• Fix Version/s: 1.3.0-beta2
• Component/s: wicket
• Assignee: Alastair Maw
• Reporter: Alastair Maw
• Created: 16/Oct/06 19:39
• Updated: 01/Jun/07 17:38
• Resolved: 01/Jun/07 17:38

Description

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.