@@ -270,8 +269,7 @@ required)

Without existing WF8

Executing the Arquillian tests with JBoss-WF8 (without WF8 -installation)

Executing the Arquillian tests with JBoss-WF8 (without WF8 installation)

Modified: deltaspike/site/trunk/content/documentation/configuration.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/configuration.html?rev=1626650&r1=1626649&r2=1626650&view=diff ============================================================================== --- deltaspike/site/trunk/content/documentation/configuration.html (original) +++ deltaspike/site/trunk/content/documentation/configuration.html Sun Sep 21 23:48:24 2014 @@ -183,6 +183,7 @@ body {

getPropertyValue()
getProjectStageAwarePropertyValue()
getPropertyAwarePropertyValue()
handling of default values

@@ -254,7 +255,7 @@ rely on CDI it can for example be used t

Currently this is e.g. used to configure the value of the current ProjectStage, configured values which can be -used in the expressions for @Exclude, Deactivatable, etc. DeltaSpike +used in the expressions for @Exclude, 'Deactivatable', etc. DeltaSpike needs such a low-level approach for several features internally, but users can utilize it for their own needs as well. This is done by using the ConfigResolver which resolves and caches `ConfigSource`s per @@ -316,17 +317,16 @@ following lookup chain until we found a

-
key + . + projectStage , e.g. "databaseconfig.username.Production"
+
key + '.' + projectStage , e.g. "databaseconfig.username.Production"
key alone , e.g. "databaseconfig.username"

getPropertyAwarePropertyValue() -_~_~_~_~_~_~_~_~_~_~_~

getPropertyAwarePropertyValue()

The method ConfigResolver#getProjectStageAwarePropertyValue(String key, String property) @@ -349,7 +349,7 @@ resolve the value of the property:

-
propertyValue = property + . + projectStage, e.g. "dbvendor.Production"
+
propertyValue = property + '.' + projectStage, e.g. "dbvendor.Production"
if nothing found: propertyValue = property, e.g. "dbvendor"
@@ -357,19 +357,19 @@ resolve the value of the property:

Let’s assume we found the value mysql for our dbvendor. In this case +

Let’s assume we found the value 'mysql' for our dbvendor. In this case the following lookup chain is used until a value got found:

-
key + . + property + projectstage, e.g. "databaseconfig.username.mysql.Production"
+
key + '.' + property + projectstage, e.g. "databaseconfig.username.mysql.Production"
-
key + . + property, e.g. "databaseconfig.username.mysql"
+
key + '.' + property, e.g. "databaseconfig.username.mysql"
-
key + . + projectstage, e.g. "databaseconfig.username.Production"
+
key + '.' + projectstage, e.g. "databaseconfig.username.Production"
key, e.g. "databaseconfig.username"
@@ -408,7 +408,7 @@ values. The ConfigResolver ConfigSource to lookup the property in question.

Each ConfigSource has a specified ordinal which can be configured +

Each 'ConfigSource' has a specified 'ordinal' which can be configured using the key deltaspike_ordinal. This ordinal get’s used to determine the importance of the values taken from the very ConfigSource. A higher ordinal means that the values taken from this ConfigSource will override @@ -459,7 +459,7 @@ caching.

To change the lookup order, you have to configure the ordinal in the corresponding config source (e.g. to change the config ordinal of the config source for system properties, you have to set the system property -with the ordinal key deltaspike_ordinal and the new value).

+with the ordinal key 'deltaspike_ordinal' and the new value).

Example with /META-INF/apache-deltaspike.properties: If the properties @@ -484,7 +484,7 @@ independent config-source, but all of th

Custom Config-Sources

ConfigSources are picked up using the ‘java.util.ServiceLoader’ +

