deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r946335 - in /websites/staging/deltaspike/trunk/content: ./ documentation/jsf.html
Date Sat, 04 Apr 2015 20:24:30 GMT
Author: buildbot
Date: Sat Apr  4 20:24:29 2015
New Revision: 946335

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/documentation/jsf.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Apr  4 20:24:29 2015
@@ -1 +1 @@
-1671310
+1671311

Modified: websites/staging/deltaspike/trunk/content/documentation/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/documentation/jsf.html Sat Apr  4 20:24:29 2015
@@ -831,7 +831,7 @@ as possible - which are terminated autom
 In such an use-case you can use this scope. The simple rule is, as long
 as the bean is referenced by a page - the bean will be available for the
 next page (if it is used again the bean will be forwarded again). It is
-important that it is based on the view-id of a page (it isis not based on
+important that it is based on the view-id of a page (it is not based on
 the request) so, for example, Ajax requests do not trigger a cleanup if the
 request doesis not access all view-access scoped beans of the page. That’s
 also the reason for the name @<em>View</em>AccessScoped.</p>
@@ -1236,10 +1236,10 @@ needed for using a different folder-name
 if they do not inherit from
 <code>org.apache.deltaspike.core.api.config.view.ViewConfig</code> <strong>nor</strong>
have a
 view-config for a page nested into them (like Pages.Wizard1.Step1). If
-it isis not used explicitly, it gets added automatically (so you can query
+it is not used explicitly, it gets added automatically (so you can query
 the meta-data at runtime even in cases you haveis not placed the
 annotations explicitly). <code>@View</code> allows to customize a bit more and
it
-also gets added automatically if it isis not used explicitly. Whereas
+also gets added automatically if it is not used explicitly. Whereas
 <code>@Folder</code> gets added to all nested interfaces (above a view-config
class
 - like Pages and Pages.Wizard1), <code>@View</code> only gets added to classes
 which in-/directly inherit from
@@ -1452,7 +1452,7 @@ inherited along the inheritance path.</p
 <p>Since the view-config is static, an approach to add parameters is
 needed. The following part shows different possibilities to add
 parameters which end up in the final URL after '?' (in case of the
-integration with JSF). It isis not needed to add all (types of) parameters
+integration with JSF). It is not needed to add all (types of) parameters
 that way. Some get added automatically based on special meta-data (e.g.
 <code>@View#navigation</code> and <code>@View#viewParams</code>).
Instead of adding
 <code>"faces-redirect=true"</code> manually it is done for you as soon as you
are



Mime
View raw message