From dc9feca6e3cfd907b1b88683ea8481cf61a1e0e6 Mon Sep 17 00:00:00 2001 From: Magesh Umasankar Date: Sun, 3 Feb 2002 21:26:18 +0000 Subject: [PATCH] Misspelt words corrected. PR: 6203 Submitted by: cyrille_list@ingenosya.com (Cyrille Morvan) git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@271129 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/OptionalTasks/ejb.html | 36 ++++++++++---------- docs/manual/OptionalTasks/jdepend.html | 4 +-- docs/manual/OptionalTasks/propertyfile.html | 16 ++++----- docs/manual/OptionalTasks/replaceregexp.html | 8 ++--- docs/manual/OptionalTasks/sos.html | 9 +++-- 5 files changed, 38 insertions(+), 35 deletions(-) diff --git a/docs/manual/OptionalTasks/ejb.html b/docs/manual/OptionalTasks/ejb.html index c3c0ee7cf..236c80fe1 100644 --- a/docs/manual/OptionalTasks/ejb.html +++ b/docs/manual/OptionalTasks/ejb.html @@ -48,9 +48,9 @@ In general these tasks are specific to the particular vendor's EJB Server.

jboss 2.1 and above EJB servers
  • Weblogic 4.5.1, 5.1, and 6.0 EJB servers
    • -
  • JOnAS +
  • JOnAS 2.4 Open Source EJB server
    • -
  • IBM WebSphere 4.0
    • +
  • IBM WebSphere 4.0
    • Over time we expect further optional tasks to support additional EJB Servers.

    @@ -65,11 +65,11 @@ In general these tasks are specific to the particular vendor's EJB Server.

    iplanet-ejbciPlanet Application Server 6.0 ejbjarNested Elements borlandBorland Application Server 4.5 - jBossjBoss iPlanetiPlanet Application Server 6.0 + jBossjBoss + jonasJOnAS 2.4 weblogicWeblogic 5.1 & 6.0 websphereIBM WebSphere 4.0 - jonasJOnAS 2.4 wlrunWeblogic 4.5.1, 5.1 & 6.0 wlstopWeblogic 4.5.1, 5.1 & 6.0 @@ -97,7 +97,7 @@ is based on the standard Ant include and exclude selection mechanisms. dest - The directory where the serialised deployment descriptors will be written + The directory where the serialized deployment descriptors will be written Yes @@ -118,20 +118,20 @@ is based on the standard Ant include and exclude selection mechanisms.

    ejbc

    Description:

    -

    The ejbc task will run Weblogic's ejbc tool. This tool will take a serialised deployment descriptor, +

    The ejbc task will run Weblogic's ejbc tool. This tool will take a serialized deployment descriptor, examine the various EJB interfaces and bean classes and then generate the required support classes necessary to deploy the bean in a Weblogic EJB container. This will include the RMI stubs and skeletons as well as the classes which implement the bean's home and remote interfaces.

    The ant task which runs this tool is able to compile several beans in a single operation. The beans to be -compiled are selected by including their serialised deployment descriptors. The standard ant +compiled are selected by including their serialized deployment descriptors. The standard ant include and exclude constructs can be used to select the deployment descriptors to be included.

    Each descriptor is examined to determine whether the generated classes are out of date and need to be regenerated. The deployment descriptor is de-serialized to discover the home, remote and implementation classes. The corresponding source files are determined and checked to see their -modification times. These times and the modification time of the serialised descriptor itself are +modification times. These times and the modification time of the serialized descriptor itself are compared with the modification time of the generated classes. If the generated classes are not present or are out of date, the ejbc tool is run to generate new versions.

    Parameters:

    @@ -143,7 +143,7 @@ or are out of date, the ejbc tool is run to generate new versions.

    descriptors - This is the base directory from which the serialised deployment descriptors are selected. + This is the base directory from which the serialized deployment descriptors are selected. Yes @@ -165,7 +165,7 @@ or are out of date, the ejbc tool is run to generate new versions.

    classpath This classpath must include both the weblogic.ejbc class and the - classfiles of the bean, home interface, remote interface, etc of the bean being + class files of the bean, home interface, remote interface, etc of the bean being processed. No @@ -578,8 +578,8 @@ following values name of the deployment descriptor. For an Account bean, for example, the deployment descriptor would be named Account-ejb-jar.xml. Vendor specific descriptors are located using the same naming convention. The weblogic bean, for example, would be named -Account-weblogic-ejb-jar.xml. Under this arrangment, the deployment descriptors -can be separated from the code implementing the beans, which can be useful whe the same bean code +Account-weblogic-ejb-jar.xml. Under this arrangement, the deployment descriptors +can be separated from the code implementing the beans, which can be useful when the same bean code is deployed in separate beans.

    @@ -792,7 +792,7 @@ deployment element are detailed here.

    The jboss element searches for the jboss specific deployment descriptors and adds them to the final ejb jar file. Jboss has two deployment descriptors jboss.xml and jaws.xml -(for container manager persistance only). The Jboss server uses hot deployment and does +(for container manager persistence only). The Jboss server uses hot deployment and does not require compilation of additional stubs and skeletons.

    @@ -1140,7 +1140,7 @@ This will create only one TOPLink-enabled ejb jar file - 'Address.jar'.

    WebSphere element

    The websphere element searches for the websphere specific deployment descriptors and -adds them to the final ejb jar file. Websphere has two specific desriptors for session +adds them to the final ejb jar file. Websphere has two specific descriptors for session beans:

    + have occurred. @@ -1287,7 +1287,7 @@ the task will fail) and a JAR file named ejb/Account.jar will be written in the destination directory. Note that when the EJB descriptors are added to the JAR file, they are automatically renamed META-INF/ejb-jar.xml and META-INF/ias-ejb-jar.xml.

    -

    Of course, this naming behavior can be modified by specifying attributes +

    Of course, this naming behaviour can be modified by specifying attributes in the ejbjar task (for example, basejarname, basenameterminator, and flatdestdir) as well as the iplanet element (for example, suffix). Refer to the appropriate documentation for more details.

    @@ -1450,7 +1450,7 @@ up to date, and it will do the minimum amount of work required.

    ejb/Account.jar will be written in the destination directory.

    -

    Of course, this naming behavior can be modified by specifying attributes +

    Of course, this naming behaviour can be modified by specifying attributes in the ejbjar task (for example, basejarname, basenameterminator, and flatdestdir) as well as the iplanet element (for example, suffix). Refer to the appropriate documentation for more details.

    @@ -1531,7 +1531,7 @@ source files will be retained. If omitted, it defaults to "no". diff --git a/docs/manual/OptionalTasks/jdepend.html b/docs/manual/OptionalTasks/jdepend.html index 17ef1c9b8..134700add 100644 --- a/docs/manual/OptionalTasks/jdepend.html +++ b/docs/manual/OptionalTasks/jdepend.html @@ -42,7 +42,7 @@ effectively manage and control package dependencies."

    - + @@ -117,7 +117,7 @@ This invokes JDepend in a separate VM on the src and testsrc< The classpath is defined using nested elements.
    -

    Copyright © 2001 Apache Software Foundation. All rights +

    Copyright © 2001-2002 Apache Software Foundation. All rights Reserved.

    diff --git a/docs/manual/OptionalTasks/propertyfile.html b/docs/manual/OptionalTasks/propertyfile.html index e8fc857c0..edd75658b 100644 --- a/docs/manual/OptionalTasks/propertyfile.html +++ b/docs/manual/OptionalTasks/propertyfile.html @@ -56,7 +56,7 @@ are lost. Work is being done to make this task a bit more "human friendly&

    Parameters specified as nested elements

    Entry

    Use nested <entry> -elements to specify actual modifcations to the property file itself.

    +elements to specify actual modifications to the property file itself.

    alwaysrebuild This controls whether ejbdeploy is called although no changes - have occured. No, defaults to false
    secpropag Modify the RMI Skel. and Stub. to implement the implicit propagation of the security context (note that - the transactionnal context is always provided). + the transactional context is always provided). No, defaults to false.
    formatThe fomat to write the output in. The default is "text", the alternative is "xml"The format to write the output in. The default is "text", the alternative is "xml" No
    @@ -97,19 +97,19 @@ elements to specify actual modifcations to the property file itself.

    AttributeNo
    -

    The rules used when setting a property value are shown below.  The +

    The rules used when setting a property value are shown below.  The operation occurs after these rules are considered.

     

    @@ -169,7 +169,7 @@ Concatenation of strings :

    Each time called, a "." will be appended to "progress"

    -

    Copyright © 2001 Apache Software Foundation. All rights +

    Copyright © 2001-2002 Apache Software Foundation. All rights Reserved.

    \ No newline at end of file diff --git a/docs/manual/OptionalTasks/replaceregexp.html b/docs/manual/OptionalTasks/replaceregexp.html index 9f880694a..e849e0ad8 100644 --- a/docs/manual/OptionalTasks/replaceregexp.html +++ b/docs/manual/OptionalTasks/replaceregexp.html @@ -58,7 +58,7 @@ It is strongly recommended to use Jakarta Oro. replace - The substition pattern to place in the file(s) in place + The substitution pattern to place in the file(s) in place of the regular expression. Yes, if no nested <substitution> is used @@ -66,7 +66,7 @@ It is strongly recommended to use Jakarta Oro. flags The flags to use when matching the regular expression. For more information, consult the Perl5 syntax
    - g --> Global replacement. Replace all occurances found
    + g --> Global replacement. Replace all occurences found
    i --> Case Insensitive. Do not consider case in the match
    m --> Multiline. Treat the string as multiple lines of input, using "^" and "$" as the start or end of any line, respectively, rather than start or end of string.
    s --> Singleline. Treat the string as a single line of input, using "." to match any character, including a newline, which normally, it would not match.
    @@ -76,7 +76,7 @@ It is strongly recommended to use Jakarta Oro. byline Process the file(s) one line at a time, executing the replacement on one line at a time (true/false). This is useful if you - want to only replace the first occurance of a regular expression on + want to only replace the first occurence of a regular expression on each line, which is not easy to do when processing the file as a whole. Defaults to false. No @@ -103,7 +103,7 @@ value, in the file ${src}/build.properties

    This task supports a nested Substitution element to specify the substitution pattern. You can use this element to refer to a previously - defined substition pattern datatype instance.

    + defined substitution pattern datatype instance.

    <substitution id="id" pattern="expression" />
    <substitution refid="id" /> diff --git a/docs/manual/OptionalTasks/sos.html b/docs/manual/OptionalTasks/sos.html index 7c6ef1538..bca3ea05c 100644 --- a/docs/manual/OptionalTasks/sos.html +++ b/docs/manual/OptionalTasks/sos.html @@ -161,7 +161,7 @@ have been tested with Linux, Solaris & Windows2000.

    nocache - true or false - Only needed if SOSHOME is set as an enviroment variable + true or false - Only needed if SOSHOME is set as an environment variable No @@ -357,7 +357,7 @@ on the same box as the SOS server & the VSS database is at nocache - true or false - Only needed if SOSHOME is set as an enviroment variable + true or false - Only needed if SOSHOME is set as an environment variable No @@ -478,7 +478,7 @@ messages will be displayed on screen.
    nocache - true or false - Only needed if SOSHOME is set as an enviroment variable + true or false - Only needed if SOSHOME is set as an environment variable No @@ -520,5 +520,8 @@ box (server2) & the VSS database is on a share called "vss". Checks-out option was not set. Extra status messages will be displayed on screen. The soscmd(.exe) file to be used resides in /usr/local/bin.

    +
    +

    Copyright © 2002 Apache Software Foundation. All rights +Reserved.