Isis' deploymentType configuration parameter declares EXPLORATION, PROTOTYPING and SERVER as three modes of operation; broadly speaking, "SERVER" corresponds to production.
Wicket, meanwhile, has its configurationType which takes values of "DEVELOPMENT" or "DEPLOYMENT".
Currently the Wicket viewer reads the Wicket "configurationType" init-param, and infers the Isis deploymentType from it.
However, it would also be useful to go the other way, so that running the app through the org.apache.isis.WebServer (ie jetty) would honour the --type (-t) cmd line arg.
For simplicity, suggest:
- Isis SERVER = Wicket DEPLOYMENT mode
- Isis anything else = Wicket DEVELOPMENT mode