Eclispe tomcat插件

  • K9_606513
    了解作者
  • 289.3KB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-06-14 13:03
    上传日期
Eclispe tomcat插件 ,其实JavaEE版本的额eclpise已经带有插件了,可以方面调式
Eclipse中Tomcat插件.zip
  • Eclipse中Tomcat插件
  • com.sysdeo.eclipse.tomcat_3.2.1
  • DevLoader.zip
    18.1KB
  • icons
  • restart.gif
    184B
  • start.gif
    923B
  • stop.gif
    171B
  • newjprj_wiz.gif
    1000B
  • newjprj_wiz2.gif
    1KB
  • newwar_wiz.gif
    360B
  • releaseNotesV321.txt
    17.3KB
  • license.txt
    1.3KB
  • plugin_ja.properties
    1.5KB
  • plugin_de.properties
    939B
  • plugin.properties
    934B
  • plugin_it.properties
    932B
  • readmeDevLoader.html
    7.1KB
  • tomcatsrc.zip
    123.1KB
  • readme.html
    2.3KB
  • plugin_fr.properties
    1KB
  • img
  • jaune.gif
    215B
  • jaune_transparent.gif
    198B
  • vert.gif
    212B
  • bleu.gif
    214B
  • rouge.gif
    213B
  • logoSysdeo137_53.gif
    2.4KB
  • plugin_bg.properties
    262B
  • tomcat.jar
    131.1KB
  • plugin.xml
    8.7KB
