Well the situation is that we have a 'set' of cooperating applications. For
development, new developers need to check out several projects from our SVN repository and
deploy these to local instances of Tomcat and Jboss.
I'm trying to make this process as painless a possible. The goal is that they can just
do the following:
1. Download and unzip Tomcat
2. Download and unzip Jboss
3. Checkout project X and Y
4. Deploy project X to Tomcat, deploy project Y to Jboss using MyEclipse.
5. Start the servers and start testing
Although seemingly a very small step, explaining to junior developers that they must
change something in [jboss install dir]/.../server.xml proves to be quite hard in
practice. They always do something wrong. Either they can't locate the file, or they
change the wrong port (e.g. set the AJP connector to 8081 instead of the HTTP connector)
or they change something in Tomcat instead of Jboss, etc.
A workaround would be to provide a pre-configured Jboss (already set to port 8081), but in
the past this provided to be problematic too. New developers start to download the latest
version anyway and run into problems since it starts up at the default port.
Providing instructions to add a setting to the MyEclipse server connector is a lot easier
than explaining what they have to change in which file.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176819#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...