AngularFaces 2.1.12 (December 11, 2016)

AngularFaces 2.1.11 (February 08, 2016)

Improved support for BootsFaces. Now both the old and the new version of BootsFaces are supported.

AngularFaces 2.1.10 (January 16, 2016)

Improved support for BootsFaces. The old BootsFaces detection mechanism had to be extended because of the new
package layout of BootsFaces.

AngularFaces 2.1.9 (September 24, 2015)

Support for the @NotEmpty annotation of Hibernate

PuiLabel and PuiMessage now access the field they refer to, even when they are rendered in a data table

Add an option to disable translation globally

Add an option to disable the automatic addition of labels and messages globally

AngularFaces 2.1.8 (July 02, 2015)

Updated to AngularJS 1.3.16 and jQuery 1.11.3

repaired ng-sync

AngularFaces 2.1.7 (June 28, 2015)

AngularFaces now copes with EL expressions in every attribute. In particular, AngularJS controllers now can be selected
by a JSF bean (i.e. <div ng-controller="# {mainBean.currentAngularJSController}" />).

Now it's possible to suppress the automatic loading of the main.js file (see issue 51. )

Client-side messages used to ignore the severity level, which led to a weird appearance in PrimeFaces applications. This error has been fixed.

Now you can use multiple AngularJS controllers on a single JSF view. For instance, a modal dialog can have its own AngularJS controller.

There's are several new options to suppress the automatic loading of AngularJS, jQuery, jQuery-UI and angular-messages.js. This is useful
if you've minified and merge the individual files, so that AngularFaces doesn't detect that the base libraries already have been loaded. Also
see issue 45.

Starting with AngularFaces 2.1.7, every AngularFaces context parameter in the web.xml file is prefixed by "AngularFaces." In the case of
the context parameter "clientSideMessages" which has been introduced in AngularFaces 2.1.5, both the old and the new
parameter are valid.

AngularFaces 2.1.6 (June 16, 2015)

AF 2.1.6 catches an exception that's thrown by the Glassfish application server when AngularFaces tries to
translate an attribute that doesn't exist.

AngularFaces 2.1.5 (May 30, 2015)

AF 2.1.5 adds the context parameter clientSideMessages. You can add it to the web.xml file to suppress
the automatic replacement of h:messages by a client-side puimessages component.

AngularFaces 2.1.4 (March 25, 2015)

AF 2.1.4 is the smallest possible update: it consists of a single bit. Unfortunately, it's an important bit.
AngularFaces 2.1.4 comes pre-packaged with jQueryUI 1.11.3. Previous versions added a script include of the
non-existing version 1.11.2. Now jQueryUI is included correctly.

AngularFaces 2.1.3 (March 14, 2015)

AF 2.1.3 fixes the bug that forced developers to use prependId="false". The bugfix relies on
MutationObserver, which is not compatible to older Internet Explorers. According to
"Can I use?", only IE 11+ is supported.
Note that AngularJS itself doesn't support the separator character JSF uses in ids. Most features will work fine,
but some features such as setting a watch or ngMessages fail.

Added <ac:include /> which is a language-aware version of <ui:include />.
It checks which languages the user prefers (according to their browser settings) and tries to add the language
code to the filename. If no such file is found, <ac:include /> defaults to the standard
behaviour of <ui:include />.

AngularJS has been updated to v1.3.14.

jQuery has been updated to v1.11.2.

jQuery-UI has been updated to v1.11.3. Currently, AngularFaces doesn't use jQuery, so you will notice this only if your application imports jQuery-UI.

Removed debug code

AngularFaces 2.1.2 (February 25, 2015)

Fixed a strange bug reordering PuiLabels and PuiMessages on postbacks.

AngularFaces 2.1.1 (February 23, 2015)

Improved the compatibility to application servers by detecting more reliably whether Mojarra or MyFaces is to be used.

Javascript libraries are now loaded in the correct order (including jQuery-UI).

Did you ever wonder why JSF integrates drop down menu (aka comboboxes) in such a clumsy way? I found a way to write selectOneMenu almost the way it’s written in pure HTML pages.

AngularFaces 2.1 updated to AngularJS 1.3. Unfortunately, this is a potential source of incompatibilities. Luckily, it’s almost the only such source. Everything else should migrate smoothly.

The CombinedResourceHandler of OmniFaces is supported. That’s an important point because AngularFaces pages tend to deliver many Javascript files. Omnifaces boils these files down to a single file, which loads a lot faster than many small files.

The “automagical” generation of labels and messages and be configured much more flexible. Originally, you only could disable this feature on a per-page basis. Now it’s possible to add the attributes addLabel="false" and addMessages="false" to every container object that’s part of the JSF tree.