内容介绍
------------------------- Version 3.2.1 ------------ Fixed : - Problem when using HTTPS and various ClassNotFound exceptions. - Tomcat 5 and 6 does not start when context declaration mode is set to 'Server.xml' ------------------------- Version 3.2 ------------ New features : - Tomcat 6.x supported. If you want to use DevLoader with Tomcat 6.x. Rename DevLoader.zip file to DevLoader.jar and put it in <%Tomcat6_Home%>/lib - Tested with Eclipse 3.1, 3.2 and 3.3M6 Fixed : - Problem when using Devloader with Maven2 plugin (Many thanks to Dimitry Voytenko) Explanations : Maven2 Eclipse plugin expands Eclipse's classpath container to include all the artifacts specified in the Maven's POM file. This fix allows resolution inside the classpath containers : On the Tomcat's Project Properties page, containers are now expanded so that a user can select the whole container (in which case the behavior is exactly the same as before) or select a component resolved via the container - Some problems with source code lookup in eclipse debugger (code assist, detail formatter, ...) - VCM Tools not notified when .tomcatplugin file is updated from Tomcat projects properties page. (Thanks to Jonathan Ball). - UTF-8 problems with context file and .tomcatplugin file (Thanks to Vincent CARON) - Fixed in beta2 : Context Declaration Mode mess with version 3.2beta, fixed in 3.2beta2 - Fixed in beta3 : Source code lookup did not work when source code was in a jar file (Many thanks to Martin Goldhahn) - Fixed in final version : - parameter '-config' should not be set when context declaration mode is not 'Server.xml' - working directory for tomcat process was set to eclipse directory instead of catalina_base. - source code lookup improvments. Known problems : - After installation the plugin is not shown in toolbar and there is no Tomcat Preference page Solution : launch eclipse once using this option : -clean - ClassNotFound when using DevLoader and launching Tomcat 5.5.12 and above Workaround : set context definition mode (Preferences->Tomcat) to 'Context files'. Explanations : This problem is due to a change in Tomcat 5.5.12 and above (see http://issues.apache.org/bugzilla/show_bug.cgi?id=37302, A Tomcat fix was introduced in Tomcat 5.5.20, this fix required a change in the plugin. Version 3.2 contains this change so DevLoader works when context is defined in server.xml. This change requires that context definition is updated. ------------------------- Version 3.1 ------------ Nothing new since version 3.1 beta (Excepted some japanese translations, thank you to Yae Suzuki) ------------------------- Version 3.1 beta ------------ New features : - Projects list in source path could be computed automatically (there is a new checkbox in Source path preference page). Computed source path contains all opened Tomcat projects and their prerequisites. Fixed : - Can't open Tomcat projects properties page on Eclipse 3.1M6 - Extra information not added to context definition when switching context declaration mode from 'server.xml' to 'context file'. - DevLoader problems when webapp root directory was set : .#webclasspath file was always created at project root instead of web app root. Thanks to Ben Turner. - Starting and stopping Tomcat was logged in .log file. - Preferences pages were sometimes too large and did not have scrollbars (several buttons and fields were hidden). ------------------------- Version 3.0 ------------ New features : - in main preference page add a way to choose how contexts are declared : - definition in server.xml (previous version allowed only this) - creation of a context file (recommended way with Tomcat 5) - add an 'advanced' preference page to simplify the main preference page. - add a field in Tomcat properties page to set extra information to generated context definitions - Tomcat projects build path are automatically updated when Tomcat version is changed Fixed : - It is no more possible to add Tomcat projects to Tomcat classpath (they won't be listed in preference page) - TOMCAT_HOME was added to project build path (when Tomcat 4 was selected in Tomcat preferences). Before Eclipse 3.0 (final release) this could make Eclipse hangs, see this bug report https://bugs.eclipse.org/bugs/show_bug.cgi?id=64646 Eclipse 3.0 won't build the project. Many thanks to Jerry Lampi - Unable to start Tomcat or to open Tomcat project properties when using DevLoader and allowing circular dependencies for Java projects. - By default, new Tomcat projects were not added to source path - When using Tomcat 5, Eclipse does not stop on breakpoints set in generated java files for JSP. This is fixed only for new Tomcat projects, for existing ones follow those steps : - Edit your Tomcat project Java Build Path - in 'Source' tab, check 'Allow output folders for source folders' - in the list named 'Source folders on build path', select '%Your_project%/work' and 'Output Folder' - select the 'Edit' button, check 'Specific output folder' and enter 'work' in the text field. ------------------------- Version 2.2.1 ------------ Fixed : - starting Tomcat 5.0.15 or 5.0.16 failed Version 2.2 works with Tomcat 5.0.14 (and previous 5.0.x), in Tomcat 5.0.15 a change in Tomcat command line was introduced. Version 2.2.1 runs Tomcat according to this change so Tomcat 5.0.15, 5.0.16 could be started. Trying to run version 5.0.14 will fail if you select 'Tomcat 5.x' in Tomcat preference page, a workaround is to select 'Tomcat 4.1.x' instead of 'Tomcat 5.x' (Tomcat 4.1.x and Tomcat 5.0.14 has the same starting command line) ------------------------- Version 2.2 ------------ New features : - add two buttons on Tomcat JVM preference page : - 'Create a launch Configuration' : add a launch configutation to start Tomcat from menus Run->Run... and Run->Debug... - 'dump configuration to .log' : write all parameters use by the plug-in to launch Tomcat in /.metadata/.log - see below (version 2.2beta and 2.1.1beta) for other new features from version 2.1 Fixed : - Starting Tomcat 4.1.29 failed ------------------------- Version 2.2beta2 ------------ Fixed : - Starting Tomcat failed if Tomcat directory contains whitespaces ------------------------- Version 2.2beta ------------ (Jump to version 2.2 because there are several new features) This version works on Eclipse 2.1.x and Eclipse 3.0M4. New features : - Tomcat project menu has a new option to ask Tomcat to reload the application. This feature uses the Tomcat manager application. This application is enabled by default but for security reasons there no default user. The plug-in add a 'Tomcat Manager App' preference page to set which URL and which tomcat user to use (there is a default value for the url and a button to add a user to tomcat-users.xml). - Add a 'source path' preference page : with previous versions all Java and Tomcat projects were visible by Eclipse Debugger. If a class was defined in two projects Eclipse debugger sometimes show the wrong source code. Using this preference page user can set in which projects Eclipse debuger will look up source code if Tomcat JVM reaches a breakpoint. - when a new project is created, .cvsignore files are created in the following directories : work and WEB-INF/classes - user can activate Tomcat Security Manager in preference page. (for more information about Security Manager see : http://jakarta.apache.org/tomcat/tomcat-4.1-doc/security-manager-howto.html) Fixed : - From version 2.1.1 beta : - In preference page Catalina base field is not saved - On Linux, starting Tomcat failed with a NoClassDefFoundError. - According to catalina.bat, the plugin will now set java.io.tempdir property - Tomcat 5 work dir should not include org.apache.jsp. - User should be warned if Tomcat home is not set in preference page Oth
评论
    相关推荐
    • Eclispe中配置WebServers的详解
      Eclispe中配置WebServers的详解,已经打包好了需要下载的axis2压缩包和需要的jar,通过整理,内含配置帮助说明
    • 在线答题系统(基于Javaweb)
      基于Javaweb的在线考试系统,管理员可以上传试卷,批改试卷,学生可以在线答题 开发环境: 项目运行环境 myeclispe10.7 jdk1.7 tomcat8.0
    • javarebel(java热启jar包及所需文件)
      解压后包含以下3个文件 javarebel.jar ...打开MyeEclispe->Window->Prefrence窗口,找到设置tomcat位置下JDK设置 在java VM参数中增加如下代码(注意下面路径): -noverify-javaagent:d:\javatools\javarebel.jar
    • tomcatPluginV321
      eclipse的一个插件,直接在eclispe环境中集成了tomcat的开发和调试。
    • MyEclispse_Jsp建立Web项目对Tomcat JDK 的环境配置
      运用MyEclisp 开发Web Project 对Tomcat和JDK的系统环境的配置
    • 选课系统(基于Javaweb)
      基于Javaweb的在线选课系统,老师能够上传自己的课程,管理员进行管理分配,学生选课 项目运行环境 myeclispe10.7 jdk1.7 tomcat8.0(附数据库)
    • androidStudent移动端-Tomcat进行学生登录和学生信息管理
      可提供学生进行简单项目的学习研究哦,里面包括eclisp服务器端的源代码,同时也包括androidStudio移动端的代码设计,同学们可以进行相应的修改,如遇不同,随时可以和作者进行联系,对你进行疑惑解答
    • spring核心工厂配置源码
      spring核心工厂配置源码 Eclispe3.2+ Tomcate5.0
    • 基于内嵌apache-tomcat-8.0.24的应用开发
      为什么使用内嵌Tomcat开发? 开发人员无需搭建Tomcat的环境就可以使用内嵌式Tomcat进行开发,减少搭建J2EE容器环境的时间和开发时容器频繁启动所花时间,提高开发的效率. 基于内嵌apache-tomcat-8.0.24的应用开发...
    • GaussDB_100_1.0.1-DATABASE-REDHAT-64bit.tar.gz
      guassdb100在redhat上安装包,单机部署的包,安装步骤请看我的文中介绍,经过大量实验搭建总结出来的文档