You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2003/12/10 02:04:10 UTC
cvs commit: jakarta-struts INSTALL README STATUS
husted 2003/12/09 17:04:10
Modified: . INSTALL README STATUS
Log:
+ Streamline to refer to user guide
Revision Changes Path
1.8 +5 -499 jakarta-struts/INSTALL
Index: INSTALL
===================================================================
RCS file: /home/cvs/jakarta-struts/INSTALL,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- INSTALL 21 Jul 2001 06:19:14 -0000 1.7
+++ INSTALL 10 Dec 2003 01:04:10 -0000 1.8
@@ -1,11 +1,7 @@
$Id$
- Struts
- ======
-
-This document contains notes that have been accumulated on getting the Struts
-applications (documentation and example) running in a variety of servlet
-container environments.
+STRUTS
+======
For most containers, you need only to:
@@ -14,496 +10,6 @@
* In some cases, you may need to restart your container if it is running.
-Status of various containers -- as reported by volunteers on the Struts-User list.
-
-* Tomcat 3.1+ Standalone - No additonal steps required.
-* Resin 1.2+ Standalone - No additional steps required.
-* WebLogic 6.0+ - No additional steps required.
-
-* Bluestone Universal Business Server - Additional steps provided below.
-* JRUN - Additional steps provided below.
-* Orion Application Server - Additional steps provided below.
-* Tomcat 3.1+ with Apache - Additional steps provided below.
-* Weblogic 5.1 (sp8) - Additional steps provided below.
-
-* Websphere - Determination pending.
-
-
-BLUESTONE UNIVERSAL BUSINESS SERVER
------------------------------------
-
-* You need UBS version 7.2 to run war file applications. The UBS 7.2.2
- evaluation is located here:
-
- http://www.bluestone.com/SaISAPI.dll/SaServletEngine.class/products/downloads.jsp
-
-* If you're using version 7.2.1, you need to download the WAR file patch,
- located in the product enhancement section of Bluestone's website:
-
- http://www.bluestone.com/SaISAPI.dll/SaServletEngine.class/products/wfe.jsp
-
-* After installation of the correct version and/or patch of UBS 7.2, you
- need to modify your apserver.txt file to point to the correct directory
- for your war file applications. Look for the section that says something
- similar to the following:
-
- [SaServletEngine.class]
- session_affinity=1
- type=1
- program=/SaServletEngine.class
- file_path=f:\webapps
- host=localhost:20000
-
-* Use the directory specified by the "file_path" variable, or modify it
- to point to your own custom webapp directory. Copy the
- "struts-documention.war" and "struts-example.war" files into that
- webapp directory, and start the UBS (read documentation distributed
- with UBS for information on how to start it if necessary). Your webapps
- are now accessible from the following URL's:
-
- http://localhost/<PLUGIN>/SaServletEngine.class/struts-example/
- http://localhost/<PLUGIN>/SaServletEngine.class/struts-documentation/
-
-
-* "<PLUGIN>" represents the plugin you are using for your specific
- webserver. For apache on Windows, it might be "cgi-bin/SaCGI.exe",
- for IIS on Windows, it might be "scripts/SaCGI.exe" or "scripts/ISAPI.dll".
- Consult the UBS documentation for more information.
-
-
-JRUN 3.0 SP2A, VERSION 3.02A.11614
-----------------------------------
-Tested with: Microsoft IIS 5.0, Windows 2000
-
-
-Important Note:
-===============
-
-At the moment, JRun is not fully compliant with the JSP 1.1/1.2
-specification.
-
-Specifically, the automatic type conversions for custom tag parameters
-specified in "Issue 7" of the JSP 1.1 Errata and in the JSP 1.2 Proposed
-Final Draft have not yet been implemented.
-
-As it stands, JSP pages that make use of Struts taglibs whose parameters
-require conversion (such as booleans) will not compile under JRun. This
-includes the Struts Example Application. Attempting to run the example
-application will result in an exception similar to the following being
-thrown:
-
- /struts-example/index.jsp:
-
- javax.servlet.ServletException: Compilation error occured:
-
- allaire.jrun.scripting.DefaultCFE:
-
- Errors reported by compiler:
- c:/JRun/servers/default/Struts Example/WEB-INF/jsp/jrun__index2ejspa.java:41:1:41:27:
- Error: No match was found for method "setLocale(java.lang.String)".
-
-(For more details refer to:
-
-< http://www.mail-archive.com/struts-user@jakarta.apache.org/msg01860.html >)
-
-The following instructions describe how to install the Struts Example
-Application under JRun. A subsequent section describes how the Struts Example
-Application can be patched to work with Struts
-
-
-The following instructions assume the following:
-
-* JRun has been installed and integrated with the web server of choice
-
-* $APP_SERVER_NAME is the name of the application server used to host the
- application. (When JRun is first installed, it creates an application
- server called JRun Default Server)
-
-* $APP_SERVER_DIR is the directory used to hold applications hosted by
- $APP_SERVER_NAME. For the JRun Default Server, the directory is
- $JRUN_HOME/servers/default where $JRUN_HOME is the directory where
- JRun is installed.
-
-Installing The Struts Example Application
------------------------------------------
-
-* Login to the JRun Management Console.
-
-* On the left pane, select $APP_SERVER_NAME. A page showing the
- current server status will be shown on the right pane.
-
-* On the right pane, click on the WAR Deployment link. A page
- containing a list of the currently deployed web applications will be
- shown.
-
-* On the right pane, click on Deploy an Application. Complete the Web
- Application Information form as follows:
-
- o Servlet War File or Directory: Enter the full path where
- struts-example.war is found or click on Browse to select
- the path.
- o JRun Server Name: $APP_SERVER_NAME
- o Application Name: Struts Example
- o Application Hosts: All Hosts
- o Application URL: /struts-example
- o Application Deploy Directory: will default to
- $APP_SERVER_NAME/Struts Example (or the name as specified for
- Application Name)
-
-* Once the form is complete, click on the Deploy button.
-
-* If deployment is successful, restart the application server by
- clicking on $APP_SERVER_NAME on the left pane. A page showing the
- current server status will be shown on the right pane. Click the
- Restart Server button to restart the application server.
-
-* Test the sample application by using the following URL in the
- browser:
- http://hostname/struts-example/index.jsp
-
- The struts-documentation.war can be installed using the same
- procedure.
-
-
-Installing Unpacked Web Applications
-------------------------------------
-
-The above steps should be followed for applications deployed as *.war files.
-
-For unpacked web applications, configuration involves the following steps:
-
-* From the JRun Management Console, select $APP_SERVER_NAME (on the
- left pane) and click on WAR Deployment (on the right pane)
-
-* On the right pane, click on Create an Application and complete the
- Web Application Information form as follows:
-
-* JRun Server Name: $APP_SERVER_NAME
-
- o Application Name: myApplication
- o Application Hosts: All Hosts
- o Application URL: /myApplication
- o Application Deploy Directory: will default to
- $APP_SERVER_NAME/myApplication
-
-* Click on Create to submit the form.
-
-* Once the web application is created, install and configure the struts
- components (struts.jar, struts*.tld, etc) for the web application under
- $APP_SERVER_NAME/myApplication/WEB-INF
-
-* Install the remaining components of the application: .class files,
- JSP pages,.properties files etc as required.
-
-* To configure the extension mapping of the request URI (ie *.do) to
- the action servlet, expand $APP_SERVER_NAME on the left pane, expand
- the Web Applications branch and click on myApplication. The right pane
- will display the configuration options for myApplication. Click on
- Servlet URL Mappings. A list of existing mappings will be shown. Click
- the Edit button and create the following entry:
-
- o Virtual Path/Extension: *.do
- o Servlet Invoked: action
-
-* Click on the Update button to save the changes.
-* Restart the application server.
-* The application should now be accessible from the browser.
-
-The JRun application server will need to be restarted each time one of the
-following changes are made to the web application:
-
-* .class or .jar files are modified
-
-* .properties files are modified
-
-* .xml files are modified
-
-
-Patching The Struts Example Application
----------------------------------------
-
-As mentioned at the beginning of these notes, the Struts Example Application
-will not run under JRun without modification. The following changes will need
-to be made:
-
-* index.jsp, logon.jsp: Change <html:html locale="true"> to
- <html:html locale=<%= true %>>
-
-* registration.jsp, subscription.jsp: Change all instances of
- filter="true" to filter=<%= true %>
-
-
-ORION APPLICATION SERVER
-------------------------
-
-* In the steps below, $ORION_HOME refers to the directory in which you
- have installed Orion, and $STRUTS_HOME is the directory in which you
- unpacked the Struts binary distribution.
-
-* Modify the file "$ORION_HOME/config/application.xml" to define the two
- new applications, by adding the following declarations, immediately
- following the <web-module> directive for the default web application:
-
- <web-module id="strutsDoc"
- path="$STRUTS_HOME/webapps/struts-documentation.war"/>
-
- <web-module id="strutsExample"
- path="$STRUTS_HOME/webapps/struts-example.war"/>
-
-* Modify the file "$ORION_HOME/config/default-web-site.xml" (or the
- configuration file for any other Orion web site) to include the following
- declarations, after the declaration for the <default-web-app> if any:
-
- <web-app application="default" name="strutsDoc"
- root="/struts-documentation"/>
-
- <web-app application="default" name="strutsExample"
- root="/struts-example"/>
-
-* After you start Orion, you should now be able to access these applications
- (assuming you haven't changed the port number from the default of 80) at:
-
- http://localhost/struts-documentation
-
- http://localhost/struts-example
-
-* Versions of Orion up to at least 1.0.3 have a bug related to
- ServletContext.getResource() calls that prevent the Struts example
- application from working out of the box. This manifests itself as a
- JSP error when you try to access the example application, with the
- following message:
-
- javax.servlet.jsp.JspException: Missing resources attribute
- org.apache.struts.action.MESSAGE
-
- followed by an error traceback. There will also be an initialization
- error message in the "$ORION_HOME/log/global-application.log" log file.
- To work around this problem, you can take the following steps:
-
- - Go to the "$STRUTS_HOME/webapps" directory, where you will note that
- Orion has automatically expanded each web application into an
- unpacked directory structure.
-
- - Go to the "$STRUTS_HOME/webapps/struts-example/WEB-INF" directory,
- and copy the file "struts-config.xml" one directory up (that is, into
- "$STRUTS_HOME/webapps/struts-example".
-
- - Modify the "$STRUTS_HOME/webapps/struts-example/WEB-INF/web.xml" file,
- changing the value of the "config" initialization parameter (for the
- action servlet) from "/WEB-INF/struts-config.xml" to "/struts-config.xml".
-
- - Restart Orion, and you should be able to access the example application.
-
- Note that this workaround has a negative security-related side effect:
- your "struts-config.xml" file can now be retrieved by remote clients at the
- following URL:
-
- http://localhost/struts-example/struts-config.xml
-
- Therefore, you should be sure you do not store sensitive information
- (such as database passwords) in this file.
-
-
-SILVERSTREAM APPLICATION SERVER 3.7.1 AND LATER
------------------------------------------------
-
-Start the SilverStream application server.
-
-Create an XML deployment plan for the "struts-example.war" application.
-
-Call the file "struts-example-depl-plan.xml". You can use the following
-contents for the file
-
------ cut here -----
-
- <?xml version="1.0" encoding="UTF-8"?>
- <!DOCTYPE warJarOptions PUBLIC
- "-//SilverStream Software, Inc.//DTD J2EE WAR Deployment Plan//EN"
- "deploy_war.dtd">
- <warJarOptions>
- <warJar>
- <warJarName>struts-example.war</warJarName>
- <isEnabled>true</isEnabled>
- <urls><el>struts-example</el></urls>
- </warJar>
- </warJarOptions>
-
------ cut here -----
-
-Create an XML deployment plan for the "struts-documentation.war"
-application.
-
-Call the file "struts-documentation-depl-plan.xml". You can use the
-following contents for the file:
-
------ cut here -----
-
- <?xml version="1.0" encoding="UTF-8"?>
- <!DOCTYPE warJarOptions PUBLIC
- "-//SilverStream Software, Inc.//DTD J2EE WAR Deployment Plan//EN"
- "deploy_war.dtd">
- <warJarOptions>
- <warJar>
- <warJarName>struts-documentation.war</warJarName>
- <isEnabled>true</isEnabled>
- <urls><el>struts-documentation</el></urls>
- </warJar>
- </warJarOptions>
-
------ cut here -----
-
-Run the following "SilverCmd DeployWAR" commands to deploy the applications.
-You can change 'localhost' to whatever server you are deploying to. You can
-change 'Silvermaster' to whatever database you are deploying to.
-
-SilverCmd DeployWar localhost Silvermaster struts-example.war
- -f struts-example-depl-plan.xml
-SilverCmd DeployWar localhost Silvermaster struts-documentation.war
- -f struts-documentation-depl-plan.xml
-
-
-TOMCAT 3.1 (OR LATER) WITH APACHE
----------------------------------
-
-* These instructions assume you have successfully integrated
- Tomcat with Apache according to the Tomcat documentation.
-
-* Copy "struts-documentation.war" and "struts-example.war"
- to your $TOMCAT_HOME/webapps directory
-
-* Restart Tomcat if it is already running
-
-* Tomcat will generate a file "$TOMCAT_HOME/conf/tomcat-apache.conf"
- that will be used by Apache. This file is regenerated every time
- you start Tomcat, so copy this file to a safe place (such as
- your Apache configuration directory; on Unix systems this is usually
- "/usr/local/apache/conf".
-
-* If you are running Tomcat 3.1, Tomcat will not have generated the
- entries for your new applications. Add the following lines to the
- "tomcat-apache.conf" file that you have saved, replacing
- $TOMCAT_HOME with the path to your Tomcat home directory:
-
- Alias /struts-documentation "$TOMCAT_HOME/webapps/struts-documentation"
- <Directory "$TOMCAT_HOME/webapps/struts-documentation>
- Options Indexes FollowSymLinks
- </Directory>
- ApJServMount /struts-documentation/servlet /struts-documentation
- <Location "/struts-documentation/WEB-INF/">
- AllowOverride None
- deny from all
- </Location>
-
- Alias /struts-example "$TOMCAT_HOME/webapps/struts-example"
- <Directory "$TOMCAT_HOME/webapps/struts-example>
- Options Indexes FollowSymLinks
- </Directory>
- ApJServMount /struts-example/servlet /struts-example
- <Location "/struts-example/WEB-INF/">
- AllowOverride None
- deny from all
- </Location>
-
-* On all versions of Tomcat, the generated file above does not
- know anything about extension mappings defined in a web.xml file,
- so the "*.do" URIs that go to the controller servlet will not be
- recognized. To fix this, add the following line to the saved
- version of "tomcat-apache.conf", after the corresponding line
- for the .jsp extension:
-
- AddHandler jserv-servlet .do
-
-* Ensure that the saved version of "tomcat-apache.conf" is referenced
- in your Apache "httpd.conf" configuration file. A typical use would
- have the following line at the bottom of "httpd.conf":
-
- Include /usr/local/apache/conf/tomcat-apache.conf
-
-* In order to recognize "index.jsp" as a default page for web
- applications, search in your "httpd.conf" for a "DirectoryIndex"
- directive. If you have one, add "index.jsp" to the end of the
- list, so that it might look like this:
-
- DirectoryIndex index.html index.jsp
-
- If you do not have such an entry, add one like this:
-
- DirectoryIndex index.jsp
-
-* Restart Apache to make it aware of the new applications. You should
- now be able to access the applications from a browser like this:
-
- http://localhost/struts-documentation
- http://localhost/struts-example
-
-
-WEBLOGIC 5.1 (service pack 8)
------------------------------
-
-* Obtain and install the Xerces XML parser (problems have been reported
- with the Sun reference implementation). Put xerces.jar in your WebLogic system
- path.
-
-* Obtain and unpack the Struts binary distribution (this procedure assumes
- it was extracted to C:\jakarta-struts).
-
-* Add an entry to weblogic.properties for each of the Struts web
- applications that you would like to configure. For example, to make the
- struts-example application available, add the following line to
- weblogic.properties:
-
- weblogic.httpd.webApp.strutsexample=c:/jakarta-struts/webapps/struts-example.war
-
-* You do not need to include struts.jar or any of the application specific
- classes in the WebLogic classpath, since this will be done automatically
- (unless deploying an unpacked web archive- see below).
-
-* Start WebLogic server and point your web browser to the struts
- application. For example, to connect to the example application added in
- step 3:
-
- http://localhost:7001/strutsexample
-
-* This example application depends on the Struts specific resource file
- ApplicationResources.properties to be present on the classpath. However,
- WebLogic only extracts *.class files from the archive so this file will not
- be found, resulting in an error the first time it is needed- something
- similar to: javax.servlet.ServletException: runtime failure in custom tag
- 'message'. Steps 6 & 7 will need to be performed for this application, and
- any other that relies on ApplicationResources.properties.
-
-* Extract ApplicationResources.properties from the *.war file, and
- manually copy it to the respective package in the _tmp_war_ directory
- WebLogic created for this application. Again referring to the struts-example
- application, this would be:
-
- c:\jakarta-struts\webapps\WEB-INF\_tmp_war_strutsexample
-
-* Restart WebLogic. You will now be able to run the application:
-
- http://localhost:7001/strutsexample
-
-* The above steps should be followed for applications deployed as *.war
- files. For unpacked web applications, configuration involves adding both
- struts.jar and /WEB-INF/classes to the WebLogic classpath. For this reason,
- I would suggest deploying applications as war files to WebLogic. However,
- the same example application can be successfully deployed in extracted
- format by modifying weblogic.properties (assuming the war was extracted to
- directory webapps/struts-example):
-
- weblogic.httpd.webApp.strutsexample=c:/jakarta-struts/webapps/struts-example/
-
- And starting WebLogic with the updated WebLogic classpath. For example:
+For more details, and container-specific instructions, see the Installation
+chapter of the Struts User Guide.
- c:\jdk1.3\bin\java -ms16m -mx64m
- -classpath c:\weblogic\lib\weblogic510sp8boot.jar;
- c:\weblogic\classes\boot;
- c:\xerces\xerces.jar -Dweblogic.class.path=c:\weblogic\lib\weblogic510sp8.jar;
- c:\weblogic\license;
- c:\weblogic\classes;
- c:\weblogic\myserver\serverclasses;
- c:\weblogic\lib\weblogicaux.jar;
- c:\jakarta-struts\lib\struts.jar;
- c:\jakarta-struts\webapps\struts-example\WEB-INF\classes
- -Dweblogic.system.home=c:\weblogic-Djava.security.manager
- -Djava.security.policy=c:\weblogic\weblogic.policyweblogic.Server
1.18 +4 -159 jakarta-struts/README
Index: README
===================================================================
RCS file: /home/cvs/jakarta-struts/README,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- README 27 Nov 2003 23:01:22 -0000 1.17
+++ README 10 Dec 2003 01:04:10 -0000 1.18
@@ -1,7 +1,7 @@
$Id$
- Struts
- ======
+STRUTS
+======
Introduction
------------
@@ -17,160 +17,5 @@
that have HTML forms which interact with JavaBeans that are managed
automatically by the controller servlet.
-- Useful utility classes that can process XML input, as well as use Java
- reflection to populate JavaBean properties by matching names in the same
- way that the standard JSP tag
+For help with installing and using Struts, see the Struts User Guide.
- <jsp:setProperty name="beanname" property="*"/>
-
- works.
-
-
-Installing and Using Struts
----------------------------
-
-You can utilize a binary distribution of Struts in your own web applications
-by following these steps. All of these steps are required if you want to
-run the Struts application framework (including executing the example
-application). If you simply wish to use the Struts custom tag library,
-and not the MVC framework, only the steps marked (*) are required.
-
-- (*) Download and install a Java2 (version 1.2 or later) Java Development Kit
- Kit implementation for your operating system platform. Define an environment
- variable JAVA_HOME that points at the base directory of your JDK
- installation, and add the directory "$JAVA_HOME/bin" to your PATH variable.
-
-- Download and install an XML parser that is compatible with the Java
- API for XML Parsing (JAXP) 1.1 specification. A useful XML parser is the
- JAXP Reference Implementation, version 1.1 or later, that is available
- at <http://java.sun.com/xml>. Another JAXP-compatible parser that has
- been reported to work fine with Struts is Xerces, version 1.3.1,
- available at <http://xml.apache.org>. Be sure to add the "jaxp.jar" and
- "crimson.jar" (or whatever JAR file comes with your parser) files to
- your CLASSPATH environment variable.
-
-- Download and install the JDBC 2.0 Optional Package Binary (formerly known
- as the Standard Extensions package) from the Java Software web site
- <http://java.sun.com/products/jdbc>, and install the "jdbc2_0-stdext.jar"
- file on your classpath (or as a system extension).
-
-- Download and install Xalan-J, from <http://xml.apache.org/xalan-j"> (or
- use the version that came with your JAXP/1.1 download), and install
- xalan.jar in the "lib" directory of your Ant installation.
-
-- (*) Download and install a servlet container that supports the Servlet
- API Specification, version 2.2 or later, and the JavaServer Pages (JSP)
- Specification, version 1.1 or later. A useful servlet container is
- Tomcat, version 3.2 or later, that is available at
- <http://jakarta.apache.org>.
-
-- (*) Download and unpack a Struts binary distribution, available from
- <http://jakarta.apache.org/builds/jakarta-struts/nightly/>.
-
-- (*) Install the Struts documentation application by deploying file
- "lib/struts-documentation.war" into your servlet container, using the
- standard techniques supported by that container. (For Tomcat, simply
- copy this file to the $TOMCAT_HOME/webapps directory and restart Tomcat).
-
-- Install the Struts example application by deploying file
- "lib/struts-example.war" into your servlet container, using the standard
- techniques supported by that container. (For Tomcat, simply copy this
- file to the $TOMCAT_HOME/webapps directory and restart Tomcat).
-
-- (*) Copy the files "lib/struts*.tld" from the Struts distribution into the
- "WEB-INF" directory of your web application.
-
-- (*) Copy the JAR files from the "lib" directory of the Struts distribution
- (such as "struts.jar" and "commons-*.jar") into the "WEB-INF/lib" directory
- of your web application.
-
-- (*) Modify your "WEB-INF/web.xml" file to include a <servlet> element to
- define the controller servlet, and a <servlet-mapping> element to establish
- which request URIs are mapped to this servlet. Normally, you will map
- the controller servlet to a wildcard pattern ("/execute/*") or a filename
- extension pattern ("*.do"). Use the "WEB-INF/web.xml" file from the
- example application (see below) for an example of how this is done.
-
-- (*) Modify the "WEB-INF/web.xml" file for your web application to include
- a tag library declaration like this for each Struts tag library you will
- be using:
-
- <taglib>
- <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
- <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
- </taglib>
-
-- Create a file "WEB-INF/struts-config.xml" that defines the mappings for your
- requests to specific action classes. Use the "struts-config.xml" file from
- the example application (see below) as a guide.
-
-- (*) In each JSP page that will use the Struts custom tags, add a line at
- the top of the page like this (for each Struts tag library needed):
-
- <%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="struts-bean" %>
-
- (If you wish, you can use a prefix other that "struts-bean").
-
-- When compiling your web application components, be sure that the
- JAR files (copied above) are included on the CLASSPATH environment
- variable used by your Java compiler.
-
-
-The Struts Documentation Application
-------------------------------------
-
-Struts comes with a web application that contains all of the documentation
-relevant to an application developer who wants to use it, including:
-* Reference manual for the custom tag library
-* User's Guide for applications based on the framework
-* API documentation for the Struts classes
-
-To view this documentation, deploy the file "webapps/struts-documentation.war"
-into your servlet container, and use a web browser to access a URL like this:
-
- http://localhost:8080/struts-documentation
-
-For notes about installing Struts applications on various servlet containers,
-please see the INSTALL document in the same directory as this README file.
-
-
-The Struts Example Application
-------------------------------
-
-Struts comes with an example web application, which was installed into your
-servlet container if you followed the steps above. This example is the
-beginnings of a portal application that would allow users to register
-themselves, and maintain a set of subscriptions they own to mail servers
-elsewhere on the Internet. When completed, this application will provide
-the ability to read mail from various mail servers, through the application.
-
-In the absence of detailed documentation, this application can serve as a
-guide to using the interesting features of Struts. You will find the source
-code to the JSP pages associated with the example in directory "web/example",
-and the source code to the Java classes in directory "src/example". The
-source code to the Struts components themselves is in directory "src/share".
-
-To run the example application, deploy the file "webapps/struts-example.war"
-into your servlet container, and use a web browser to access a URL like this:
-
- http://localhost:8080/struts-example
-
-You can register yourself as a new user, or log on with username "user" and
-password "pass".
-
-For notes about installing Struts applications on various servlet containers,
-please see the INSTALL document in the same directory as this README file.
-
-
-Using the Struts Source Distribution
-------------------------------------
-
-If you wish to contribute to the development of the Struts toolkit, you should
-download and install a source distribution of Struts from
-<http://jakarta.apache.org/builds/jakarta-struts/nightly/src>. You will also
-need a recent nightly build of the Ant project development tool (you *must*
-use version 1.5.2 or later of Ant).
-
-Before committing any changes to the Struts CVS repository, you must do a
-"build clean" followed by a "build dist", to ensure that everything compiles
-and builds cleanly.
1.63 +2 -67 jakarta-struts/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/jakarta-struts/STATUS,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- STATUS 26 Oct 2002 00:57:28 -0000 1.62
+++ STATUS 10 Dec 2003 01:04:10 -0000 1.63
@@ -2,70 +2,5 @@
======
$Id$
+For overall project status, see the Roadmap page ("status.html") of the Struts website.
- OUTSTANDING BUGS IN STRUTS 1.1-b2 AND NIGHTLY BUILDS
- ====================================================
-
- 12 open bugs to swat!!
-
-
-This file is not actively maintained. Use this bugzilla query to see the current
-open bugs:
-
-http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time
-
-
-Controller:
-----------
-
-
-Custom Tags:
------------
- 1586 The <html:form> tag generates incorrect focus javascript for radio buttons.
-11574 Nested logic tags are brittle
-12185 HTML tags badly parsed in text/xml mode
-
-
-Documentation:
--------------
-10537 [:TODO:] sections (18)
-
-
-Example Webapps:
----------------
-
-
-File Upload:
------------
-
-
-Standard Actions:
-----------------
-
-
-Tiles Framework:
----------------
-12159 Link to tutorial incorrect
-
-
-Unknown:
--------
-
-
-Utilities:
----------
-11685 Unsafe URLEncoding in RequestUtil
-11932 (Message Resource is not multi-app aware) Multi-Resource not work in Multi-Appliction config environment
-
-
-Validator Framework:
--------------------
- 7353 Validator JavaScript Select Error
-10348 Validator is not available under sub-application
-11520 [validator-rules.xml] javascript validateRequired() function does not work with radio objects
-11950 Missing <script> in generated javascipt
-12178 Validator restricted to one Message Resource bundle.
-
-
-Web Site:
---------
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org