If you support code for multiple java application servers, you might eventually encounter a file named:
JBoss uses this file to control the path of the web application, whereas Tomcat generally uses the filename of the WAR itself.
Usually, the contents are pretty sparse, you might consider adding one to your projects should you ever wish to deploy them on JBoss:
NOTE: There are several other attributes that can find their way into this file for JBoss, notably security configuration, like JAAS.
WARNING: Unfortunately, I’ve tried to add a simple
DOCTYPE jboss-web and XML preamble to this, file to make it validate, but the server (JBoss 5.1.x) fails to recognize them.
I’ve done a lot of front-end java coding over my career, one particularly annoying aspect is the wait for a build (compile-deploy) cycle in my local developement servers to view or test a small change. One particularly useful tool that I’ve been using for some time is a FileSync plugin for Eclipse. It is useful as you can “map” folders from your Eclipse project to a path on your local filesystem, as such the individual files are automatically copied to your server installation. I’ve personally used this approache with JBoss, Tomcat and WebSphere, but there is no reason that it should not work for other servers.
When setting up a new JBoss environment, or maintaining an older one you often need to set or reset admin passwords. You can find them here…