- This topic has 1 reply, 2 voices, and was last updated 19 years, 7 months ago by
Riyad Kalla.
Viewing 2 posts - 1 through 2 (of 2 total)
-
AuthorPosts
-
Scott AndersonParticipantMyEclipse Project Release Notes
Release 2.1.1 EA2
June 23, 2003Overview
MyEclipse Enterprise Workbench ver. 2.1.1 EA2 is an incremental early access release. The EA2 new features are concentrated in 3 major categories: Web tools, core J2EE project model and deployment, and application server support. Following is a summary of the new features, corrected problems, and known problems that will be addressed in follow on releases.Features and Enhancements
- ID 12 – Hard and soft TAB support for JSP and HTML editors Notes: JSP and HTML editors supports hard and soft tabs
ID 22 – JSP editor background color settings Notes: Supports sophisticated color model for normal or inverted background coloring schemes.
ID 30 – Closing Tag Support Notes: Added closing tag as a completion option
ID 43 – User preference for HTML/JSP upper and lower case tags
ID 46 – Added project properties for web projects Notes: Allows user to set web-root folder and context-root
ID n/a – Native JSP Debugging Notes: Added JSR045 native JSP debugging for Weblogic 7 & 8, and Tomcat 5.
ID n/a – HTML editor supports preview mode Notes: Allows user to quick switch between source and rendered html view
ID 45 – New WebProject wizard allows web-root folderProject Model and Deployment Enhancements
- ID n/a – Support for Web, EJB, and EAR projects Notes: EAR projects are organized as an EAR project with references to 1 or more Web and/or EJB projects.
ID n/a – Creation wizards for Web, EJB, and EAR projects
ID n/a – Exploded deployment of WAR, EJB, and multi-module EAR projects to multiple servers Notes: Exploded archive model allows supporting appservers to dynamically reload modified class and resource files. The MyEclipse model is extremely efficient making optimal use of the Eclipse incremental builder model to systematically keep project codebase synchronized with each deployment.
ID 44 – Deployment/Undeployment wizard and dialog Notes: Dynamically deploy, update, and undeploy to any supporting application server. Smartly knows the capabilities of each server type and only presents options that are valid, e.g. will not present Tomcat as deployment target for EJB or EAR projects.
ID 25 – Project build-path allows user to add MyEclipse libraryset
ID 25a – Added MY_ECLIPSE_LIB classpath variableApplication Server Features
- ID 59 – Tomcat 4 & 5 connector Notes: This connector provides start/stop controls and how swap debugging support with either Tomcat version 4 or 5. The connector also provides native JSP debugging support (JSR045) support for Tomcat 5.
ID 60 – WebSphere 5 connector Notes: This connector provides start/stop controls and how swap debugging support with WebSphere 5.Problems Fixed
- ID 21 – Invocation error when Web Project creation
ID 40 – JSP Editor should redraw all open editors when color pref…
ID 29 – Clarified web-root and context-root terminology
ID 31 – Use forced shutdown on WLS 7 & 8
ID 32 – Detection of WebLogic version sometimes erroneous
ID 35 – WebRoot not persisted and restored correctly
ID 36 – User Reports: Escape characters are not properly handled
ID 44 – // and /* inside a string (quoted sequence) are seen as c…
ID 47 – WebProject wizard presents “Finish” button too soon
ID 53 – JBoss connector ignores Java library path additions
ID 54 – JBoss connector does not function with enspaced paths
ID 55 – Oracle AS connector ignores Java library path additions
ID 56 – Oracle connector does not function with enspaced paths
ID 57 – WebSphere 4 – connector ignores Java library path additions
ID 58 – WebSphere4 – connector does not function with enspaced paths
ID 61 – WebLogic is not honoring java library path additions
ID 62 – Weblogic – connector does not function with enspaced paths
ID 64 – Can’t use “public” as name of a JSP directory
ID 40 – JSP Editor should redraw all open editors when color preferences changesKnown Issues
- ID n/a – Web project context-root not supported Notes:
This requires interacting with server specific configuration files and/or active service. Project name is used as context root.
Riyad KallaMemberMarking unsticky…
-
AuthorPosts
Viewing 2 posts - 1 through 2 (of 2 total)