Rick,
I've been using resin's import ability with 3.0, 3.1 and now 4.0. I had some
issues in 4.0 that required tweaking my namespaces on the imported xml file so
below is an example of my resin.xml and app.xml that I am now using in 4.0.32.
If you are using 3, you might have to change the locat
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 wrote:
>
>> then
On Jan 4, 2013, at 0:53 , Riccardo Cohen 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
re
I personnaly have multiple resin.xml, and launch resin on the one I want
to see. The only difference in the resin.xml is some path and database
access. I use this because my application is twice on my mac : one for
development, and one copy of the production. They have different
directories and
