releases/2.0/newandnoteworthy/jee.xml - www.eclipse.org/webtools - Git at Google

 <?xml version="1.0" encoding="utf-8"?>
 <?xml-stylesheet type="text/xsl" href="../../../development/news/new_and_noteworthy.xsl"?>
 <release name="2.0" root="../../..">
 	<greeting>
 		WTP 2.0 features the debut of exciting functionality from the
 		new JavaServer Faces component and improvements in supporting
 		JSP 2.0 and Java EE 5. A webinar for the JavaServer Faces Tools
 		project showcasing some of these features was recorded and is
 		available from
 		<a href="http://www.eclipse.org/community/webinars.php#JSF">
 			here
 		</a>
 		.
 	</greeting>
 	<component name="JSP">
 		<item title="Support for Tag Handlers from Tag files">
 			<description>
 				Custom tags declared by JSP 2.0 tag files are now
 				supported for use by the JSP editor as well as
 				validation and debugging.
 				<br />
 				<br />
 				<img src="jee/tagdir-usage1.png"
 					alt="tagdir attribute in use" />
 				<br />
 				<br />
 				<img src="jee/tagediting.png"
 					alt="JSP editor editing a .tag file" />
 			</description>
 		</item>
 		<item title="Content Assist for Tag Library URIs">
 			<description>
 				Content Assist is now available for the
 				<strong>uri</strong>
 				and
 				<strong>tagdir</strong>
 				attributes of Tag Library Directives.
 				<br />
 				<br />
 				<img src="j2ee/taglib-content-assist.png"
 					alt="URI proposals" />
 				<br />
 				<br />
 				Once the URI is specified, it will also offer any values
 				suggested by the library for the prefix.
 				<br />
 				<br />
 				<img src="j2ee/taglib-content-assist2.png"
 					alt="prefix proposals" />
 			</description>
 		</item>
 		<item title="Tag Library Directive Validation">
 			<description>
 				The JSP Validator will now report if it can not find the
 				library referred to by a Tag Library Directive, as well
 				as any problems it finds regarding the prefix value.
 				<br />
 				<br />
 				<img src="j2ee/taglibValidation.png"
 					alt="sample taglib directive warning" />
 			</description>
 		</item>
 		<item title="Include directive validation">
 			<description>
 				The JSP Syntax Validator now warns when the JSP segment
 				referred to by an include directive can not be found.
 				<br />
 				<br />
 				<img src="jee/include-validation1.png"
 					alt="warning on bad file value" />
 			</description>
 		</item>
 		<item title="New JSP Content validator">
 			<description>
 				There is now a separate validator for JSP content versus
 				just using the validator of the embedded content type
 				within JSP. For example, users are now able to enable
 				HTML Syntax validation in their HTML files while
 				disabling JSP content validation (i.e. HTML content
 				within a JSP file).
 				<br />
 				<br />
 				<img src="jee/jspcontentvalidator.png"
 					alt="The new validator in the Validation preference page" />
 			</description>
 		</item>
 		<item title="Hyperlinking to custom tag declarations">
 			<description>
 				Activating hyperlinks within custom tag names will open
 				the tag library descriptor or tag file that declares the
 				custom tag.
 				<br />
 				<br />
 				<img src="jee/tag-hyperlink1.png"
 					alt="hyperlink showing on a custom tag" />
 			</description>
 		</item>
 	</component>

 	<component name="Java EE Tools">
 		<item title="JavaEE 5 projects are now runnable">
 			<description>
 				Support for deploying JavaEE projects on a
 				JavaEE-compliant server now includes JavaEE 5 . This was
 				tested using Servlet 2.5 projects on Apache Tomcat 6 and
 				Geronimo application servers.
 				<i>
 					For JavaEE 5, some servers may still require
 					deployment descriptors, even though they are
 					optional. By default, they are only generated for
 					Dynamic Web projects. Check your server
 					documentation for details.
 				</i>
 			</description>
 		</item>
 		<!-- important to users?
 			<item title="Java Enterprise Edition 5 Facets">
 			<description>
 			New versions of the EAR, Web, Application Client, and
 			EJB facets have been added. These versions have been
 			created to enable developing applications for the Java
 			Platform, Enterprise Edition 5.
 			<br />
 			<br />
 			<img src="jee/Image2.png"
 			alt="New EAR Application Project Wizard showing new Facet" />
 			</description>
 			</item>
 		-->
 		<item title="Easier publishing of dependencies">
 			<description>
 				Entries on the Java Build Path can now be added to the
 				published structure of J2EE module projects through the
 				<b>J2EE Module Dependencies</b>
 				properties page.
 				<br />
 				<br />
 				First, add the desired library or classpath container to
 				the Java Build Path
 				<br />
 				<img src="jee/AddingUserLibrary.png"
 					alt=" J2EE Module Dependencies page on a web project " />
 				<br />
 				<br />
 				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)
 				<br />
 				<img src="jee/WARJ2EEModuleDependencies.png"
 					alt=" Module Dependencies property page on a web project " />
 				<br />
 				<br />
 				<img src="jee/EARJ2EEModuleDependencies.png"
 					alt=" Module Dependencies property page on an EAR project " />
 				<br />
 				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.
 				<br />
 				<br />
 				Adopters may also make use of corresponding new APIs
 				found in the
 				<i>org.eclipse.jst.j2ee.classpathdep</i>
 				package of the
 				<i>org.eclipse.jst.j2ee</i>
 				plug-in.
 			</description>
 		</item>
 		<item title="More flexible validation ">
 			<description>
 				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. -->
 				<br />
 				<br />
 				<img src="jee/validation-contenttypes.png"
 					alt="new filenames being added to an existing content type" />
 				<br />
 				<br />
 				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.
 			</description>
 		</item>
 	</component>

 	<component name="JavaServer Faces">
 		<item title="Support for JSF 1.2">
 			<description>
 				JSF Tools supports JavaServer Faces 1.1 and 1.2 versions.
 				<br />
 				<br />
 				<img src="j2ee/jsf-versions.png"
 					alt="Support for JSF 1.1 and 1.2" />
 				<br />
 				<br />
 			</description>
 		</item>
 		<item title="Web Page Editor">
 			<description>
 				An enhanced Web Page Editor is now available. Building
 				on the existing JSP editing support, it provides
 				simultaneous synchronized visual and source editing of a
 				Faces JSP in a split pane arrangment, a
 				flyout/detachable palette, enhanced property sheets, a
 				Preview page, and more.
 				<br />
 				<br />
 				<img src="j2ee/jsf-web-page-editor.png"
 					alt="Web Page Editor sample screenshot" />
 				<br />
 				<br />
 				The layout of the panes, as well as whether to show
 				both, is configurable.
 				<br />
 				<br />
 				<img src="j2ee/jsf-layout.png"
 					alt="Web Page Editor sample screenshot" />
 				<br />
 				<br />
 				More planned features and ideas can be found at the
 				editor's
 				<a
 					href="http://wiki.eclipse.org/index.php/Visual_JSF_Page_Designer">
 					wiki page
 				</a>
 				.
 			</description>
 		</item>
 		<item title="Faces Config Editor">
 			<description>
 				The Faces Configuration Editor is a comprehensive
 				multi-page editor to edit the Faces configuration
 				resource file. It includes a graphical editor to
 				visually define the navigational rules.
 				<br />
 				<br />
 				<img src="j2ee/jsf-faces-config-editor.png"
 					alt="Faces Config Editor sample screenshot" />
 			</description>
 		</item>
 		<item title="Improved HTML DataTable tag variable support">
 			<description>
 				EL variables declared using the
 				<em>var</em>
 				attribute on the
 				<strong>h:dataTable</strong>
 				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
 				generic Lists.
 				<br />
 				<br />
 				<img src="jee/DataTableVariableSupport.png"
 					alt="content assist popup" />
 			</description>
 		</item>

 		<item
 			title="JSF Libraries are now regular Classpath Containers">
 			<description>
 				JSF Libraries make use of the
 				<i>easier publishing of dependencies</i>
 				feature introduced in this release. References to JSF
 				Libraries in a project are made using the standard Java
 				Build Path property page and set to be
 				published/exported using the J2EE Module Dependencies
 				property page, and will appear as JDT Libraries in the
 				Project and Package Explorer views.
 				<i>
 					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.
 				</i>
 				Information on this can be found at
 				<a
 					href="http://wiki.eclipse.org/index.php/JSF_Library_Migration">
 					http://wiki.eclipse.org/index.php/JSF_Library_Migration
 				</a>
 				. 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 standard Java Build Path and J2EE
 				Module Dependencies property pages.
 				<br />
 				<br />
 				Creating a JSF Library Reference JSF Libraries as
 				Classpath Containers
 				<br />
 				<img src="jee/Fig1.png"
 					alt="Fig 1. Add Library from Java Build Path" />
 				<br />
 				<br />
 				Add Library from Java Build Path
 				<br />
 				<img src="jee/Fig1.png"
 					alt="Fig. 2 Choose JSF Libraries" />
 				<br />
 				<br />
 				Choose JSF Libraries
 				<br />
 				<img src="jee/Fig3.png"
 					alt="Fig. 3 Select One or More Libraries" />
 				<br />
 				<br />
 				Select One or More Libraries
 				<br />
 				<img src="jee/Fig4.png"
 					alt="Fig. 4 JSF Libraries Added as Classpath Containers to Java Build Path" />
 				<br />
 				<br />
 				JSF Libraries Added as Classpath Containers to Java
 				Build Path
 				<br />
 				<img src="jee/Fig5.png"
 					alt="Fig. 5 Select JSF Libraries for Publish and Export" />
 				<br />
 				Select JSF Libraries for Publish and Export
 			</description>
 		</item>


 		<item title="Custom JSF Servlet Classname">
 			<description>
 				The JSF servlet classname can now be specified during
 				JSF Facet installation.
 				<br />
 				<br />
 				<img src="jee/Fig6.png"
 					alt="Fig. 6 JSF Servlet Classname in JSF Facet Installation Wizard" />
 			</description>
 		</item>

 		<item title="EL Validation Severity Configuration">
 			<description>
 				The severity of problems found during EL validation can
 				now be changed by preferences. We have adapted the UI
 				used by JDT to perform similar severity changes on Java
 				problems.
 				<br />
 				<br />
 				<img src="j2ee/Fig7.png"
 					alt="Fig. 7 JSF EL Validation Preference Page" />
 			</description>
 		</item>

 	</component>
 </release>
	<?xml version="1.0" encoding="utf-8"?>
	<?xml-stylesheet type="text/xsl" href="../../../development/news/new_and_noteworthy.xsl"?>
	<release name="2.0" root="../../..">
	<greeting>
	WTP 2.0 features the debut of exciting functionality from the
	new JavaServer Faces component and improvements in supporting
	JSP 2.0 and Java EE 5. A webinar for the JavaServer Faces Tools
	project showcasing some of these features was recorded and is
	available from
	<a href="http://www.eclipse.org/community/webinars.php#JSF">
	here
	</a>
	.
	</greeting>
	<component name="JSP">
	<item title="Support for Tag Handlers from Tag files">
	<description>
	Custom tags declared by JSP 2.0 tag files are now
	supported for use by the JSP editor as well as
	validation and debugging.
	<br />
	<br />
	<img src="jee/tagdir-usage1.png"
	alt="tagdir attribute in use" />
	<br />
	<br />
	<img src="jee/tagediting.png"
	alt="JSP editor editing a .tag file" />
	</description>
	</item>
	<item title="Content Assist for Tag Library URIs">
	<description>
	Content Assist is now available for the
	<strong>uri</strong>
	and
	<strong>tagdir</strong>
	attributes of Tag Library Directives.
	<br />
	<br />
	<img src="j2ee/taglib-content-assist.png"
	alt="URI proposals" />
	<br />
	<br />
	Once the URI is specified, it will also offer any values
	suggested by the library for the prefix.
	<br />
	<br />
	<img src="j2ee/taglib-content-assist2.png"
	alt="prefix proposals" />
	</description>
	</item>
	<item title="Tag Library Directive Validation">
	<description>
	The JSP Validator will now report if it can not find the
	library referred to by a Tag Library Directive, as well
	as any problems it finds regarding the prefix value.
	<br />
	<br />
	<img src="j2ee/taglibValidation.png"
	alt="sample taglib directive warning" />
	</description>
	</item>
	<item title="Include directive validation">
	<description>
	The JSP Syntax Validator now warns when the JSP segment
	referred to by an include directive can not be found.
	<br />
	<br />
	<img src="jee/include-validation1.png"
	alt="warning on bad file value" />
	</description>
	</item>
	<item title="New JSP Content validator">
	<description>
	There is now a separate validator for JSP content versus
	just using the validator of the embedded content type
	within JSP. For example, users are now able to enable
	HTML Syntax validation in their HTML files while
	disabling JSP content validation (i.e. HTML content
	within a JSP file).
	<br />
	<br />
	<img src="jee/jspcontentvalidator.png"
	alt="The new validator in the Validation preference page" />
	</description>
	</item>
	<item title="Hyperlinking to custom tag declarations">
	<description>
	Activating hyperlinks within custom tag names will open
	the tag library descriptor or tag file that declares the
	custom tag.
	<br />
	<br />
	<img src="jee/tag-hyperlink1.png"
	alt="hyperlink showing on a custom tag" />
	</description>
	</item>
	</component>

	<component name="Java EE Tools">
	<item title="JavaEE 5 projects are now runnable">
	<description>
	Support for deploying JavaEE projects on a
	JavaEE-compliant server now includes JavaEE 5 . This was
	tested using Servlet 2.5 projects on Apache Tomcat 6 and
	Geronimo application servers.
	<i>
	For JavaEE 5, some servers may still require
	deployment descriptors, even though they are
	optional. By default, they are only generated for
	Dynamic Web projects. Check your server
	documentation for details.
	</i>
	</description>
	</item>
	<!-- important to users?
	<item title="Java Enterprise Edition 5 Facets">
	<description>
	New versions of the EAR, Web, Application Client, and
	EJB facets have been added. These versions have been
	created to enable developing applications for the Java
	Platform, Enterprise Edition 5.
	<br />
	<br />
	<img src="jee/Image2.png"
	alt="New EAR Application Project Wizard showing new Facet" />
	</description>
	</item>
	-->
	<item title="Easier publishing of dependencies">
	<description>
	Entries on the Java Build Path can now be added to the
	published structure of J2EE module projects through the
	<b>J2EE Module Dependencies</b>
	properties page.
	<br />
	<br />
	First, add the desired library or classpath container to
	the Java Build Path
	<br />
	<img src="jee/AddingUserLibrary.png"
	alt=" J2EE Module Dependencies page on a web project " />
	<br />
	<br />
	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)
	<br />
	<img src="jee/WARJ2EEModuleDependencies.png"
	alt=" Module Dependencies property page on a web project " />
	<br />
	<br />
	<img src="jee/EARJ2EEModuleDependencies.png"
	alt=" Module Dependencies property page on an EAR project " />
	<br />
	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.
	<br />
	<br />
	Adopters may also make use of corresponding new APIs
	found in the
	<i>org.eclipse.jst.j2ee.classpathdep</i>
	package of the
	<i>org.eclipse.jst.j2ee</i>
	plug-in.
	</description>
	</item>
	<item title="More flexible validation ">
	<description>
	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. -->
	<br />
	<br />
	<img src="jee/validation-contenttypes.png"
	alt="new filenames being added to an existing content type" />
	<br />
	<br />
	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.
	</description>
	</item>
	</component>

	<component name="JavaServer Faces">
	<item title="Support for JSF 1.2">
	<description>
	JSF Tools supports JavaServer Faces 1.1 and 1.2 versions.
	<br />
	<br />
	<img src="j2ee/jsf-versions.png"
	alt="Support for JSF 1.1 and 1.2" />
	<br />
	<br />
	</description>
	</item>
	<item title="Web Page Editor">
	<description>
	An enhanced Web Page Editor is now available. Building
	on the existing JSP editing support, it provides
	simultaneous synchronized visual and source editing of a
	Faces JSP in a split pane arrangment, a
	flyout/detachable palette, enhanced property sheets, a
	Preview page, and more.
	<br />
	<br />
	<img src="j2ee/jsf-web-page-editor.png"
	alt="Web Page Editor sample screenshot" />
	<br />
	<br />
	The layout of the panes, as well as whether to show
	both, is configurable.
	<br />
	<br />
	<img src="j2ee/jsf-layout.png"
	alt="Web Page Editor sample screenshot" />
	<br />
	<br />
	More planned features and ideas can be found at the
	editor's
	<a
	href="http://wiki.eclipse.org/index.php/Visual_JSF_Page_Designer">
	wiki page
	</a>
	.
	</description>
	</item>
	<item title="Faces Config Editor">
	<description>
	The Faces Configuration Editor is a comprehensive
	multi-page editor to edit the Faces configuration
	resource file. It includes a graphical editor to
	visually define the navigational rules.
	<br />
	<br />
	<img src="j2ee/jsf-faces-config-editor.png"
	alt="Faces Config Editor sample screenshot" />
	</description>
	</item>
	<item title="Improved HTML DataTable tag variable support">
	<description>
	EL variables declared using the
	<em>var</em>
	attribute on the
	<strong>h:dataTable</strong>
	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
	generic Lists.
	<br />
	<br />
	<img src="jee/DataTableVariableSupport.png"
	alt="content assist popup" />
	</description>
	</item>

	<item
	title="JSF Libraries are now regular Classpath Containers">
	<description>
	JSF Libraries make use of the
	<i>easier publishing of dependencies</i>
	feature introduced in this release. References to JSF
	Libraries in a project are made using the standard Java
	Build Path property page and set to be
	published/exported using the J2EE Module Dependencies
	property page, and will appear as JDT Libraries in the
	Project and Package Explorer views.
	<i>
	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.
	</i>
	Information on this can be found at
	<a
	href="http://wiki.eclipse.org/index.php/JSF_Library_Migration">
	http://wiki.eclipse.org/index.php/JSF_Library_Migration
	</a>
	. 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 standard Java Build Path and J2EE
	Module Dependencies property pages.
	<br />
	<br />
	Creating a JSF Library Reference JSF Libraries as
	Classpath Containers
	<br />
	<img src="jee/Fig1.png"
	alt="Fig 1. Add Library from Java Build Path" />
	<br />
	<br />
	Add Library from Java Build Path
	<br />
	<img src="jee/Fig1.png"
	alt="Fig. 2 Choose JSF Libraries" />
	<br />
	<br />
	Choose JSF Libraries
	<br />
	<img src="jee/Fig3.png"
	alt="Fig. 3 Select One or More Libraries" />
	<br />
	<br />
	Select One or More Libraries
	<br />
	<img src="jee/Fig4.png"
	alt="Fig. 4 JSF Libraries Added as Classpath Containers to Java Build Path" />
	<br />
	<br />
	JSF Libraries Added as Classpath Containers to Java
	Build Path
	<br />
	<img src="jee/Fig5.png"
	alt="Fig. 5 Select JSF Libraries for Publish and Export" />
	<br />
	Select JSF Libraries for Publish and Export
	</description>
	</item>


	<item title="Custom JSF Servlet Classname">
	<description>
	The JSF servlet classname can now be specified during
	JSF Facet installation.
	<br />
	<br />
	<img src="jee/Fig6.png"
	alt="Fig. 6 JSF Servlet Classname in JSF Facet Installation Wizard" />
	</description>
	</item>

	<item title="EL Validation Severity Configuration">
	<description>
	The severity of problems found during EL validation can
	now be changed by preferences. We have adapted the UI
	used by JDT to perform similar severity changes on Java
	problems.
	<br />
	<br />
	<img src="j2ee/Fig7.png"
	alt="Fig. 7 JSF EL Validation Preference Page" />
	</description>
	</item>

	</component>
	</release>