header for walkmod.xml

Author: Romain Manni-Bucau

assembly/openejb-standalone/src/main/resources/service.readme.txt

@@ -1 +1,31 @@
-Windows NT Service==================The two batch files for creating and removing OpenEJB as a Windows Service are basicallyself explanatory. Both scripts must be run using an account that has rights to installor de-install a service. This is usually an administrator account.service.install.as.admin.batservice.remove.as.admin.batIf a 'jre' or 'jdk' directory is found in an adjacent path to this 'bin' directory thenthis will be used as the preferred runtime, else the installed system runtime is used.NOTE: If you modify either of these batch files then ensure that there are no hiddencharacters after the '^' continuation symbol (such as tab or space). But always ensurethere is a space before (and not a tab). The service installer will drop further optionsand simply warn that '++JvmOptions' is unknown, leading to unexpected results.++JvmOptions=-Dopenejb.home="%openejb%" ^++JvmOptions=-Xms128M ^[tab or space] <-- Will break here, no further options will be appended++JvmOptions=-Xmx512M ^++JvmOptions=-XX:MaxPermSize=256M <-- Last line has no continuation symbolUsing the Monitor=================The file named 'OpenEJBServer.exe' can be used to modify service parameters post installation by running as an Administrator.To use the monitor feature:1. Create a shortcut to 'OpenEJBServer.exe' in your 'Startup' directory2. Right click the shortcut and select 'Properties'3. Edit the 'Target' field and append  //MS to the end of the line (Do not forget the preceding space ...\bin\OpenEJBServer.exe //MS)
+Windows NT Service
+==================
+
+The two batch files for creating and removing OpenEJB as a Windows Service are basically
+self explanatory. Both scripts must be run using an account that has rights to install
+or de-install a service. This is usually an administrator account.
+
+service.install.as.admin.bat
+service.remove.as.admin.bat
+
+If a 'jre' or 'jdk' directory is found in an adjacent path to this 'bin' directory then
+this will be used as the preferred runtime, else the installed system runtime is used.
+
+NOTE: If you modify either of these batch files then ensure that there are no hidden
+characters after the '^' continuation symbol (such as tab or space). But always ensure
+there is a space before (and not a tab). The service installer will drop further options
+and simply warn that '++JvmOptions' is unknown, leading to unexpected results.
+
+++JvmOptions=-Dopenejb.home="%openejb%" ^
+++JvmOptions=-Xms128M ^[tab or space] <-- Will break here, no further options will be appended
+++JvmOptions=-Xmx512M ^
+++JvmOptions=-XX:MaxPermSize=256M <-- Last line has no continuation symbol
+
+Using the Monitor
+=================
+The file named 'OpenEJBServer.exe' can be used to modify service parameters post installation by running as an Administrator.
+To use the monitor feature:
+
+1. Create a shortcut to 'OpenEJBServer.exe' in your 'Startup' directory
+2. Right click the shortcut and select 'Properties'
+3. Edit the 'Target' field and append  //MS to the end of the line (Do not forget the preceding space ...\bin\OpenEJBServer.exe //MS)

container/openejb-core/src/main/resources/org/apache/openejb/config/rules/Messages_hi_input.txt

@@ -50,7 +50,7 @@ The semantics of the value element are as follows:
 Just as simple as that !
 
 ###What exception would the client receive, with a timeout ?
-Quoting from the spec, "if a client-invoked business method is in progress on an instance when another client-invoked call, from the same or different client, arrives at the same instance of a stateful session bean, if the second client is a client of the beanÕs business interface or no-interface view, the concurrent invocation must result in the second client receiving a javax.ejb.ConcurrentAccessException[15]. If the EJB 2.1 client view is used, the container must throw a java.rmi.RemoteException if the second client is a remote client, or a javax.ejb.EJBException if the second client is a local client"
+Quoting from the spec, "if a client-invoked business method is in progress on an instance when another client-invoked call, from the same or different client, arrives at the same instance of a stateful session bean, if the second client is a client of the bean�s business interface or no-interface view, the concurrent invocation must result in the second client receiving a javax.ejb.ConcurrentAccessException[15]. If the EJB 2.1 client view is used, the container must throw a java.rmi.RemoteException if the second client is a remote client, or a javax.ejb.EJBException if the second client is a local client"
 
 ### No standard default
 

