How many modules do you have? Do you really need to be able to do this with your live production server? I'm just trying to get an idea behind the decision behind going with this sort of an architecture. Perhaps we can offer up an alternative that would work with the existing Wicket stuff so that we can avoid some headaches for you. :)
On Tue, Jun 23, 2009 at 11:21 AM, Daniel Dominik Holúbek < dankodo...@gmail.com> wrote: > Yes, that's the way it's meant to work :) > > On Tue, Jun 23, 2009 at 3:25 PM, James Carman > <jcar...@carmanconsulting.com>wrote: > > > On Tue, Jun 23, 2009 at 8:26 AM, Daniel Dominik Holúbek > > <dankodo...@gmail.com> wrote: > > > > > > I appreciate your help, of course :)You know, I'm trying to create a > web > > app > > > consisting of independent modules. Then if I change something in one > > module, > > > I don't have to redeploy whole application. > > > This can be achieved of course, the only problem is this thing we are > > > currently speaking of. :) > > > > So, you are going to redeploy the individual modules "live", while the > > application is running, in production? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > -- > -danoh- >
