Riccardo has it right - the easiest way to do this is to simply have a resin.xml for each webapp - and then just start resin using the resin.xml that is configured for the app you want to run.
On 01/04/2013 07:31 AM, Rick Mann wrote: > On Jan 4, 2013, at 0:53 , Riccardo Cohen<[email protected]> wrote: > >> then >> you don't have to restart resin each time you want to change the >> application. > I actually deliberately restart resin quite frequently. It doesn't pick up > certain changes just reloading the class (for example, a Spring @Controller > reload won't cause Spring to notice a new handler mapping). Add to that a > persistent leak that causes resin to gobble up memory after a few app > reloads, and it's best (for me) to restart resin frequently. > > Which is, more or less, orthogonal to easily switching configurations. > _______________________________________________ resin-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/resin-interest
