> Databases have this cool feature called 'access control' ;) Its fairly > trivial to set up the db to take connections from both apps and share > the live data.
Yes but if we assume that the applications are separate, i.e., they cannot be merged. If they can be merged it turns into developing a single application. Whole another ballpark, eh. > But every app and environment is different and this may not be > possible, I just proposed this as its a method that people miss > oftentimes. You are right. The right answer is to forget about the 'constraint' that you are running two applications. If you are coding application A and application B just make an application C that is modular. Especially if both are wicket. We have run into the iframe situation when the other application is for example JSF and there is no money to rewrite it completely. Furthermore, we have tweaked Wicket application views into CMS systems using iframe... .. but when you have all the code in wicket .. don't go there, just refactor and make a modular wicket app on a "single server" ;) ** Martin > > John- > > On Thu, Sep 10, 2009 at 11:37 AM, Martin Makundi > <martin.maku...@koodaripalvelut.com> wrote: >> Well.. that doesn't help if the other app is on other server and other >> db and live data should be viewed from the other app.. in that sad >> case you do need iframe. >> >> ** >> Martin >> >> 2009/9/10 John Armstrong <siber...@siberian.org>: >>> My vote would be to create a common jar package that contains the >>> relevant panels along with their associated business logic, DAO/ORM >>> etc. >>> >>> Then you can use that jar package in both of your apps seamlessly >>> assuming there are not more complex interactions going on. We use this >>> paradigm on our apps and it works very nicely. >>> >>> John- >>> >>> On Thu, Sep 10, 2009 at 12 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
