The fix is really easy, I can just do it myself. What I wanted to ask on the list first is if people agree or not, since this would change the api a little (removing the "isDeployment" parameter from the factory method).
There's no point in adding this to the managed settings, as it is only read once at application startup. Cheers, Dave > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Edward Yakop > Sent: 27 March 2008 16:43 > To: General OPS4J > Subject: Re: Remove deployment configuration from ApplicationFactory? > > > Hi, > > Could u put a jira bug for this. And I will attend it as soon as I can. > > Regards, > Edward Yakop > > On Thu, Mar 27, 2008 at 3:07 PM, David Leangen <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I noticed that when I tried to configure the deployment mode via > > pax-wicket, it doesn't work. > > > > I guess when we updated pax-wicket to support Wicket 1.3.x, this part > > was not done properly. > > > > > > The way this is set in Wicket seems to have changed, and it looks like > > pax-wicket probably doesn't even need to support this anymore. > > > > > > To set the deployment mode in Wicket, you can just set a system > > property: > > > > wicket.configuration={development|deployment} > > > > > > However, this only allows for a global configuration. > > > > > > Can we just use the Wicket way, or do we still want to be able to set > > this on a per-app basis? > > > > I personally think just one global configuration is enough (at > least for > > my needs). > > > > > > Cheers, > > David > > > > > > > > > > _______________________________________________ > > general mailing list > > [email protected] > > http://lists.ops4j.org/mailman/listinfo/general > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