AngularFaces 2.1.12 (December 11, 2016)

AngularFaces 2.1.11 (February 08, 2016)

Improved support for BootsFaces. Now both the old and the new version of BootsFaces are supported.

AngularFaces 2.1.10 (January 16, 2016)

Improved support for BootsFaces. The old BootsFaces detection mechanism had to be extended because of the new
package layout of BootsFaces.

AngularFaces 2.1.9 (September 24, 2015)

Support for the @NotEmpty annotation of Hibernate

PuiLabel and PuiMessage now access the field they refer to, even when they are rendered in a data table

Add an option to disable translation globally

Add an option to disable the automatic addition of labels and messages globally

AngularFaces 2.1.8 (July 02, 2015)

Updated to AngularJS 1.3.16 and jQuery 1.11.3

repaired ng-sync

AngularFaces 2.1.7 (June 28, 2015)

AngularFaces now copes with EL expressions in every attribute. In particular, AngularJS controllers now can be selected
by a JSF bean (i.e. <div ng-controller="# {mainBean.currentAngularJSController}" />).

Now it's possible to suppress the automatic loading of the main.js file (see issue 51. )

Client-side messages used to ignore the severity level, which led to a weird appearance in PrimeFaces applications. This error has been fixed.

Now you can use multiple AngularJS controllers on a single JSF view. For instance, a modal dialog can have its own AngularJS controller.

There's are several new options to suppress the automatic loading of AngularJS, jQuery, jQuery-UI and angular-messages.js. This is useful
if you've minified and merge the individual files, so that AngularFaces doesn't detect that the base libraries already have been loaded. Also
see issue 45.

Starting with AngularFaces 2.1.7, every AngularFaces context parameter in the web.xml file is prefixed by "AngularFaces." In the case of
the context parameter "clientSideMessages" which has been introduced in AngularFaces 2.1.5, both the old and the new
parameter are valid.

AngularFaces 2.1.6 (June 16, 2015)

AF 2.1.6 catches an exception that's thrown by the Glassfish application server when AngularFaces tries to
translate an attribute that doesn't exist.

AngularFaces 2.1.5 (May 30, 2015)

AF 2.1.5 adds the context parameter clientSideMessages. You can add it to the web.xml file to suppress
the automatic replacement of h:messages by a client-side puimessages component.

AngularFaces 2.1.4 (March 25, 2015)

AF 2.1.4 is the smallest possible update: it consists of a single bit. Unfortunately, it's an important bit.
AngularFaces 2.1.4 comes pre-packaged with jQueryUI 1.11.3. Previous versions added a script include of the
non-existing version 1.11.2. Now jQueryUI is included correctly.

AngularFaces 2.1.3 (March 14, 2015)

AF 2.1.3 fixes the bug that forced developers to use prependId="false". The bugfix relies on
MutationObserver, which is not compatible to older Internet Explorers. According to
"Can I use?", only IE 11+ is supported.
Note that AngularJS itself doesn't support the separator character JSF uses in ids. Most features will work fine,
but some features such as setting a watch or ngMessages fail.

Added <ac:include /> which is a language-aware version of <ui:include />.
It checks which languages the user prefers (according to their browser settings) and tries to add the language
code to the filename. If no such file is found, <ac:include /> defaults to the standard
behaviour of <ui:include />.

AngularJS has been updated to v1.3.14.

jQuery has been updated to v1.11.2.

jQuery-UI has been updated to v1.11.3. Currently, AngularFaces doesn't use jQuery, so you will notice this only if your application imports jQuery-UI.

Removed debug code

AngularFaces 2.1.2 (February 25, 2015)

Fixed a strange bug reordering PuiLabels and PuiMessages on postbacks.

AngularFaces 2.1.1 (February 23, 2015)

Improved the compatibility to application servers by detecting more reliably whether Mojarra or MyFaces is to be used.

Javascript libraries are now loaded in the correct order (including jQuery-UI).

Did you ever wonder why JSF integrates drop down menu (aka comboboxes) in such a clumsy way? I found a way to write selectOneMenu almost the way it’s written in pure HTML pages.

AngularFaces 2.1 updated to AngularJS 1.3. Unfortunately, this is a potential source of incompatibilities. Luckily, it’s almost the only such source. Everything else should migrate smoothly.

The CombinedResourceHandler of OmniFaces is supported. That’s an important point because AngularFaces pages tend to deliver many Javascript files. Omnifaces boils these files down to a single file, which loads a lot faster than many small files.

The “automagical” generation of labels and messages and be configured much more flexible. Originally, you only could disable this feature on a per-page basis. Now it’s possible to add the attributes addLabel="false" and addMessages="false" to every container object that’s part of the JSF tree.

