Entries on the Java Build Path can now be added to the
published structure of J2EE module projects through the
J2EE Module Dependencies
First, add the desired library or classpath container to
the Java Build Path
Then select the library so it will be published in the
module (Web Library dependencies will be published to
/WEB-INF/lib, J2EE Module dependencies will be published
to the EAR root)
The resolved contributions from entries published to the
EAR root will be displayed in the J2EE Module
Dependencies page for the EAR project as grayed items.
Adopters may also make use of corresponding new APIs
found in the
package of the
More flexible validation
The validation framework now supports Content Types, so
additional filename added to content types on the
Content Type preference page will also be validated by
their respective validators. The J2EE validators already
leverage the new content type support with other
validators expected to transition by the next milestone.
For adopters, new APIs have been added to the validation
framework supporting turning on and off individual
validators, translating into increased convenience,
utility, and performance.
Improved HTML DataTable tag variable support
EL variables declared using the "var" attribute on the
tag are now recognized by the JSF EL framework. The
amount of additional support varies depending on the
"value" attribute used to back the variable, the most
complete being offered for scalar or array objects with
generics planned for the future.
JSF Libraries are now regular Classpath Containers
JSF Libraries now make use of the
easier publishing of dependencies
feature also introduced in this milestone, so now
references to JSF Libraries in a project are made using
the Java Build Path and made published/exported using
the J2EE Module Dependencies, and will appear as JDT
Libraries in the project explorer.
An upgrade of the JSF Library Registry will
automatically occur when an older workspace is
opened. The actual references, however, will require
a manual upgrade.
Information on this can be found at
. JSF Library references are still being created at JSF
Facet installation time, but if you need to add, modify,
or remove references after project creation, you will
now be using the Java Build Path and J2EE Module
Dependencies property pages.
Creating a JSF Library Reference JSF Libraries as
Add Library from Java Build Path
Choose JSF Libraries
Select One or More Libraries
JSF Libraries Added as Classpath Containers to Java
Select JSF Libraries for Publish and Export
Custom JSF Servlet Classname
The JSF servlet classname can now be specified during
JSF Facet installation.
Support for Tag Handlers from Tag files
Custom tags declared by JSP 2.0 tag files are now
supported for use by the JSP editor as well as
debugging. Support for editing and validating tag files
will be added in a future version.
Hyperlinking to custom tag declarations
Activating Hyperlinks within custom tag names will open
the tag library descriptor or tag file that declares the
Include directive validation
The JSP Syntax Validator now warns when the JSP fragment
referred to by an include directive can not be found.