You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by jm...@apache.org on 2003/01/09 05:12:42 UTC

cvs commit: jakarta-struts/src/share/org/apache/struts/util RequestUtils.java

jmitchell    2003/01/08 20:12:42

  Modified:    .        build.properties.sample
               doc/faqs database.xml
               src/share/org/apache/struts/util RequestUtils.java
  Log:
  Fix a couple of typos
  
  Revision  Changes    Path
  1.25      +2 -2      jakarta-struts/build.properties.sample
  
  Index: build.properties.sample
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/build.properties.sample,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- build.properties.sample	5 Jan 2003 02:48:21 -0000	1.24
  +++ build.properties.sample	9 Jan 2003 04:12:41 -0000	1.25
  @@ -30,7 +30,7 @@
   # if you are going to execute the "deploy.catalina" target.
   catalina.home=${apache.home}/jakarta-tomcat-4.0.6
   
  -# The JAR file containingthe Beanutils package (Version 1.5 or later)  
  +# The JAR file containing the Beanutils package (Version 1.5 or later)  
   # from the Jakarta Commons project.
   
   commons-beanutils.jar=${commons-lib.home}/beanutils/dist/commons-beanutils.jar
  
  
  
  1.3       +4 -4      jakarta-struts/doc/faqs/database.xml
  
  Index: database.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/doc/faqs/database.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- database.xml	29 Dec 2002 20:51:31 -0000	1.2
  +++ database.xml	9 Jan 2003 04:12:41 -0000	1.3
  @@ -61,8 +61,8 @@
       <p>
       Ideally, the business logic layer should encapsulate the data access
       details, including acquiring a database connection. 
  -    However, some application designs expect that the caller able to provide a
  -    with a database connection or DataSource instance. 
  +    However, some application designs expect that the caller be able to provide a
  +    database connection or DataSource instance. 
       When this is the case, the Struts DataSource manager can make it easy for 
       your Action to produce these resources on demand.
       </p>
  @@ -71,11 +71,11 @@
       The Struts DataSource manager is configured as an element in the
       <a href="../userGuide/configuration.html#data-source_config">
       Struts configuration file</a> (struts-config.xml). 
  -    The manager can used to deploy any connection pool that implements the
  +    The manager can be used to deploy any connection pool that implements the
       <code>javax.sql.DataSource</code> interface and is configurable totally
       from JavaBean properties. 
       If your DBMS or container provides a connection pool that meets these 
  -    requirements, then that component might your first choice.
  +    requirements, then that component might be your first choice.
       </p>
   
       <p>
  
  
  
  1.78      +5 -5      jakarta-struts/src/share/org/apache/struts/util/RequestUtils.java
  
  Index: RequestUtils.java
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/src/share/org/apache/struts/util/RequestUtils.java,v
  retrieving revision 1.77
  retrieving revision 1.78
  diff -u -r1.77 -r1.78
  --- RequestUtils.java	29 Dec 2002 21:27:32 -0000	1.77
  +++ RequestUtils.java	9 Jan 2003 04:12:42 -0000	1.78
  @@ -1667,7 +1667,7 @@
       }
   
       /**
  -     * Return the ModuleConfig object is it exists, null otherwise.
  +     * Return the ModuleConfig object if it exists, null if otherwise.
        * @param pageContext The page context.
        * @return the ModuleConfig object
        * @since 1.1b3
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>