Starting and stopping Tomcat 4.x, 5.x and 6.x
Registering Tomcat process to Eclipse debugger
Creating a WAR project (wizard can update server.xml file)
Adding Java Projects to Tomcat classpath
Setting Tomcat JVM parameters, classpath and bootclasspath
Exporting a Tomcat project to a WAR File
Capability to use a custom Tomcat classloader to load classes in several java projects at the same classloader level than classes in a Tomcat project, see readmeDevLoader.html
This plugin does not contain Tomcat.
(Download and install Tomcat before using this plugin).
This is a design choice not to include Tomcat in the plugin distribution, this way the same plugin version can works with any Tomcat version.
Unzip it in your_Eclipse_Home/plugins
Plugin activation for Eclipse 3.x :
- launch eclipse once using this option : -clean
- if Tomcat icons are not shown in toolbar : select menu 'Window>Customize Perspective...>Commands', and check 'Tomcat' in 'Available command groups'
Set Tomcat version and Tomcat home : Workbench -> Preferences, select Tomcat and set Tomcat version and Tomcat home (Tomcat version and Tomcat home are the only required fields, other settings are there for advanced configuration).
This plugin launches Tomcat using the default JRE
checked in Eclipe preferences window.
To set a JDK as default JRE for Eclipse open the preference window : Window -> Preferences -> Java -> Installed JREs.
This JRE must be a JDK (This is a Tomcat prerequisite).
The plugin sets itself Tomcat classpath and bootclasspath. Use Preferences -> Tomcat ->JVM Settings, only if you need specific settings.
Official documation (french) : http://www.eclipsetotale.com/articles/tomcat/tomcatPluginDocFR.html
Tutorials (english) :
In some case, despite it is correctly unzipped in Eclipse 3 'plugins' directory, the plugin is not loaded : run Eclipse with the -clean option to solve the problem.
ClassNotFound when using DevLoader and launching
Tomcat 5.5.12 and above
Workaround : set context definition mode (Preferences->Tomcat) to 'Context files'.
This problem is due to a change in Tomcat 5.5.12 and above ( http://issues.apache.org/bugzilla/show_bug.cgi?id=37302 ,)
We hope this bug will be fix but it seems that Tomcat developers don't care about it because it happens when a context containing its own loader is defined in server.xml file and since Tomcat 5 defining context in server.xml is not recommended)
ClassNotFoundException on javac/Main when accessing JSP : Tomcat is started with a JRE instead of a JDK.
If you have a problem with the plugin check eclipse log file (<%Your_Workspace_dir%>/.metadata/.log)
For detail know click this link
Posted on: March 10, 2008 If you enjoyed this post then why not add us on Google+? Add us to your Circles