Why only one application server per webapp?

Up until now I always worked with a single tomcat server configured into idea: today I wanted to try other servers, so I installed jboss, resin, weblogic and orion (since we're there: what's happening with www.orionserver.com?!?) in order to try my app on those servers using the plugins: I so realized that one has to explicitly assign a particular server to a webapp in the "web module settings", and this has to be changed every time one wants to deploy - test on a different server.

Is this true? Isn't it ugly? I end up having a quantity of different tabs in the "deploy" or "run" dialogs (jboss, orion, tomcat, weblogic, jsr45 server, ...) all of them unusable except the one that has been configured in the webapp!

3 comments
Comment actions Permalink

Problem is that each app server can have additional (proprietary)
deployment descriptors which have to be deployed together with the
webapp. E.g. for JBoss there's an additional jboss-web.xml deployment
descriptor containing JBoss-specific deployment information. Therefore
it isn't possible to just switch app server at deploy time.

Davide Baroncelli wrote:

Up until now I always worked with a single tomcat server configured into idea: today I wanted to try other servers, so I installed jboss, resin, weblogic and orion (since we're there: what's happening with www.orionserver.com?!?) in order to try my app on those servers using the plugins: I so realized that one has to explicitly assign a particular server to a webapp in the "web module settings", and this has to be changed every time one wants to deploy - test on a different server.

Is this true? Isn't it ugly? I end up having a quantity of different tabs in the "deploy" or "run" dialogs (jboss, orion, tomcat, weblogic, jsr45 server, ...) all of them unusable except the one that has been configured in the webapp!

0
Comment actions Permalink

Can't this be managed with a "many-to-many" setting? ;)

0
Comment actions Permalink

Sure it is. I've already proposed this:

1- Setup an app server
2- Set up a web app run config
3- In the webapp run config specify the location of the app server's
descriptors and deployment location.
4- Add those descriptors to be deployed on run along with the compile of the
rest of the module.
5- If a module is running multiple app servers, show all descriptors in the
j2ee view and put a special mark on the active one.
6- If someone switches app servers, simply remove all other app server
deployment descriptors for the current module you're running, and redeploy
the new app server's module.

This would mean a run config per app server, per module.
This would mean that if you have multiple modules you want to run at the
same time, you setup a run config for the app server you want to run it on.

R


On 8/20/04 5:52 AM, in article cg4hln$e82$1@is.intellij.net, "Martin Fuhrer"
<mf@fuhrer.com> wrote:

Problem is that each app server can have additional (proprietary)
deployment descriptors which have to be deployed together with the
webapp. E.g. for JBoss there's an additional jboss-web.xml deployment
descriptor containing JBoss-specific deployment information. Therefore
it isn't possible to just switch app server at deploy time.

Davide Baroncelli wrote:

>> Up until now I always worked with a single tomcat server configured into
>> idea: today I wanted to try other servers, so I installed jboss, resin,
>> weblogic and orion (since we're there: what's happening with
>> www.orionserver.com?!?) in order to try my app on those servers using the
>> plugins: I so realized that one has to explicitly assign a particular server
>> to a webapp in the "web module settings", and this has to be changed every
>> time one wants to deploy - test on a different server.
>>
>> Is this true? Isn't it ugly? I end up having a quantity of different tabs in
>> the "deploy" or "run" dialogs (jboss, orion, tomcat, weblogic, jsr45 server,
>> ...) all of them unusable except the one that has been configured in the
>> webapp!

0

Please sign in to leave a comment.