examples/access-timeout/README.md

@@ -1 +1,39 @@
-Windows NT Service==================The two batch files for creating and removing TomEE as a Windows Service are basicallyself explanatory. Both scripts must be run using an account that has rights to installor de-install a service. This is usually an administrator account.service.install.as.admin.batservice.remove.as.admin.batNOTE: Both scripts actually call the service.bat file, if you modify this batch file then ensure that there are no hiddencharacters after the '^' continuation symbol (such as tab or space). But always ensurethere is a space before (and not a tab). The service installer will drop further optionsand simply warn that '++JvmOptions' is unknown, leading to unexpected results.++JvmOptions=-Dcatalina.base="%CATALINA_BASE%" ^++JvmOptions=-Xms128M ^[tab or space] <-- Will break here, no further options will be appended++JvmOptions=-Xmx512M ^++JvmOptions=-XX:MaxPermSize=256M <-- Last line has no continuation symbolUsing a Defined JRE or JDK==========================The service script searches for and uses an installed Java runtime.If you want to override this feature to use a specific runtime then edit the 'service.bat' file.set "JAVA_HOME=[Full path to your JRE or JDK]"Be aware if you override the runtime that the service installer uses native 32 bit x86, 64 bit ia64 and 64 bit amd64executables to invoke the selected java runtime. For example, you cannot execute a 32 bit JRE using a 64 bit service.If this is required then you will have to override the %PROCESSOR_ARCHITECTURE% variable.Using the Monitor=================The file named 'TomEE.exe' can be used to modify service parameters post installation by running as an Administrator.To use the monitor feature:1. Create a shortcut to 'TomEE.exe' in your 'Startup' directory2. Right click the shortcut and select 'Properties'3. Edit the 'Target' field and append  //MS to the end of the line (Do not forget the preceding space ...\bin\TomEE.exe //MS)
+Windows NT Service
+==================
+
+The two batch files for creating and removing TomEE as a Windows Service are basically
+self explanatory. Both scripts must be run using an account that has rights to install
+or de-install a service. This is usually an administrator account.
+
+service.install.as.admin.bat
+service.remove.as.admin.bat
+
+NOTE: Both scripts actually call the service.bat file, if you modify this batch file then ensure that there are no hidden
+characters after the '^' continuation symbol (such as tab or space). But always ensure
+there is a space before (and not a tab). The service installer will drop further options
+and simply warn that '++JvmOptions' is unknown, leading to unexpected results.
+
+++JvmOptions=-Dcatalina.base="%CATALINA_BASE%" ^
+++JvmOptions=-Xms128M ^[tab or space] <-- Will break here, no further options will be appended
+++JvmOptions=-Xmx512M ^
+++JvmOptions=-XX:MaxPermSize=256M <-- Last line has no continuation symbol
+
+Using a Defined JRE or JDK
+==========================
+The service script searches for and uses an installed Java runtime.
+If you want to override this feature to use a specific runtime then edit the 'service.bat' file.
+
+set "JAVA_HOME=[Full path to your JRE or JDK]"
+
+Be aware if you override the runtime that the service installer uses native 32 bit x86, 64 bit ia64 and 64 bit amd64
+executables to invoke the selected java runtime. For example, you cannot execute a 32 bit JRE using a 64 bit service.
+If this is required then you will have to override the %PROCESSOR_ARCHITECTURE% variable.
+
+Using the Monitor
+=================
+The file named 'TomEE.exe' can be used to modify service parameters post installation by running as an Administrator.
+To use the monitor feature:
+
+1. Create a shortcut to 'TomEE.exe' in your 'Startup' directory
+2. Right click the shortcut and select 'Properties'
+3. Edit the 'Target' field and append  //MS to the end of the line (Do not forget the preceding space ...\bin\TomEE.exe //MS)

tomee/apache-tomee/src/main/resources/service.readme.txt

@@ -1,4 +1,20 @@
 <!DOCTYPE walkmod PUBLIC "-//WALKMOD//DTD"  "http://www.walkmod.com/dtd/walkmod-1.1.dtd" >
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
 <walkmod>
     <chain name="main-chain">
       <reader path="." >