Re: [Resin-interest] Is there an easy way to do this? port

2007-02-02 Thread Daniel López
Jose Quinteiro escribió: Hi, As Jose, I would recommend having different instances for development and deployment. Even though Resin does a good job on separating contexts and detecting changes and restarting just the appropriate web app. You will still affect your deployment applications with

Re: [Resin-interest] Is there an easy way to do this? port

2007-02-02 Thread Scott Ferguson
On Feb 2, 2007, at 12:39 AM, Daniel López wrote: Jose Quinteiro escribió: Hi, As Jose, I would recommend having different instances for development and deployment. Even though Resin does a good job on separating contexts and detecting changes and restarting just the appropriate web app.

[Resin-interest] Is there an easy way to do this? port

2007-02-01 Thread Vinny
Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. I want my production apps running under port 443 docroot : (/web/production/webapps) and my dev apps running under 8080. docroot : (/web/dev/webapps) both production and dev apps will have the same context

Re: [Resin-interest] Is there an easy way to do this? port

2007-02-01 Thread Jose Quinteiro
The way I've accomplished this is by having two different instances of Resin, with different conf files. It's easy to do with 3.0.x, a little harder with 3.1.0. HTH, Jose. Vinny wrote: Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. I want my

Re: [Resin-interest] Is there an easy way to do this? port

2007-02-01 Thread Scott Ferguson
On Feb 1, 2007, at 9:35 AM, Vinny wrote: Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. I want my production apps running under port 443 docroot : (/web/production/webapps) and my dev apps running under 8080. docroot : (/web/dev/webapps) both