Craig R. McClanahan wrote:

I'm happy to announce the availability of the first nightly build of the
integration library supporting the use of JavaServer Faces and Struts that has
been updated to support the final release of JavaServer Faces 1.0.  This is not
a formal Apache release; however, it is intended to support experimentation and
trigger bug reports so that we can complete a release in the next couple of
months.  Pick up the files dated 20040308 (or later) from:

http://cvs.apache.org/builds/jakarta-struts/nightly/struts-faces/

Key new features (see the README.txt file for full details):

* Supports the final release of JavaServer Faces 1.0 (previous
 versions supported the beta version).

* Fully worked out examples with and without Tiles.

* You can use value binding expressions ("#{...}") for all attributes
 of the Struts specific components, just like you can with all attributes
 of standard JavaServer Faces components.

* A managed bean named "struts" is available to provide access to
 Struts-internal objects, similar in spirit to the <bean:struts>
 tag in the existing libraries.

* The integration library supports either prefix mapping (/faces/*)
 or extension mapping (*.faces) for the JavaServer Faces servlet.

* You can use the new <s:loadMessages> tag to expose a Struts
 MessageResources object as a Map, so that messages can be looked
 up using value binding expressions, similar to the way that the
 standard <f:loadBundle> tag works with resource bundles.  This allows
 you to use your existing Struts application resources seamlessly with
 non-Struts component tags.

Craig McClanahan


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

.



Great Craig.

You are amazing. We are working with both Struts-Faces and Struts-Chain.

Thanks

BaTien
DBGROUPS

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to