AngularFaces 2.1.12 (December 11, 2016)

AngularFaces 2.1.11 (February 08, 2016)

Improved support for BootsFaces. Now both the old and the new version of BootsFaces are supported.

AngularFaces 2.1.10 (January 16, 2016)

Improved support for BootsFaces. The old BootsFaces detection mechanism had to be extended because of the new
package layout of BootsFaces.

AngularFaces 2.1.9 (September 24, 2015)

Support for the @NotEmpty annotation of Hibernate

PuiLabel and PuiMessage now access the field they refer to, even when they are rendered in a data table

Add an option to disable translation globally

Add an option to disable the automatic addition of labels and messages globally

AngularFaces 2.1.8 (July 02, 2015)

Updated to AngularJS 1.3.16 and jQuery 1.11.3

repaired ng-sync

AngularFaces 2.1.7 (June 28, 2015)

AngularFaces now copes with EL expressions in every attribute. In particular, AngularJS controllers now can be selected
by a JSF bean (i.e. <div ng-controller="# {mainBean.currentAngularJSController}" />).

Now it's possible to suppress the automatic loading of the main.js file (see issue 51. )

Client-side messages used to ignore the severity level, which led to a weird appearance in PrimeFaces applications. This error has been fixed.

Now you can use multiple AngularJS controllers on a single JSF view. For instance, a modal dialog can have its own AngularJS controller.

There's are several new options to suppress the automatic loading of AngularJS, jQuery, jQuery-UI and angular-messages.js. This is useful
if you've minified and merge the individual files, so that AngularFaces doesn't detect that the base libraries already have been loaded. Also
see issue 45.

Starting with AngularFaces 2.1.7, every AngularFaces context parameter in the web.xml file is prefixed by "AngularFaces." In the case of
the context parameter "clientSideMessages" which has been introduced in AngularFaces 2.1.5, both the old and the new
parameter are valid.

AngularFaces 2.1.6 (June 16, 2015)

AF 2.1.6 catches an exception that's thrown by the Glassfish application server when AngularFaces tries to
translate an attribute that doesn't exist.

AngularFaces 2.1.5 (May 30, 2015)

AF 2.1.5 adds the context parameter clientSideMessages. You can add it to the web.xml file to suppress
the automatic replacement of h:messages by a client-side puimessages component.

AngularFaces 2.1.4 (March 25, 2015)

AF 2.1.4 is the smallest possible update: it consists of a single bit. Unfortunately, it's an important bit.
AngularFaces 2.1.4 comes pre-packaged with jQueryUI 1.11.3. Previous versions added a script include of the
non-existing version 1.11.2. Now jQueryUI is included correctly.

AngularFaces 2.1.3 (March 14, 2015)

AF 2.1.3 fixes the bug that forced developers to use prependId="false". The bugfix relies on
MutationObserver, which is not compatible to older Internet Explorers. According to
"Can I use?", only IE 11+ is supported.
Note that AngularJS itself doesn't support the separator character JSF uses in ids. Most features will work fine,
but some features such as setting a watch or ngMessages fail.

Added <ac:include /> which is a language-aware version of <ui:include />.
It checks which languages the user prefers (according to their browser settings) and tries to add the language
code to the filename. If no such file is found, <ac:include /> defaults to the standard
behaviour of <ui:include />.

AngularJS has been updated to v1.3.14.

jQuery has been updated to v1.11.2.

jQuery-UI has been updated to v1.11.3. Currently, AngularFaces doesn't use jQuery, so you will notice this only if your application imports jQuery-UI.

Removed debug code

AngularFaces 2.1.2 (February 25, 2015)

Fixed a strange bug reordering PuiLabels and PuiMessages on postbacks.

AngularFaces 2.1.1 (February 23, 2015)

Improved the compatibility to application servers by detecting more reliably whether Mojarra or MyFaces is to be used.

Javascript libraries are now loaded in the correct order (including jQuery-UI).

Did you ever wonder why JSF integrates drop down menu (aka comboboxes) in such a clumsy way? I found a way to write selectOneMenu almost the way it’s written in pure HTML pages.

AngularFaces 2.1 updated to AngularJS 1.3. Unfortunately, this is a potential source of incompatibilities. Luckily, it’s almost the only such source. Everything else should migrate smoothly.

The CombinedResourceHandler of OmniFaces is supported. That’s an important point because AngularFaces pages tend to deliver many Javascript files. Omnifaces boils these files down to a single file, which loads a lot faster than many small files.

The “automagical” generation of labels and messages and be configured much more flexible. Originally, you only could disable this feature on a per-page basis. Now it’s possible to add the attributes addLabel="false" and addMessages="false" to every container object that’s part of the JSF tree.