ConfigSources are picked up using the `java.util.ServiceLoader' mechanism.

Added: deltaspike/site/trunk/content/documentation/container-control-test.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/container-control-test.html?rev=1626650&view=auto ============================================================================== --- deltaspike/site/trunk/content/documentation/container-control-test.html (added) +++ deltaspike/site/trunk/content/documentation/container-control-test.html Sun Sep 21 23:48:24 2014 @@ -0,0 +1,400 @@ + + + + + + + + + +Container & Control + + + + + + + + + + + + + + + + +

Container & Control

+ +

Introduction
+
- CdiContainer
- ContextControl usage
- Embedded Servlet Support
- +
  - Jetty
  - Undertow
  - Tomcat
  +
+

+ +

Introduction

There are basically two parts:

+
The CdiContainer interface allows to boot and shutdown the CDI container in SE applications.
+
+
The ContextControl interface allows to control the life-cycle of the built-in contexts of the CDI container.
+

CdiContainer

You can use the CdiContainerLoader as a simple factory to gain access to the underlying CdiContainer implementation. This is of little interest for Java EE applications since the CDI Container +already gets properly booted and shut down by the Servlet container integration.

// this will give you a CdiContainer for Weld or OWB, depending on the jar you added
+CdiContainer cdiContainer = CdiContainerLoader.getCdiContainer();
+// now we gonna boot the CDI container. This will trigger the classpath scan, etc
+cdiContainer.boot();
+// and finally we like to start all built-in contexts
+cdiContainer.getContextControl().startContexts();
+// now we can use CDI in our SE application.
+// And there is not a single line of OWB or Weld specific code in your project!
+// finally we gonna stop the container
+cdiContainer.shutdown();

ContextControl usage

The ContextControl interface allows you to start and stop built-in standard Contexts like @RequestScoped, @ConversationScoped, @SessionScoped, etc. It is provided as @Dependent bean and can get injected in the classic CDI way. This is not only usable in Java SE projects but also very helpful in Servlets and Java EE containers.

Restarting the RequestContext in unit tests

In unit testing it can be necessary to test with attached and also with detached JPA entities. A very common approach for +JPA is the link: entitymanager-per-request approach +and thus have a producer method which creates a @RequestScoped EntityManager. Since a single unit test is usually +treated as one ârequestâ a problem arises detaching entities.

Using ContextControl to detach entities:

@Test
+public void testMyBusinessLogic()
+{
+    doSomeJpaStuff()
+    MyEntity me = em.find(...);
+    ContextControl ctxCtrl = BeanProvider.getContextualReference(ContextControl.class);
+    //stopping the request context will dispose the @RequestScoped EntityManager
+    ctxCtrl.stopContext(RequestScoped.class);
+    // and now immediately restart the context again
+    ctxCtrl.startContext(RequestScoped.class);
+    // the entity 'em' is now in a detached state!
+    doSomeStuffWithTheDetachedEntity(em);
+}

Attaching a Request Context to a new thread in EE

Accessing the @RequestScoped bean in a new thread will result in a ContextNotActiveException. The request-context usually gets started for a particular thread via a simple ServletRequestListener. So "no servlet-request" means that there is no Servlet-Context for the current (/new) Thread. +You might face such issues, if you would like to reuse business services in e.g. a Quartz Job.

Controlling the request-context for a Quartz-Job:

public class CdiJob implements org.quartz.Job
+{
+    public void execute(JobExecutionContext context) throws JobExecutionException
+    {
+        ContextControl ctxCtrl = BeanProvider.getContextualReference(ContextControl.class);
+        //this will implicitly bind a new RequestContext to the current thread
+        ctxCtrl.startContext(RequestScoped.class);
+        try
+        {
+            doYourWork();
+        }
+        finally
+        {
+            //stop the RequestContext to ensure that all request-scoped beans get cleaned up.
+            ctxCtrl.stopContext(RequestScoped.class);
+        }
+    }
+}

Embedded Servlet Support

Starting with 1.0.2, you can use DeltaSpike to power embedded Servlet runtimes. This work is done via Servlet Listeners. The configuration is specific to each container, below are some examples.

The two main listeners are CdiServletRequestListener and CdiServletContextListener. CdiServletRequestListener is responsible for starting a RequestContext on each incoming request. In most containers this is all you need. For Tomcat specifically, you need to use CdiServletContextListener which registers the CdiServletRequestListener.

The main usecase for this feature is for lightweight embedded runtimes, microservices. For each of these, it is assumed that you are using the following start up code somewhere:

CdiContainer cdiContainer = CdiContainerLoader.getCdiContainer();
+cdiContainer.boot();
+cdiContainer.getContextControl().startContexts();

Jetty

For Jetty, you need to add an EventListener which will be your CdiServletRequestListener. The object must be instantiated. This must be done before the server is started.

Server server = new Server(port);
+ServletContextHandler context = new ServletContextHandler(ServletContextHandler.SESSIONS);
+context.setContextPath("/");
+server.setHandler(context);
+context.addEventListener(new CdiServletRequestListener());
+context.addServlet(new ServletHolder(new YourServlet()),"/*");
+server.start();

Undertow

For Undertow, you register the CdiServletRequestListener via ListenerInfo by passing in the class to their builders. Then you add the ListenerInfo to your deployment before starting.

ServletInfo servletInfo = Servlets.servlet("YourServletName", YourServlet.class).setAsyncSupported(true)
+    .setLoadOnStartup(1).addMapping("/*");
+ListenerInfo listenerInfo = Servlets.listener(CdiServletRequestListener.class);  (1)
+DeploymentInfo di = new DeploymentInfo()
+        .addListener(listenerInfo) (2)
+        .setContextPath("/")
+        .addServlet(servletInfo).setDeploymentName("CdiSEServlet")
+        .setClassLoader(ClassLoader.getSystemClassLoader());
+DeploymentManager deploymentManager = Servlets.defaultContainer().addDeployment(di);
+deploymentManager.deploy();
+Undertow server = Undertow.builder()
+        .addHttpListener(port, "localhost")
+        .setHandler(deploymentManager.start())
+        .build();
+server.start();

+
Register as a listener.
+
+
Add to deployment
+

Tomcat

For Tomcat, you need to register the CdiServletContextListener instead of the CdiServletRequestListener. It is added as an ApplicationListener by passing in the class name as a String.

Tomcat tomcat = new Tomcat();
+tomcat.setPort(port);
+File base = new File("...");
+Context ctx = tomcat.addContext("/",base.getAbsolutePath());
+StandardContext standardContext = (StandardContext)ctx;
+standardContext.addApplicationListener(CdiServletContextListener.class.getName());
+Wrapper wrapper = Tomcat.addServlet(ctx,"YourServlet",YourServlet.class.getName());
+wrapper.addMapping("/*");
+tomcat.start();

+ +

+ + + +

+ + + + \ No newline at end of file Modified: deltaspike/site/trunk/content/documentation/core.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/core.html?rev=1626650&r1=1626649&r2=1626650&view=diff ============================================================================== --- deltaspike/site/trunk/content/documentation/core.html (original) +++ deltaspike/site/trunk/content/documentation/core.html Sun Sep 21 23:48:24 2014 @@ -191,8 +191,7 @@ body {

Customizing the message context

Injecting Resources

Exception Control +

Injecting Resources

Usage
Exception handlers

The BeanProvider is a class which provides (static) util methods which allow to lookup beans if it isn’t possible to inject them via @Inject or if the lookup depends on dynamic conditions. Instead of using the -term bean, the term contextual instance is used because that’s the +term 'bean', the term 'contextual instance' is used because that’s the term used by CDI itself.

@@ -277,7 +276,7 @@ question. CDI qualifiers are annotations implement a corresponding literal for providing an instance.

Literal implementation for @MyQualifier:

Literal implementation for '@MyQualifier':

@@ -319,7 +318,7 @@ the following examples show how to do a

MyBean myBean = BeanProvider.getContextualReference("myBean", false, MyBean.class);

MyBean myBean = BeanProvider.getContextualReference("myBean", false, MyBean.class);

@@ -559,7 +558,7 @@ ExpressionInterpreter is needed:

Literals

Literals allow the instantiation of annotations by extending the -abstract class javax.enterprise.util.AnnotationLiteral

+abstract class 'javax.enterprise.util.AnnotationLiteral'

Example

@@ -895,9 +894,9 @@ and FileResourceProvider. T the InjectableResourceProvider interface to allow reading from alternate sources, if needed (e.g. database LOBs, NoSQL storage areas).

===Exception Control

Exception Control

Exception handling in DeltaSpike is based around the CDI eventing model. While the implementation of exception handlers may not be the same as a Added: deltaspike/site/trunk/content/documentation/deltaspike_1.0.3.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/deltaspike_1.0.3.html?rev=1626650&view=auto ============================================================================== --- deltaspike/site/trunk/content/documentation/deltaspike_1.0.3.html (added) +++ deltaspike/site/trunk/content/documentation/deltaspike_1.0.3.html Sun Sep 21 23:48:24 2014 @@ -0,0 +1,338 @@ + + + + + + + + + +DeltaSpike Release Notes v1.0.3 + + + + + + + + + + + + + + +

+ +

DeltaSpike Release Notes v1.0.3

+ +

Announcement
Highlights +
- Code Changes
- Documentation Changes
+
Credits & Thanks
Full Release Notes

+ +

Announcement

The DeltaSpike team is proud to announce the release of v1.0.3. See our release announcement email for additional information.

Please read our setup guide to add DeltaSpike to your application.

Highlights

Code Changes

+
Multiple improvements and fixes to our JSF Support
+
+
Fixes around client window handling with JSF Native & Primefaces AJAX
+
+
Window ID handling now works properly with lazy configuration
+
+
Exception handling has been improved; better cross module support, JSF integration for Exceptions is improved.
+
+
CDI versions are no longer included directly in any profile, to help with running applications against CDI 1.1/1.2 runtimes
+
+
BeanManagerProvider will automatically use a child’s classloader for BeanManager detection in case none found for the parent.
+

Documentation Changes

Several important documentation changes went in as well

+
Scope availability in the core module
+
+
Documentation around Security and PicketLink
+
+
The first steps to moving our documentation to asciidoc has been performed
+

Credits & Thanks

+
Thanks to all those that contributed via OpenHub
+
+
Thanks to those who reviewed and voted on the release
+

Full Release Notes

Bug +

[DELTASPIKE-696] - Remove unneeded dependencies on CDICtrl Servlet +
[DELTASPIKE-706] - Multiple CDI API versions on classpath in JSF module tests (Weld) +
[DELTASPIKE-710] - Error using clientWindow and (p|f):ajax +
[DELTASPIKE-717] - Exception handlers not invoked when @Secured ViewConfig is violated in an app with JSF module without a DefaultErrorView page +
[DELTASPIKE-719] - Only one voter invoked if multiple voters are applied through a stereotype +
[DELTASPIKE-723] - Exception bypassing on JSF conversion errors +
[DELTASPIKE-726] - Lazy window handling doesn't recognize new windows anymore +
[DELTASPIKE-729] - f:viewAction is executed twice with LAZY window handling mode +

+ +

Improvement +

[DELTASPIKE-692] - workaround for tests which don't use optional classes +
[DELTASPIKE-699] - Signature relaxing of attribute method() in CriteriaSupport +
[DELTASPIKE-708] - Veto the AbstractEntityRepository class +
[DELTASPIKE-712] - BeanManagerProvider : Wrap usage in parent class loaders +

+ +

New Feature +

[DELTASPIKE-702] - Add support to GreaterThan and LessThan in criteria to dates +

+ +

Task +

[DELTASPIKE-640] - Document Scopes in Core module +
[DELTASPIKE-677] - document ds-security in combination with picketlink +
[DELTASPIKE-697] - Set the baseDir to reside in the target directory for tomcat tests. +
[DELTASPIKE-698] - re-visit glassfish4 profile +
[DELTASPIKE-711] - Create placeholder documentation directory +
[DELTASPIKE-716] - Migrate documentation format to asciidoc at git repo +
[DELTASPIKE-730] - release notes for v1.0.3 +

+ +

+ + + +

+ + + + \ No newline at end of file Modified: deltaspike/site/trunk/content/documentation/index.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/index.html?rev=1626650&r1=1626649&r2=1626650&view=diff ============================================================================== --- deltaspike/site/trunk/content/documentation/index.html (original) +++ deltaspike/site/trunk/content/documentation/index.html Sun Sep 21 23:48:24 2014 @@ -191,8 +191,8 @@ body {

Configuration of DeltaSpike Core

Configuration of DeltaSpike Modules

With Java SE

… for Apache OpenWebBeans

… for JBoss Weld (RI)

… for Apache OpenWebBeans

… for JBoss Weld (RI)

For Embedded Servlet Runtimes, you can add

Testing Snapshots

@@ -422,8 +422,7 @@ manually.

Project Configuration with Maven

Hint: In the listings below replace the placeholders for the version -with the version of your choice or use:

Hint: In the listings below replace the placeholders for the version with the version of your choice or use:

@@ -678,7 +677,7 @@ with the version of your choice or use:<

… for Apache OpenWebBeans

<dependency>
@@ -705,7 +704,7 @@ with the version of your choice or use:<


 
- … for JBoss Weld (RI)
+… for JBoss Weld (RI)
 
 
 <dependency>

Modified: deltaspike/site/trunk/content/documentation/jpa.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/jpa.html?rev=1626650&r1=1626649&r2=1626650&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/jpa.html (original)
+++ deltaspike/site/trunk/content/documentation/jpa.html Sun Sep 21 23:48:24 2014
@@ -172,7 +172,6 @@ body {
 				
        	 		
 @Transactional
-@TransactionScoped
 Extended Persistence Contexts
 JTA Support
 
@@ -508,11 +507,9 @@ a different EntityManager. 
 FirstLevelTransactionBean e.g. to try an optional path instead of an
 immediate rollback.
 
+
+==@TransactionScoped
 
-

-
-@TransactionScoped
-
 
 @Transactional also starts a context which is available as long as the
 transaction started by @Transactional. Besides other beans you can use

Modified: deltaspike/site/trunk/content/documentation/jsf.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/jsf.html?rev=1626650&r1=1626649&r2=1626650&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/jsf.html (original)
+++ deltaspike/site/trunk/content/documentation/jsf.html Sun Sep 21 23:48:24 2014
@@ -215,10 +215,11 @@ body {
 
Intro
 Motivation
 Bean-discovery-mode annotated
-Basic API usages
+
Basic API usages
 
 File (@View) and Folder (@Folder) paths
 Navigation Parameters
+Static Configuration via @NavigationParameter
 Security Integration via @Secured
 View-Controller Callbacks via @ViewControllerRef
 Referencing Views via @ViewRef
@@ -331,7 +332,7 @@ contains a method to prevent this proble
 the browser window via JavaScript. Usually this is rendered and executed
 in the same page as the user form. See the "Post-render window
 detection" paragraph for a more detailed description. The major downside
-of this solution is that we might already pollute foreign beans (and
+of this solution is that we might already pollute 'foreign' beans (and
 destroy their information) while rendering the page, which means this is
 not feasible as general solution.
 
@@ -366,13 +367,13 @@ windowId will be added as hidden input t
 
 
 Having the windowhandler.html site rendered between requests sometimes
-leads to some flickering if the destination page takes some time to
+leads to some 'flickering' if the destination page takes some time to
 load. The browser first renders our windowhandler and only after that
 the original page will get loaded. This effect may be minimized by
 branding the windowhandler.html page and providing an own one with a
 bgcolor which matches your application. For html-5 aware browsers we
-also got rid of this flickering by storing away a screenshot of the
-first page in onclick() and immediately restore this screenshot on the
+also got rid of this flickering by storing away a 'screenshot' of the
+first page in onclick() and immediately restore this 'screenshot' on the
 intermediate windowhandler.html page. Technically we do this by storing
 away the and css information into the html5 localStorage and restore them on the
 intermediate page. We also introduced a WindowConfig which is able to
@@ -599,7 +600,7 @@ implementation, you can just do it e.g. 
 
 
 
-Don’t forget to set the ClientWindowRenderMode to CUSTOM via the
+
Don’t forget to set the ClientWindowRenderMode to 'CUSTOM' via the
 JsfModuleConfig:
 
 
@@ -684,8 +685,8 @@ also the reason for the name @View
 Hint: @ViewAccessScoped beans are best used in conjunction with the
 CLIENTWINDOW window handling, which ensures a clean browser-tab
-separation without touching the old windowId. Otherwise a open in new
-tab on a page with a @ViewAccessScoped bean might cause the termination
+separation without touching the old windowId. Otherwise a 'open in new
+tab' on a page with a @ViewAccessScoped bean might cause the termination
 (and re-initialization) of that bean.
 

 

@@ -855,8 +856,7 @@ more work initially?
The short answer is:
 

 
-It gives a good return in case of real applications (esp. beyond simple
-demos).
+It gives a good return in case of real applications (esp. beyond simple demos).
 
 
 The long answer is:
@@ -931,7 +931,7 @@ like to use the mode annotated
 

 
-Basic API usages
+Basic API usages
 
 While reading this section keep the following simple rules in mind:
 Meta-data gets inherited along the path of Java inheritance
@@ -1137,7 +1137,7 @@ Pages.Wizard1.Step1).
 `NameBuilder`s inline or globally).
 
 
-@Folder#name
+@Folder#name
 
 The rules are pretty simple. You will get what you write. There are only
 two additional features:
@@ -1145,7 +1145,7 @@ two additional features:
 
 
 
-You don’t have to care about duplicated / (e.g. /folder1//folder2/step1.xhtml would get corrected auto. to /folder1/folder2/step1.xhtml)
+You don’t have to care about duplicated '/' (e.g. /folder1//folder2/step1.xhtml would get corrected auto. to /folder1/folder2/step1.xhtml)
 
 
 With "." at the beginning (e.g. "./") you can keep the path before.
@@ -1293,7 +1293,7 @@ inherited along the inheritance path.
 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
+parameters which end up in the final URL after '?' (in case of the
 integration with JSF). It isn’t needed to add all (types of) parameters
 that way. Some get added autom. based on special meta-data (e.g.
 @View#navigation and @View#viewParams). Instead of adding
@@ -1301,8 +1301,9 @@ that way. Some get added autom. based on
 using @View(navigation = REDIRECT). The same goes for
 "includeViewParams=true" and @View(viewParams = INCLUDE).
 
-
-Static Configuration via @NavigationParameter
+
+
+Static Configuration via @NavigationParameter
 
 In some cases it’s needed to add an information in any case. So you can
 annotate the view-config class with @NavigationParameter. Supported
@@ -1349,7 +1350,6 @@ them statically for particular methods:<
 }
 
 
-
 
 Dynamic Configuration via NavigationParameterContext
 
@@ -2544,7 +2544,7 @@ normal exceptions. This is possible via 
 To avoid that the same content of a form gets submitted and therefore
 processed multiple times, it’s possible to use the tag
 <ds:preventDoubleSubmit/>. As usual for DeltaSpike JSF-tags, the ds
-namespace is http://deltaspike.apache.org/jsf. Just add this tag
+namespace is http://deltaspike.apache.org/jsf. Just add this tag
 within every JSF form-tag, you would like to safeguard.
 
 

Modified: deltaspike/site/trunk/content/documentation/scheduler.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/scheduler.html?rev=1626650&r1=1626649&r2=1626650&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/scheduler.html (original)
+++ deltaspike/site/trunk/content/documentation/scheduler.html Sun Sep 21 23:48:24 2014
@@ -7,7 +7,7 @@
 
 
 
-Title: Scheduler Module
+Scheduler Module
 
 
 
@@ -166,7 +166,7 @@ body {
 		
 			
 				
-			    Title: Scheduler Module
+			    Scheduler Module
                 
 
 				
@@ -236,10 +236,10 @@ Furthermore, the request- and session-sc
 per job-execution. Therefore, the container-control module (of
 DeltaSpike) is required. That can be controlled via
 @Scheduled#startScopes (possible values: all scopes supported by the
-container-control module as well as {} for no scopes).
+container-control module as well as {} for 'no scopes').
 
 
-With false for @Scheduled#onStartup it’s even possible to
+
With 'false' for @Scheduled#onStartup it’s even possible to
 schedule/install jobs dynamically - e.g.:
 
 

Modified: deltaspike/site/trunk/content/documentation/source.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/source.html?rev=1626650&r1=1626649&r2=1626650&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/source.html (original)
+++ deltaspike/site/trunk/content/documentation/source.html Sun Sep 21 23:48:24 2014
@@ -174,7 +174,7 @@ body {
 Introduction
 SCM / Repository
 
-Initial checkout
+Initial 'checkout'
 Update existing clone
 Read-only Mirrors
 
@@ -188,7 +188,7 @@ body {
 Tools / IDE
 
 IntelliJ
-Eclipse
+Eclipse
 
 
 
@@ -209,7 +209,7 @@ repository of the project is available
 here.
 
 
-Initial checkout
+Initial 'checkout'
 
 
 git clone https://git-wip-us.apache.org/repos/asf/deltaspike.git
@@ -284,7 +284,7 @@ Settings…
 
 
 
-Eclipse
+Eclipse
 
 For Eclipse you can use this
 Code Formatter Profile. Import it via Window | Preferences | Java | Code Style | Formatter

Modified: deltaspike/site/trunk/content/documentation/spi.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/spi.html?rev=1626650&r1=1626649&r2=1626650&view=diff
==============================================================================
--- deltaspike/site/trunk/content/documentation/spi.html (original)
+++ deltaspike/site/trunk/content/documentation/spi.html Sun Sep 21 23:48:24 2014
@@ -212,7 +212,7 @@ case please also contact us
 
 To deactivate a class it’s required to implement ClassDeactivator.
-Returning false or true allows to de-/activate the class in
+Returning 'false' or 'true' allows to de-/activate the class in
 question. Retuning null means that the current class-deactivator doesn’t
 have information about the class in question and can’t provide a result.
 Since ClassDeactivator implementations are configured with the

Without existing AS7

Without existing WF8

getPropertyAwarePropertyValue()

Custom Config-Sources

Container & Control

Introduction

CdiContainer

ContextControl usage

Embedded Servlet Support

Jetty

Undertow

Tomcat

Literals

Exception Control

DeltaSpike Release Notes v1.0.3

Announcement

Highlights

Code Changes

Documentation Changes

Credits & Thanks

Full Release Notes

Bug +

Improvement +

New Feature +

Task +

Project Configuration with Maven

…​ for Apache OpenWebBeans

…​ for Apache OpenWebBeans

…​ for JBoss Weld (RI)

…​ for JBoss Weld (RI)

@TransactionScoped

Basic API usages

Basic API usages

@Folder#name

@Folder#name

Static Configuration via @NavigationParameter

Static Configuration via @NavigationParameter

Dynamic Configuration via NavigationParameterContext

Title: Scheduler Module

Scheduler Module

Initial checkout

Initial 'checkout'

Eclipse

Eclipse

… for Apache OpenWebBeans

… for Apache OpenWebBeans

… for JBoss Weld (RI)

… for JBoss Weld (RI)