blob: ae2c047bc60c4111490749a025c2665d814d3817 [file]
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../../../development/news/new_and_noteworthy.xsl"?>
<release name="2.0" root="../../..">
<component name="Server Tools">
<item title="Create Server With Runtime">
<description>
When you create a runtime you can now create a server at the same time.
If this option is available for the runtime you're creating, just select
the <b>Also create new local server</b> option at the bottom of the dialog.
<br/>
<br/>
<img src="server/tomcat6b.png" alt="Also create new local server"/>
</description>
</item>
<item title="Servers view menu">
<description>
The Servers view context menu has been improved for Eclipse consistency and
new options have been added, along with a Properties dialog.<br/>
<img src="server/serversViewMenu.png" alt="Servers view context menu"/>
</description>
</item>
<item title="Publish Clean">
<description>
The Servers view has a new <b>Clean...</b> option which will perform a
"clean" publish on the server. Much like clean builds, this will remove
any invalid resources from the server before doing a full republish.
<br/>
<br/>
<img src="server/clean.png" alt="Clean publish action on context menu"/>
</description>
</item>
<item title="Publishing performance">
<description>
A new binary format and removal of duplicate information have improved both
the size and performance of storing the publishing history file by 70-90%.
<!-- While it won't make much difference to the average user, t-->This improvement
will decrease workspace size and improve publishing performance for extremely
large applications.
</description>
</item>
<item title="HTTP Server Support">
<description>
Thanks to a donation from ATF, WTP now supports publishing static web
applications to local HTTP servers! You can specify the directory to
publish to, which port the HTTP server uses, and any URL prefix that
your Apache (or other) HTTP server uses.
<br/>
<br/>
<img src="server/httpServer.gif" alt="HTTP server support"/>
</description>
</item>
<item title="Built-in Preview Server">
<description>
Want to compile or run a web application quickly, without waiting to download
or install an external server? The new Preview server allows you to do
exactly that - it supports static and dynamic web apps and allow you to preview
their function on the embedded Jetty server.
</description>
</item>
<item title="Apache Tomcat v6 Support">
<description>
WTP now supports Apache Tomcat v6!
<br/>
<br/>
<img src="server/tomcat6.png" alt="Tomcat 6 support"/>
</description>
</item>
<item title="Manage Tomcat Work Directories">
<description>
Need to clean Tomcat's work directories? Two new menu items in the Servers view
allow you to <b>Clean Tomcat Work Directory</b> or <b>Clean Module Work Directory</b>
without leaving Eclipse.
<br/>
<br/>
<img src="server/cleanworkdir.png" alt="Clean server Work Directory context menu action on the server"/>
<br/>
<br/>
<br/>
<img src="server/cleanmodule.png" alt="Clean Module Work Directory context menu action on the module"/>
</description>
</item>
<item title="Configure Tomcat's Paths">
<description>
There are new user settable paths for the Tomcat server (with server editor UI
still under development).
The <b>Server path</b> allows you to specify a separate instance of the Tomcat server
at a location of your choice.
The <b>Deploy path</b> allows you avoid using the "webapps" directory and the
complications that arise with auto-deployment and default web applications.
<br/>
<br/>
<img src="server/tomcatPaths.png" alt="Configurable paths"/>
</description>
</item>
<item title="Tomcat Publishing Options">
<description>
Two new options which affect publishing are now available in the Server Options
section of the Tomcat server editor. The Tomcat server must be 5.0.x or later
for these options to be enabled. The <b>Serve modules without publishing</b>
option does what it says. Web content will be served directly from the "WebContent"
folder of the Dynamic Web Project. A customized context is used to make the project's
dependencies available in the Web application's classloader.
The <b>Publish module contexts to separate XML files</b> option will publish contexts
using the preferred method of separate XML files under the &quot;conf/Catalina/localhost&quot;
directory, rather than keeping them in the &quot;server.xml&quot; file. A couple of
improvements for this option are noted in Bugs 180931 and 180936.
<br/>
<br/>
<img src="server/tomcatOpts.png" alt="Tomcat publishing options"/>
</description>
</item>
<item title="Debug Last Launched">
<description>
Have you ever used Run on Server, hit a bug in your application, and then hit F11
to test again, only to find out that it tries to start the server again instead?
This long standing and annoying bug has been fixed, so you can now use F11
(or Ctrl-F11 for debug) to rerun just the last html page or EJB.
</description>
</item>
<item title="Servers view initialization">
<description>
The Servers view is no longer blocked from opening until the servers API
is done initializing. The Servers view now appears immediately and shows
the text "Initializing..." until servers have been loaded in the background.
<br/>
<br/>
This change is consistent with JDT's approach to background loading and will
allow perspectives containing the Servers view to appear immediately instead
of being blocked by workspaces with lots of servers or adopter extensions.
<br/>
<br/>
<img src="server/serversViewInit.png" alt="Servers view initialization"/>
</description>
</item>
</component>
</release>