blob: 9d42b4974033783d31247c5d44c309cc8b325eb7 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../../../development/news/new_and_noteworthy.xsl"?>
<release name="3.0" root="../../..">
<!--
<component name="component name, such as Java EE Tools">
<item title="item title can go here">
<title>item title can also go here</title>
<description>description of this new feature, preferably with cropped .pngs (800px wide or less) of the UI</description>
</item>
</component>
-->
<component name="Java EE Tools">
<item title="Servlet wizard">
<description>
Several enhancements are introduced to the Servlet
wizard. The most noticeable are:
<ul>
<li>
Initialization parameters are now displayed in a
table view. The user can easily see parameter's
name, value and description.
</li>
<li>
Servlet mappings are now validated. If a user
enters an invalid servlet mapping, then an error
message appears and the wizard cannot be
finished.
</li>
</ul>
<br />
<br />
<img src="javaee/servletWizard.png"
alt="Servlet wizard" />
</description>
</item>
<item title="Servlet Filter wizard">
<description>
A new wizard is introduced for generating Servlet
Filters stubs. Servlet Filters are web artifacts
described in chapter SRV.6 of the Servlet specification.
<br />
<br />
<img src="javaee/filterWizard.png"
alt="Servlet Filter wizard" />
</description>
</item>
<item title="Application Lifecycle Listener wizard">
<description>
A new wizard is introduced for generating Application
Lifecycle Listener stubs. Application Lifecycle
Listeners are web artifacts described in chapter SRV.10
of the Servlet specification.
<br />
<br />
<img src="javaee/listenerWizard.png"
alt="Application Lifecycle Listener wizard" />
</description>
</item>
<item title="New context menu action group">
<description>
There are now three wizards for creating web artifacts:
<ul>
<li>Servlets</li>
<li>Servlet Filters</li>
<li>Application Lifecycle Listeners</li>
</ul>
<br />
They represents the web artifacts, which are based on Java classes.
For easier access these wizards are now available in the context menu of the
<i>Dynamic Web Project</i> as a separate action group.
<br />
<br />
<br />
<img src="javaee/contextMenu.png"
alt="Context menu action group" />
</description>
</item>
<item title="Rearrangement of the toolbar in the Java EE perspective">
<description>
The old toolbar section of five buttons for invoking the
Java EE project wizards is now replaced by two pulldown
buttons:
<ul>
<li>
for invoking the Java EE project wizards (Web, EJB, EAR, etc.)
</li>
<li>
for invoking the Java EE artifact wizards (Servlet, Session Bean, etc.)
</li>
</ul>
<br />
<br />
Old arrangement:
<br />
<img src="javaee/oldToolbar.png"
alt="Pulldown buttons" />
<br />
<br />
New arrangement:
<br />
<img src="javaee/toolbar.png"
alt="Pulldown buttons" />
</description>
</item>
<item title="EAR 5.0 Bundled Libraries Support">
<description>
In accordance with the Java EE 5 specification, a couple of
enhancements are introduced in the EAR 5.0
<i>Java EE Module Dependencies</i>
property page:
<ul>
<li>new column with check-boxes appears in the modules table,
allowing the user to choose if a certain bundled library should be
packed in the EAR's library directory;</li>
<li>
new
<i>Change Library Directory</i>
button appears on the same page to allow the user to change easily
the location of the library directory.
</li>
</ul>
<br />
<br />
<img src="javaee/dependencies.png" alt="J2EE Module Dependencies" />
<br />
<br />
<br />
Appropriate message dialogs pop up in the
<i>Java EE Module Dependencies</i>
property page to warn and allow the user to automatically resolve
conflicts between EAR packing and MANIFEST.MF class path
dependencies.
<br />
<br />
<img src="javaee/conflict.png" alt="Dependencies Conflict" />
</description>
</item>
<item title="Java EE Deployment Descriptor Nodes">
<description>
Deployment Descriptor nodes for Java EE 5 projects are introduced.
This nodes are shown in the project explorer and apply for:
<ul>
<li>EJB 3.0 project</li>
<li>Web 2.5 project</li>
<li>EAR 5.0 project</li>
</ul>
<br />
<br />
<img src="javaee/ddNodes.png" alt="Java EE Deployment Descriptor Nodes" />
<br />
<br />
<br />
According to the Java EE specification artifacts can be described
both in the deployment descriptor and with the use of java
annotations in the source code. Current implementation will show you
a merged view between the artifacts described with java annotations
and those described in the deployment descriptor.
<br />
The result of the following annotated bean:
<br />
<br />
<img src="javaee/ejbCode.png" alt="Annotated bean code" />
<br />
<br />
will be:
<br />
<br />
<img src="javaee/ejbddNode.png" alt="EJB 3.0 Deployment Descriptor Node" />
<br />
<br />
Merging artifacts is also done for Web 2.5 projects. The result from
merging the following Servlet class:
<br />
<br />
<img src="javaee/servletCode.png" alt="Servlet with java annotations" />
<br />
<br />
will result in the following deployment descriptor node:
<br />
<br />
<img src="javaee/webddNode.png" alt="Web 3.0 Deployment Descriptor Node" />
<br />
<br />
</description>
</item>
</component>
<component name="EJB Tools">
<item title="EJB 3.0 Session Bean wizard">
<description>
A new wizard is introduced for generating EJB 3.0 Session
Bean classes and interfaces. The following features can be
highlighted:
<ul>
<li>
Metadata is injected as Java annotations in the
source code instead of described in the ejb-jar.xml
deployment descriptor.
</li>
<li>
Optionally, Local and Remote Business interfaces
can be generated.
</li>
<li>
Optionally, Home and Component interfaces can be
generated for backward compatibility with the
EJB 2.x specification.
</li>
</ul>
<br />
<br />
<img src="javaee/sessionBeanWizard.png"
alt="Session Bean wizard" />
</description>
</item>
<item title="EJB 3.0 Message-Driven Bean wizard">
<description>
A new wizard is introduced for generating EJB 3.0 Message-Driven
Bean classes and interfaces.
<br />
<br />
<img src="javaee/MDBWizard.png"
alt="Message-Driven Bean wizard" />
<br />
<br />
<br />
The metadata is injected as Java annotations in the
source code instead of described in the ejb-jar.xml
deployment descriptor.
<br />
<br />
<img src="javaee/MDBInEditor.png"
alt="Message-Driven Bean wizard" />
</description>
</item>
</component>
</release>