AngularFaces 2.1.12 (December 11, 2016)

AngularFaces 2.1.11 (February 08, 2016)

Improved support for BootsFaces. Now both the old and the new version of BootsFaces are supported.

AngularFaces 2.1.10 (January 16, 2016)

Improved support for BootsFaces. The old BootsFaces detection mechanism had to be extended because of the new
package layout of BootsFaces.

AngularFaces 2.1.9 (September 24, 2015)

Support for the @NotEmpty annotation of Hibernate

PuiLabel and PuiMessage now access the field they refer to, even when they are rendered in a data table

Add an option to disable translation globally

Add an option to disable the automatic addition of labels and messages globally

AngularFaces 2.1.8 (July 02, 2015)

Updated to AngularJS 1.3.16 and jQuery 1.11.3

repaired ng-sync

AngularFaces 2.1.7 (June 28, 2015)

AngularFaces now copes with EL expressions in every attribute. In particular, AngularJS controllers now can be selected
by a JSF bean (i.e. <div ng-controller="# {mainBean.currentAngularJSController}" />).

Now it's possible to suppress the automatic loading of the main.js file (see issue 51. )

Client-side messages used to ignore the severity level, which led to a weird appearance in PrimeFaces applications. This error has been fixed.

Now you can use multiple AngularJS controllers on a single JSF view. For instance, a modal dialog can have its own AngularJS controller.

There's are several new options to suppress the automatic loading of AngularJS, jQuery, jQuery-UI and angular-messages.js. This is useful
if you've minified and merge the individual files, so that AngularFaces doesn't detect that the base libraries already have been loaded. Also
see issue 45.

Starting with AngularFaces 2.1.7, every AngularFaces context parameter in the web.xml file is prefixed by "AngularFaces." In the case of
the context parameter "clientSideMessages" which has been introduced in AngularFaces 2.1.5, both the old and the new
parameter are valid.

AngularFaces 2.1.6 (June 16, 2015)

AF 2.1.6 catches an exception that's thrown by the Glassfish application server when AngularFaces tries to
translate an attribute that doesn't exist.

AngularFaces 2.1.5 (May 30, 2015)

AF 2.1.5 adds the context parameter clientSideMessages. You can add it to the web.xml file to suppress
the automatic replacement of h:messages by a client-side puimessages component.

AngularFaces 2.1.4 (March 25, 2015)

AF 2.1.4 is the smallest possible update: it consists of a single bit. Unfortunately, it's an important bit.
AngularFaces 2.1.4 comes pre-packaged with jQueryUI 1.11.3. Previous versions added a script include of the
non-existing version 1.11.2. Now jQueryUI is included correctly.

AngularFaces 2.1.3 (March 14, 2015)

AF 2.1.3 fixes the bug that forced developers to use prependId="false". The bugfix relies on
MutationObserver, which is not compatible to older Internet Explorers. According to
"Can I use?", only IE 11+ is supported.
Note that AngularJS itself doesn't support the separator character JSF uses in ids. Most features will work fine,
but some features such as setting a watch or ngMessages fail.

Added <ac:include /> which is a language-aware version of <ui:include />.
It checks which languages the user prefers (according to their browser settings) and tries to add the language
code to the filename. If no such file is found, <ac:include /> defaults to the standard
behaviour of <ui:include />.

AngularJS has been updated to v1.3.14.

jQuery has been updated to v1.11.2.

jQuery-UI has been updated to v1.11.3. Currently, AngularFaces doesn't use jQuery, so you will notice this only if your application imports jQuery-UI.

Removed debug code

AngularFaces 2.1.2 (February 25, 2015)

Fixed a strange bug reordering PuiLabels and PuiMessages on postbacks.

AngularFaces 2.1.1 (February 23, 2015)

Improved the compatibility to application servers by detecting more reliably whether Mojarra or MyFaces is to be used.

Javascript libraries are now loaded in the correct order (including jQuery-UI).

Did you ever wonder why JSF integrates drop down menu (aka comboboxes) in such a clumsy way? I found a way to write selectOneMenu almost the way it’s written in pure HTML pages.

AngularFaces 2.1 updated to AngularJS 1.3. Unfortunately, this is a potential source of incompatibilities. Luckily, it’s almost the only such source. Everything else should migrate smoothly.

The CombinedResourceHandler of OmniFaces is supported. That’s an important point because AngularFaces pages tend to deliver many Javascript files. Omnifaces boils these files down to a single file, which loads a lot faster than many small files.

The “automagical” generation of labels and messages and be configured much more flexible. Originally, you only could disable this feature on a per-page basis. Now it’s possible to add the attributes addLabel="false" and addMessages="false" to every container object that’s part of the JSF tree.