initial version of lesson03-cdi-pe

lesson03-cdi-pe/.gitignore

@@ -0,0 +1,5 @@
+target
+.settings/*
+!.settings/.jsdtscope
+.project
+.classpath

lesson03-cdi-pe/.openshift/action_hooks/build

@@ -0,0 +1,5 @@
+#!/bin/bash
+# This is a simple build script and will be executed on your CI system if 
+# available.  Otherwise it will execute while your application is stopped
+# before the deploy step.  This script gets executed directly, so it
+# could be python, php, ruby, etc.

lesson03-cdi-pe/.openshift/action_hooks/deploy

@@ -0,0 +1,5 @@
+#!/bin/bash
+# This deploy hook gets executed after dependencies are resolved and the
+# build hook has been run but before the application has been started back
+# up again.  This script gets executed directly, so it could be python, php,
+# ruby, etc.

lesson03-cdi-pe/.openshift/action_hooks/post_deploy

@@ -0,0 +1,4 @@
+#!/bin/bash
+# This is a simple post deploy hook executed after your application 
+# is deployed and started.  This script gets executed directly, so 
+# it could be python, php, ruby, etc.

lesson03-cdi-pe/.openshift/action_hooks/post_start_jbossas-7

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.

lesson03-cdi-pe/.openshift/action_hooks/post_stop_jbossas-7

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.

lesson03-cdi-pe/.openshift/action_hooks/pre_build

@@ -0,0 +1,5 @@
+#!/bin/bash
+# This is a simple script and will be executed on your CI system if 
+# available.  Otherwise it will execute while your application is stopped
+# before the build step.  This script gets executed directly, so it
+# could be python, php, ruby, etc.

lesson03-cdi-pe/.openshift/action_hooks/pre_build_jbossas-7

@@ -0,0 +1,5 @@
+#!/bin/bash
+# This is a simple bash script and will be sourced prior to building 
+# your application. This script can be used to modify the Maven build
+# arguments for non-CI/Jenkins builds by exporting MAVEN_ARGS. The default
+# is "clean package -Popenshift -DskipTests"

lesson03-cdi-pe/.openshift/action_hooks/pre_start_jbossas-7

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.

lesson03-cdi-pe/.openshift/action_hooks/pre_stop_jbossas-7

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.

lesson03-cdi-pe/.openshift/config/modules/README

@@ -0,0 +1,18 @@
+Place your JBoss AS7 modules in this directory. This directory is added to the
+module path of the AS7 server associated with your application. It has the
+same structure as the standard AS7 modules directory.
+
+The modules placed in this directory will be added to or override the default modules
+provided by the OpenShift JBoss AS7 cartridge.
+
+Scenarios:
+1) Replace a default module with a new module that contains a bug fix or new feature
+2) Add a module that does not exist in the base OpenShift AS7 cartridge in order to add
+a new component. Typically these new modules will need to be enabled and configured in
+standalone.xml
+
+Unless one of the above scenarios is required there is no need to modify the 
+modules directory.
+
+NOTE: Replacing default modules as in scenario 1 can cause conflicts between modules so
+should be done with caution and adequate testing.