blob: b5642ee70feb6e0e5d7bc7b04e2c799b61ab8789 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../new_and_noteworthy.xsl"?>
<release name="3.0 M6" root="../../..">
<!--
<component name="component name, such as JavaServer Faces 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="JavaServer Faces Tools">
<item title="Support for Apache MyFaces Trinidad">
<description>
Apache MyFaces Trinidad tags are now supported in the Web Page Editor, in source editors, and in the Properties view.
<br/>
<br/>
<img src="jsf/trinidad_in_wpe.png" alt="Trinidad tags in the Web Page Editor"/>
<br/>
<br/>
<img src="jsf/trinidad_codeassist.png" alt="Code-assist for Trinidad tags in source editors"/>
<br/>
<br/>
<img src="jsf/trinidad_properties.png" alt="Advanced property sections for Trinidad tags"/>
</description>
</item>
<item title="Improvements to EL content assist and hover help">
<description>
<div>Thanks to <b>Matthias Fuessel</b> for providing improvements to our EL support:</div>
<div style="margin: 1em;">
<img width="752" height="203" src="jsf/ImprovedContentAssist.png" alt="Improved icons and additional info in content assist"/>
</div>
<div style="padding-top: 1em;padding-bottom: 1em;border-width: 0px; border-style: inset;margin: 1em;">
<img width="741" height="194" src="jsf/ImprovedHoverHelp.png" alt="Improved info in content assist"/>
</div>
</description>
</item>
<item title="New EL framework enhancements">
<description>
<div><p>Thanks to <b>Xiaonan Jiang</b> at IBM for driving new framework requirements and providing prototypes.</p>
<h4>Decorative Variable and Property Resolvers</h4>
<p>To better support the decorative nature of JSF variable and property resolvers, we have added the ability
to register decorative design time resolvers to the default application manager. Decorative resolvers
are called only if the runtime resolver that they are associated with is found in the configuration
of the current web project. For more information see: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=206514#c22">here</a></p></div>
<div style="padding-top: 2em;padding-bottom: 2em;border-width: 0px; border-style: inset;margin: 1em;">
<img width="407" height="194" src="jsf/DecorativeResolver.png" alt="Picture of resolver extension in plugin.xml editor"/>
</div>
<div>
<h4>Enhancements to symbol creation API</h4>
<p>We have refactored several internal symbol creation methods and combined them with contributions
by <b>Matthias Fuessel</b> and <b>Xiaonan Jiang</b> (IBM), to create a new set of extension points
to simplify creation of common JSF symbols. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=211321#c11">here</a>
for more details.</p>
<p>
We have also made the symbol creation methods available on a new factory called <i>JSFSymbolFactory</i>.
</p>
</div>
</description>
</item>
<item title="New EL validation preferences">
<description>
<div>
<p>New validation preferences for EL validation problems allow you
to change the severity of type assignment problems between Error, Warning and Ignore.</p></div>
<div style="padding-top: 2em;padding-bottom: 2em;margin: 1em;">
<img width="666" height="585" src="jsf/NewELValidationPreferences.png" alt="Shows new preference options in the JSF->Validation properties page"/>
</div>
</description>
</item>
</component>
</release>