Für diese Seite gibt es noch keine deutsche Übersetzung. Bitte lesen Sie solange die englische Version. Wir bitten Sie um Verständnis.
The idea of the JSF 2.2 HTML5 dialect is to start with a native HTML page, and to add a few JSF attributes to make it an JSF view. AngularFaces take this idea to another level.
AngularFaces allows you to use these tags without a preceding "h:", even if there's no "jsf:" attribute:
You have to add a few lines to the web.xml
to activate this features. AngularFaces 2.1 doesn't allow you to
get rid of the feature altogether: it's needed internally. But you can chose between a progressive version and a conservative version. The latter
only cares about a few tags:
h:messages
and prime:messages
ngsync
translate
and i18n
The progressive tag decorator supports most tags of BootsFaces. This feature is activated only if BootsFaces is detected in the classpath.
Read the complete list of supported tag at the BootsFaces showcase.
Even if it's only a handful of changes, it's astonishing how much tidier these few changes make your JSF file looks:
The idea of the JSF 2.2 HTML5 dialect is to start with a native HTML page, and to add a few JSF attributes to make it an JSF view. AngularFaces take this idea to another level.
AngularFaces allows you to use these tags without a preceding "h:", even if there's no "jsf:" attribute:
You have to add a few lines to the web.xml
to activate this features. AngularFaces 2.1 doesn't allow you to
get rid of the feature altogether: it's needed internally. But you can chose between a progressive version and a conservative version. The latter
only cares about a few tags:
h:messages
and prime:messages
ngsync
translate
and i18n
The progressive tag decorator supports most tags of BootsFaces. This feature is activated only if BootsFaces is detected in the classpath.
Read the complete list of supported tag at the BootsFaces showcase.
Even if it's only a handful of changes, it's astonishing how much tidier these few changes make your JSF file looks:
A página ainda não foi traduzido para o Português. Por favor, leia a tradução em Inglês. Pedimos desculpas por qualquer inconveniente.
The idea of the JSF 2.2 HTML5 dialect is to start with a native HTML page, and to add a few JSF attributes to make it an JSF view. AngularFaces take this idea to another level.
AngularFaces allows you to use these tags without a preceding "h:", even if there's no "jsf:" attribute:
You have to add a few lines to the web.xml
to activate this features. AngularFaces 2.1 doesn't allow you to
get rid of the feature altogether: it's needed internally. But you can chose between a progressive version and a conservative version. The latter
only cares about a few tags:
h:messages
and prime:messages
ngsync
translate
and i18n
The progressive tag decorator supports most tags of BootsFaces. This feature is activated only if BootsFaces is detected in the classpath.
Read the complete list of supported tag at the BootsFaces showcase.
Even if it's only a handful of changes, it's astonishing how much tidier these few changes make your JSF file looks:
Für diese Seite gibt es noch keine deutsche Übersetzung. Bitte lesen Sie solange die englische Version. Wir bitten Sie um Verständnis.
The idea of the JSF 2.2 HTML5 dialect is to start with a native HTML page, and to add a few JSF attributes to make it an JSF view. AngularFaces take this idea to another level.
AngularFaces allows you to use these tags without a preceding "h:", even if there's no "jsf:" attribute:
You have to add a few lines to the web.xml
to activate this features. AngularFaces 2.1 doesn't allow you to
get rid of the feature altogether: it's needed internally. But you can chose between a progressive version and a conservative version. The latter
only cares about a few tags:
h:messages
and prime:messages
ngsync
translate
and i18n
The progressive tag decorator supports most tags of BootsFaces. This feature is activated only if BootsFaces is detected in the classpath.
Read the complete list of supported tag at the BootsFaces showcase.
Even if it's only a handful of changes, it's astonishing how much tidier these few changes make your JSF file looks: