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. :)
But if there is no way to do it, I think that putting the whole database stuff into application bundle and then treating it normally would be okay, even if I will have to redeploy the application bundle if I change something in database. Thanks! :) On Tue, Jun 23, 2009 at 12:41 PM, James Carman <jcar...@carmanconsulting.com > wrote: > On Tue, Jun 23, 2009 at 4:05 AM, Daniel Dominik Holúbek > <dankodo...@gmail.com> wrote: > > > > Okay, but I still don't understand the reason of doing this stuff :)I've > > already created the Application bean, and implemented > > ApplicationContextAware. > > Then the setApplicationContext method gets called, so I created > > ApplictionContext variable in that class and set it it that method. > > But if I try to access it in another bundle via Application.get(), it is > > still "null". > > But even if it wasn't, I think that the DAO bean, declared in other > bundle > > (database-bundle) would not be there. > > > > None of us have experience with this environment, so we're trying to > help as best we can. This stuff wasn't designed for this environment. > Why, exactly, do you feel it's necessary to architect your > application this way, if you don't mind me asking? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- -danoh-
