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 2002/12/24 01:56:08 UTC
cvs commit: jakarta-struts/doc/faqs eclipse.xml kickstart.xml netbeans.xml newbie.xml
jmitchell 2002/12/23 16:56:08
Modified: doc/faqs eclipse.xml kickstart.xml netbeans.xml newbie.xml
Log:
Fix a few typos
Revision Changes Path
1.2 +4 -4 jakarta-struts/doc/faqs/eclipse.xml
Index: eclipse.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/faqs/eclipse.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- eclipse.xml 25 Nov 2002 05:25:14 -0000 1.1
+++ eclipse.xml 24 Dec 2002 00:56:08 -0000 1.2
@@ -17,7 +17,7 @@
<p>
* DISCLAIMER - This simple How-To shows you one of many ways to setup a working project using<br/>
-the Struts framewoek. This is mainly geared toward struts users who are new to Eclipse, and<br/>
+the Struts framework. This is mainly geared toward struts users who are new to Eclipse, and<br/>
don't want to spend a lot of time figuring out the differences between their old IDE (if any)<br/>
and this one.<br/>
<br/>
@@ -167,8 +167,8 @@
<li>
Compilation warnings and errors are detected immediately. In this screenshot, I drill down<br/>
into the source folder, package, file, class, and double click on the method....which <br/>
- brings up the source editor. I hover the mouse over the affending warning to see <br/>
- a description of what' wrong.<br/>
+ brings up the source editor. I hover the mouse over the offending warning to see <br/>
+ a description of what's wrong.<br/>
<img src="../images/how-to/eclipse/developing-eclipse-style14.jpg"></img><br/><br/><br/>
</li>
<li>
@@ -211,7 +211,7 @@
<img src="../images/how-to/eclipse/developing-eclipse-style27.jpg"></img><br/><br/><br/>
</li>
<li>
- Cant't forget that last one<br/>
+ Can't forget that last one<br/>
<img src="../images/how-to/eclipse/developing-eclipse-style28.jpg"></img><br/><br/><br/>
</li>
<li>
1.6 +6 -6 jakarta-struts/doc/faqs/kickstart.xml
Index: kickstart.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/faqs/kickstart.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- kickstart.xml 2 Dec 2002 00:24:16 -0000 1.5
+++ kickstart.xml 24 Dec 2002 00:56:08 -0000 1.6
@@ -114,7 +114,7 @@
<p>Why is that an important distinction? Because if you are using a servlet container on your development machine to test your application, the "struts.jar" <b>must not</b> be on your CLASSPATH environment variable when running the container. (This is because each Web application must also have their own copy of the Struts classes, and the container will become confused if it is on the environment path as well.)</p>
<p>There are several general approaches to this issue:</p>
<ul>
-<li><b>Use ANT</b> for building your projects -- it can easily assemble classpaths for the compiler. (This is how Struts itself is built, along with Tomcat and most other Java-based projects).</li>
+<li><b>Use ANT</b> for building your projects -- it can easily assemble classpaths for the compiler. (This is how Struts itself is built, along with Tomcat and most other Java-based projects).</li>
<li><b>Use an IDE</b> where you can configure the "class path" used for compilation independent of the CLASSPATH environment variable.</li>
<li><b>Use a shell script</b> that temporarily adds struts.jar to the classpath just for compilation, for example<br/>
<i>javac -classpath /path/to/struts.jar:$CLASSPATH $@</i></li>
@@ -131,7 +131,7 @@
The sources for these tests are in the "src/test"
hierarchy in the CVS repository, and are executed via the "test.junit"
target in the top-level build.xml file. Such tests are focused on the
-low-level functionality of individual methods, are are particularly
+low-level functionality of individual methods, are particularly
suitable for the static methods in the org.apache.struts.util utility
classes. In the test hierarchy, there are also some "mock object" classes
(in the org.apache.struts.mock package) so that you can package up things
@@ -204,20 +204,20 @@
<section href="turbine" name="What's the difference between Struts and Turbine? What's the difference between Struts and Expresso?">
<p>
-If you are starting fromn scratch, packages like
+If you are starting from scratch, packages like
<a href="http://jakarta.apache.org/turbine">Turbine</a> and
<a href="http://jcorporate.com">Expresso</a>
can be very helpful since they try to provide all of the basic services that your team is likely to need.
-Such services include things like data persistance and logging.
+Such services include things like data persistence and logging.
</p>
<p>
If you are not starting from scratch, and need to hook up your web application to an existing infrastructure, then "plain vanilla" Struts can be a better choice.
-The core Struts framework does not presuppose that you are using a given set of data persistance, presentation, or logging tools.
+The core Struts framework does not presuppose that you are using a given set of data persistence, presentation, or logging tools.
Anything goes =:0)
</p>
<p>
Compared to other offerings, Struts endeavors to be a minimalist framework.
-We try leverage existing technologies whenever we can and then provide only the missing pieces you need to combine disparent technologies into a coherent application.
+We try leverage existing technologies whenever we can and then provide only the missing pieces you need to combine disparate technologies into a coherent application.
This is great when you want to select your own tools to use with Struts.
But, if you prefer a more integrated infrastructure, then packages like Turbine or Expresso are perfectly good ways to go.
</p>
1.3 +4 -4 jakarta-struts/doc/faqs/netbeans.xml
Index: netbeans.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/faqs/netbeans.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- netbeans.xml 25 Nov 2002 05:25:14 -0000 1.2
+++ netbeans.xml 24 Dec 2002 00:56:08 -0000 1.3
@@ -18,7 +18,7 @@
Please read <a href="http://jakarta.apache.org/site/idedevelopers.html">this</a> first.<br/>
<p>
* DISCLAIMER - This simple How-To shows you one of many ways to setup a working project using<br/>
-the Struts framewoek. This is mainly geared toward struts users who are new to Netbeans, and<br/>
+the Struts framework. This is mainly geared toward struts users who are new to Netbeans, and<br/>
don't want to spend a lot of time figuring out the differences between their old IDE (if any)<br/>
and this one.<br/>
<br/>
@@ -52,7 +52,7 @@
directory of your project. (Actually, it doesn't matter where sits so long as you make <br/>
the appropriate changes to directories and such.)<br/>
<br/>
- *Note - I will not spend any time here trying to convice you why you should be <br/>
+ *Note - I will not spend any time here trying to convince you why you should be <br/>
using Ant to build your projects. I guess I consider this to be obvious.<br/>
Here is the build.xml file I use for this demonstration (you MUST modify this <br/>
to use your environment):<br/>
@@ -179,7 +179,7 @@
specified correctly.<br/>
</li>
<li>
- Now we can finish seting up our Netbeans project<br/><br/>
+ Now we can finish setting up our Netbeans project<br/><br/>
Mount the directory where we extracted the example and where we ran the build:<br/>
<img src="../images/how-to/netbeans/building1.jpg"></img><br/><br/><br/>
<img src="../images/how-to/netbeans/building2.jpg"></img><br/><br/><br/>
@@ -191,7 +191,7 @@
</li>
<li>
I usually get rid of the additional mounted directory under /WEB-INF/classes. <br/>
- Since everthing there gets overwritten with each build, I don't usually need to<br/>
+ Since everything there gets overwritten with each build, I don't usually need to<br/>
see this (or possibly make changes in the wrong place)<br/>
<img src="../images/how-to/netbeans/building4.jpg"></img><br/><br/><br/>
</li>
1.6 +5 -5 jakarta-struts/doc/faqs/newbie.xml
Index: newbie.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/faqs/newbie.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- newbie.xml 27 Nov 2002 14:42:19 -0000 1.5
+++ newbie.xml 24 Dec 2002 00:56:08 -0000 1.6
@@ -294,7 +294,7 @@
<section href="tags" name="Why do the Struts tags provide for so little formatting?">
<p>
-<i>The Struts tags seem to provide only the most rudimentary funcationality.
+<i>The Struts tags seem to provide only the most rudimentary functionality.
Why is there not better support for date formatting and advanced string handling?</i>
</p>
<p>
@@ -321,7 +321,7 @@
<a href="http://struts.application-servers.com">struts-layout taglib</a>.
</p>
<p>
-In the same arena, there is a well regarded contributtor taglib that can help you create
+In the same arena, there is a well regarded contributor taglib that can help you create
<a href="http://sourceforge.net/projects/struts-menu/">Menus for your Struts applications</a>.
</p>
</section>
@@ -330,7 +330,7 @@
<section href="link" name="Why does the <html:link> tag URL-encode javascript and mailto links?">
<p>
The <html:link> tag is not intended for use with client-side references like those used to launch Javascripts or email clients.
-The purpose of link tag is to interject the context (or module) path into the URI so that your server-side links are not dependant on your context (or modoule) name.
+The purpose of link tag is to interject the context (or module) path into the URI so that your server-side links are not dependant on your context (or module) name.
It also encodes the link, as needed, to maintain the client's session on the server.
Neither feature applies to client-side links, so there is no reason to use the <html:link> tag.
Simply markup the client-side links using the standard <a/> tag.
@@ -350,7 +350,7 @@
<p>
A common approach is to create an Action class for each of the business API methods/classes that you need to call.
Ideally, all the database access code should be encapsulated in the business API classes, so Struts doesn't know
-what persistent layer you are using (or even if there is a persisentance layer). It just passes a key or search
+what persistent layer you are using (or even if there is a persistence layer). It just passes a key or search
String and gets back a bean or collection of beans. This lets you use the same business API classes in other
environments, and also to run unit tests against your business API outside of Struts or a HTTP environment.
</p>
@@ -359,7 +359,7 @@
your business API. As you gain experience, you will find ways to combine your Actions, say by using the
DispatchAction. It's even possible to use a single "framework" Action to call all of your business
classes, as is done with Scaffold ProcessAction in the contrib folder. Using fewer Actions does require
-a deeper understanding of how Struts and MVC frameworks operate. Don't hestitate to err on the side
+a deeper understanding of how Struts and MVC frameworks operate. Don't hesitate to err on the side
of creating more Actions at first. The Struts configuration makes it easy to refactor your Actions
later, since you can change the Action type without changing anything else in the application.
</p>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>