![]() ![]() This way, you get the benefit of a packaged distribution, but without the disadvantages of battling with a configuration that is designed to be run as a service. However, if you only want Tomcat installed for development, and you do not want to run it as a service in the background all the time, there is better alternative for this exact purpose there is a package specifically for creating private instances. Using sudo update-rc.d tomcat7 disable to prevent the service from starting is not persistent across updates, so if the tomcat7 package gets updated then it'll start up automatically next time you boot.When you run Tomcat from Eclipse it won't have permissions to write to the places it wants to because the files are not owned by your user.The installation directories and files are not set up in the way that Eclipse expects they are split into two locations.When using Tomcat for development, there are a few problems with installing the tomcat7 package because it is intended to be run as a background service owned by the tomcat7 user: If you install the packaged version, you'll get updates automatically. However, if you want to keep it updated you'll need to manage that yourself. It also allows you to receive security updates automatically.įor Tomcat, it is pretty easy to download the zip distribution, unpack, and point Eclipse at it. ![]() It allows you to configure, start, and stop services in a fairly standard way, and if you run Ubuntu on your production environment it allows you to run consistent versions to minimise compatibility issues. See Cannot start tomcat after installing a private instance.Īll software is different, obviously, but in general packaged software is quicker and easier to install than zipped distributions. I need to update it based on having actually tried using Tomcat 7. NB: This answer was written based on using Tomcat6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |