dims 01/07/18 04:11:39
Modified: xdocs actions.txt actions.xml caching.xml contrib.xml
datasources.xml directory-generator.xml
emotional-landscapes.xml esql.xml extending.xml
faq.xml httprequest.xml i18n-transformer.xml
imagedirectory-generator.xml installing.xml
jars.xml log-transformer.xml
logicsheet-concepts.xml logicsheet-forms.xml
matchers_selectors.xml patches.xml sessions.xml
sitemap.xml sql-transformer.xml uc2.xml
xslt-transformer.xml xsp-internals.xml
Log:
Document spelling corrections patches from John Morrison.
Revision Changes Path
1.3 +10 -10 xml-cocoon2/xdocs/actions.txt
Index: actions.txt
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/actions.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- actions.txt 2001/06/21 13:10:33 1.2
+++ actions.txt 2001/07/18 11:11:38 1.3
@@ -1,6 +1,6 @@
WARNING: This material is subject to change at anytime and may
never find a way into the main distribution. It could
-be removed if it has proven not to be usefull for Cocoon 2.
+be removed if it has proven not to be useful for Cocoon 2.
This is a proposal for a Action sitemap component. For more
information look at the javadoc comments in the file Action.java
@@ -45,7 +45,7 @@
> > </when>
> > <otherwise>
> > <generate src="myapp/{1}/index.xml"/>
-> > </otehrwise>
+> > </otherwise>
> > </select>
> > <select type="browser">
> > <when test="netscape">
@@ -93,7 +93,7 @@
component in the sitemap so far. Generally speaking I think a Sitemap
Action is an object that acts upon an application model based on data
supplied by the environments objectModel (ie Request). It's its
-responsability to make some data available to the Sitemap engine as
+responsibility to make some data available to the Sitemap engine as
further selection/matching criteria (a List object) as well as in the
objectModel for other sitemap components
@@ -142,14 +142,14 @@
someone will do it with a sitemap component :/
Authorisation is more dependant on the application context and there are
the possibilities to use AuthorisationMatchers, AuthorisationSelectors,
-AuthorisationActions or a authorisation logicsheeet, what ever suit your
+AuthorisationActions or a authorisation logicsheet, what ever suit your
needs best.
> What about form validation ?
Even here, it depends. If you only want to validate form data a Selector
can be used to achieve that and in the <map:when> elements you
-regenerate the resource if validation failes or choose an action to put
+regenerate the resource if validation fails or choose an action to put
the form data into your application model and generate the next screen
or whatever.
@@ -203,7 +203,7 @@
> NoEntry.html type page.
> ...
>
-> So when I designe a sitemap for a web-application I want to somehow be able
+> So when I design a sitemap for a web-application I want to somehow be able
> to do the following.
>
> * Anything under webapp/ must run SessionValidatorAction
@@ -211,12 +211,12 @@
> "admin" role
> * Then specific resources webapp/a.xml, webapp/b.xml and webapp/admin/c.xml
> must run FormValidationAction with appropriate form schema and the
-> apprporiate FormDBEntryAction
+> appropriate FormDBEntryAction
Didn't get the last one? What is a FormDBEntryAction for? Probably an
XSP page?
-> * A user can also arbitarily submit an action from any page (via post
+> * A user can also arbitrarily submit an action from any page (via post
> request or perhaps a ?action=blah tacked onto URL) that must be executed.
<match type="uri" pattern="webapp/**">
@@ -263,7 +263,7 @@
>
> So what would I want to see in a Cocoon-Application framework ???
>
-> Well actions are independent of resources and exist in a seperate
namespace.
+> Well actions are independent of resources and exist in a separate
namespace.
>
> Each request can in theory result in a action-pipeline.
>
@@ -288,7 +288,7 @@
> to C2 and I suspect many others would too :P.
Implementing the framework to use actions like I've mentioned through
-out this mail is a matter of an hour or two. But your're right
+out this mail is a matter of an hour or two. But you're right
implementing general actions for general usage is another thing.
Giacomo
1.5 +7 -7 xml-cocoon2/xdocs/actions.xml
Index: actions.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/actions.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- actions.xml 2001/07/17 12:31:29 1.4
+++ actions.xml 2001/07/18 11:11:38 1.5
@@ -21,7 +21,7 @@
at run time, we surmised that sometimes we need to adjust the pipeline
based on runtime parameters, or even the contents of the Request
parameter.
Without the use of Actions this would make the sitemap almost
- incomprehensable.
+ incomprehensible.
</p>
<p>
The quick and dirty definition of an Action is "a Sitemap Component that
@@ -77,7 +77,7 @@
<p>
The alternative is to use Actions. Actions handle the pure logic
handling portions of your site. This allows you to create each page
- in the multiplage form to handle any logic it needs to for display
+ in the multipage form to handle any logic it needs to for display
purposes only. Your form handling information is kept separate, and
can even predictably change the pipeline used in the sitemap.
</p>
@@ -162,7 +162,7 @@
</source>
<p>
Using this approach, we will generate the file named
"hello_world.xsp"
- because the value of the Sitemap paramter "{world}" is "hello".
Also,
+ because the value of the Sitemap parameter "{world}" is "hello".
Also,
the file "hello_world.xsp" can use the request parameter "hello" to
produce the value "world".
</p>
@@ -183,7 +183,7 @@
<source>
<![CDATA[
<map:match pattern="file">
- <map:act type="hello-world" src="optinal src">
+ <map:act type="hello-world" src="optional src">
<!-- and here come the parameters: -->
<map:parameter name="first parameter" value="test"/>
@@ -208,10 +208,10 @@
You can arrange actions in an action set. The sitemap calls the
act method of those actions in the sequence they are defined in the
action set. It is possible to signal to the sitemap to
- call an antion only if the Environments getAction method returns
+ call an action only if the Environments getAction method returns
a String identical to the value supplied with an action attribute.
In the current implementation of the HttpEnvironment the value
- returned by the getAction methos is determined by a http parameter
+ returned by the getAction method is determined by a http parameter
called "cocoon-action". So far let's have a look at at possible
action set definition:
</p>
@@ -273,7 +273,7 @@
</p>
<p>
However, one is not limited to specify distinct values at the action
attribute.
-It is possible and I think usefull to mark several actions with the same
+It is possible and I think useful to mark several actions with the same
action attribute value which will then be called in sequence. This allows you
to choose a granularity of your actions at will.
</p>
1.8 +5 -5 xml-cocoon2/xdocs/caching.xml
Index: caching.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/caching.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- caching.xml 2001/07/02 09:03:36 1.7
+++ caching.xml 2001/07/18 11:11:38 1.8
@@ -27,7 +27,7 @@
For more information about configuration see the chapter
below.</p>
<p>The following subchapters describe the available caching
algorithms.</p>
<s2 title="The CachingEventPipeline">
- <p>The CachingEventPipelineuses a very easy but
effectiv approach
+ <p>The CachingEventPipelineuses a very easy but
effective approach
to cache the event pipelines of a request: The pipeline
process
is cached up to the most possible point.</p>
<p>Each sitemap component (generator or transformer) which
might be
@@ -73,7 +73,7 @@
<s3 title="Examples">
<p>If you have the following pipeline:</p>
<p>Generator[type=file|src=a.xml]->Transformer[type="xslt"|src=a.xsl]->Serializer</p>
- <p>The file generator is cacheable and
generates a key which hashesthe src
+ <p>The file generator is cacheable and
generates a key which hashes the src
(or the filename) to build the key. The cache
validity object uses the last modification date
of the xml file.</p>
<p>The xslt transformer is cacheable and
generates a key which hashes
@@ -86,7 +86,7 @@
the serializer.</p>
<p>Only part of the following pipeline is
cached:</p>
<p>Generator[type=file|src=a.xml]->Transformer[type="xslt"|src=a.xsl]->Transformer[type=sql]->Transformer[type="xslt"|src=b.xsl]->Serializer</p>
- <p>The file generator is cacheable and
generates a key which hashesthe src
+ <p>The file generator is cacheable and
generates a key which hashes the src
(or the filename) to build the key. The cache
validity object uses the last modification date
of the xml file.</p>
<p>The xslt transformer is cacheable and
generates a key which hashes
@@ -129,7 +129,7 @@
For more information about configuration see the chapter
below.</p>
<p>The following subchapters describe the available caching
algorithms.</p>
<s2 title="The CachingStreamPipeline">
- <p>The <code>CachingStreamPipeline</code> uses a very
easy but effectiv approach
+ <p>The <code>CachingStreamPipeline</code> uses a very
easy but effective approach
to cache the stream pipelines of a request: If the
underlying
event stream and the serializer is cacheable the
request is cached.
If a reader is used instead and it is cacheable, the
response
@@ -151,7 +151,7 @@
simple as a serializer often has no other input than
the sax events. In
this case the key for this serializer can be a simple
constant value
and the validity object is the
<code>NOPCacheValidity</code>.</p>
- <p>A reader is cacheable if it imimplements the
<code>Cacheable</code>
+ <p>A reader is cacheable if it implements the
<code>Cacheable</code>
interface.</p>
<p>When a response is cached all validity objects are
stored together with
the cached response, which is actually a byte array, in
the cache.
1.3 +3 -3 xml-cocoon2/xdocs/contrib.xml
Index: contrib.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/contrib.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- contrib.xml 2001/06/08 10:54:24 1.2
+++ contrib.xml 2001/07/18 11:11:38 1.3
@@ -64,7 +64,7 @@
having too many questioners and not enough experts to respond to all the
questions.</li>
<li>Testing Cocoon (especially its less-frequently-used features) on
various configurations
and reporting back.</li>
- <li>Debugging - producing reproducable test cases and/or finding causes
of bugs (at the time of
+ <li>Debugging - producing reproduceable test cases and/or finding causes
of bugs (at the time of
writing, some known bugs are informally listed on <connect
href="todo.xml">To Do</connect>, but
eventually a bug database should be made available on the Apache
site).</li>
<li>Specifying/analysing/designing new features for Cocoon 2 - and
beyond. (If you wish to get involved
@@ -145,7 +145,7 @@
</ul>
<p>And obviously, it should be tested against the current CVS snapshot of
Cocoon!</p>
- <p>This testing is designed to iron out the most common kinds of
incompatibilty
+ <p>This testing is designed to iron out the most common kinds of
incompatibility
problems (Servlet >2.0 requirements; platform-dependent assumptions; JDK
>1.1 code).
These requirements are, of course, open to review and discussion. Note
that
the contributor is not required to do the testing - indeed it is
probably better
@@ -165,7 +165,7 @@
</s2>
<s2 title="Licensing Requirements for the Cocoon Distribution">
- <p>To avoid legal problems, the Apache Project Management Committe (PMC)
have agreed on
+ <p>To avoid legal problems, the Apache Project Management Committee (PMC)
have agreed on
a policy for under what licensing code can be accepted into Apache
projects:</p>
<ul>
<li>Source code files must be under the Apache license and must have
copyright assigned to
1.2 +2 -2 xml-cocoon2/xdocs/datasources.xml
Index: datasources.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/datasources.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- datasources.xml 2001/05/09 20:50:24 1.1
+++ datasources.xml 2001/07/18 11:11:38 1.2
@@ -19,7 +19,7 @@
</p>
<s2 title="Installing the Driver">
<p>
- Independant of how you choose to get and maintain your JDBC
connections,
+ Independent of how you choose to get and maintain your JDBC
connections,
you have to load the driver so Cocoon can use it (unless you are using
a J2EE container--more on that later). This is an init parameter in
your web.xml file. The following snippet will show you how:
@@ -51,7 +51,7 @@
connection. The JDBC data source lets Cocoon handle all the pooling
logic. The J2EE data source tells Cocoon how to pull the DataSource
object from a J2EE container (thats Java 2 Enterprise Edition)--the
- major caviat is that Cocoon must be installed as part of a Enterprise
+ major caveat is that Cocoon must be installed as part of a Enterprise
Application.
</p>
<p>
1.5 +1 -1 xml-cocoon2/xdocs/directory-generator.xml
Index: directory-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/directory-generator.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- directory-generator.xml 2001/07/16 14:42:29 1.4
+++ directory-generator.xml 2001/07/18 11:11:38 1.5
@@ -40,7 +40,7 @@
</source>
</s1>
<s1 title="Configuration">
-<p>The following parmeter can be specified in the pipeline for
+<p>The following parameter can be specified in the pipeline for
the generate command:</p>
<ul>
<li>depth (optional) : Sets how deep Directory Generator should delve into
the
1.2 +7 -7 xml-cocoon2/xdocs/emotional-landscapes.xml
Index: emotional-landscapes.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/emotional-landscapes.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- emotional-landscapes.xml 2001/05/09 20:50:22 1.1
+++ emotional-landscapes.xml 2001/07/18 11:11:38 1.2
@@ -44,7 +44,7 @@
I'll explain you what the Apache Cocoon project is about and what we are
doing to solve the problems that we encountered in our web engineering
experiences, but from an executive perspective, yes, because we all had
-the problems of managing a web site, dealing with our colleages, rushing
+the problems of managing a web site, dealing with our colleagues, rushing
to the graphical guru to have the little GIF with the new title, or
calling the web administrator at night because the database is returning
errors without reasons.
@@ -54,7 +54,7 @@
I was frustrated of seeing the best and most clever information
technology ever invented (the web) ruined by the lack of engineering
practices, tortured by those "let's-reinvent-the-wheel-once-again"
-craftmen that were great at doing their jobs as inviduals but that
+craftmen that were great at doing their jobs as individuals but that
couldn't scale and imposed a growth saturation to the whole project.
</p>
@@ -218,7 +218,7 @@
<p>
tell me, who wrote the page? You could guess by comparing the structure,
-but how do you know the two stuctures reflect the same semantic
+but how do you know the two structures reflect the same semantic
information?
</p>
@@ -326,7 +326,7 @@
<p>
that allowed me to write my pages in XML, create my "graphics" as
-tranformation rules and generate HTML pages on the fly directly from my
+transformation rules and generate HTML pages on the fly directly from my
web server.
</p>
@@ -350,7 +350,7 @@
<p>
Anything without changing the basic architecture that is simply based on
-the simple "angle braket" XML syntax.
+the simple "angle bracket" XML syntax.
</p>
</s1>
@@ -377,7 +377,7 @@
It can be observed that separating people with common skills in
different working groups increases productivity and reduces management
costs, but only if the groups do not overlap and have clear "contracts"
-that define their operativity and their concerns.
+that define their operability and their concerns.
</p>
<p>
@@ -672,7 +672,7 @@
</p>
<p>
-Resource views are a particular type of HTTP variants, but targetted for
+Resource views are a particular type of HTTP variants, but targeted for
the yet-to-be-possible semantic indexing of content.
</p>
1.4 +3 -3 xml-cocoon2/xdocs/esql.xml
Index: esql.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/esql.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- esql.xml 2001/07/09 12:47:04 1.3
+++ esql.xml 2001/07/18 11:11:38 1.4
@@ -137,7 +137,7 @@
<td>returns the value of the given column as a clob</td>
</tr>
<tr><td>esql:row-results//esql:get-xml</td>
- <td>returns the value of the given column interpeted as an xml
fragment.
+ <td>returns the value of the given column interpreted as an xml
fragment.
The fragment is parsed by the default xsp parser and the document element
is returned.
If a root attribute exists, its value is taken to be the name of an element
to wrap around the contents of
the fragment before parsing.</td>
@@ -149,10 +149,10 @@
<td>returns the position of the current row in the result set</td>
</tr>
<tr><td>esql:row-results//esql:get-column-name</td>
- <td>returns the name of the given column. the column mus tbe
specified by number, not name.</td>
+ <td>returns the name of the given column. the column must be
specified by number, not name.</td>
</tr>
<tr><td>esql:row-results//esql:get-column-label</td>
- <td>returns the label of the given column. the column mus tbe
specified by number, not name.</td>
+ <td>returns the label of the given column. the column must be
specified by number, not name.</td>
</tr>
<tr><td>esql:row-results//esql:get-column-type-name</td>
<td>returns the name of the type of the given column. the column
must be specified by number, not name.</td>
1.2 +5 -5 xml-cocoon2/xdocs/extending.xml
Index: extending.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/extending.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- extending.xml 2001/05/09 20:50:22 1.1
+++ extending.xml 2001/07/18 11:11:38 1.2
@@ -26,7 +26,7 @@
<p>You may want to write a <code>Generator</code> if
you want some other
basis for your SAX events (maybe you want a SAX event every
time the
temperature of your CPU changes?) However, before writing a
- <code>Generator</code> from scratch, it may be worthwile to
have a look at
+ <code>Generator</code> from scratch, it may be worthwhile to
have a look at
<link href="#xsp">XSP</link>, which can create a
<code>Generator</code> for
you.</p>
<p>Existing <code>Generator</code>s are: </p>
@@ -45,11 +45,11 @@
DirectoryGenerators that adds extra attributes for
image files. </li>
<li>
<code>PhpGenerator</code> - Allows PHP
to be used as a generator.
- Builds upon the PHP servlet functionallity. Overrides
the output method in
+ Builds upon the PHP servlet functionality. Overrides
the output method in
order to pipe the results into SAX events.</li>
<li>
<code>RequestGenerator</code> - [FIXME:
This looks like just
- outputting the request headers, the request parameters
and the configuration
+ outputing the request headers, the request parameters
and the configuration
parameters. But I don't see any use of it (besides
debugging and
demonstration). Are there other situations in which
you might want to use
this?]</li>
@@ -97,7 +97,7 @@
<ul>
<li>
<code>LogTransformer</code> - This is a
class that can be plugged
- into a pipeline to print the SAX events which passes
thru this
+ into a pipeline to print the SAX events which passes
through this
<code>Transformer</code> in a readable form to a file.
This
<code>Transformer</code>'s main purpose is
debugging.</li>
<li>
@@ -165,7 +165,7 @@
</ul>
</s1>
<s1 title="About Action">
- <p>[FIXME: We have to wait until we can see what is
going to happen here. Also, I wonder if this belongs here or should deserve a
seperate page.]</p>
+ <p>[FIXME: We have to wait until we can see what is
going to happen here. Also, I wonder if this belongs here or should deserve a
separate page.]</p>
<p>The Action part will be used for making Cocoon able
to react on form input. This will make Cocoon no longer a simple basis for web
publishing, but will make it apt for web interaction as well.</p>
</s1>
<s1 title="About XSP">
1.5 +1 -1 xml-cocoon2/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq.xml 2001/07/17 21:34:23 1.4
+++ faq.xml 2001/07/18 11:11:38 1.5
@@ -163,7 +163,7 @@
<answer>
<p>
This is another neat feature from DOS- times.
- To increase enviroment-space add the following line to your
+ To increase environment-space add the following line to your
config.sys (and restart):
shell=c:\command.com /E:4096 /P
</p>
1.3 +1 -1 xml-cocoon2/xdocs/httprequest.xml
Index: httprequest.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/httprequest.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- httprequest.xml 2001/05/23 12:32:22 1.2
+++ httprequest.xml 2001/07/18 11:11:38 1.3
@@ -353,7 +353,7 @@
<s2 title="JavaLanguage">
<p><code>org.apache.cocoon.components.language.programming.java.JavaLanguage</code></p>
- <p>This takes care for outputting Java code as source of the
sitemap
+ <p>This takes care for outputing Java code as source of the
sitemap
class.</p>
</s2>
<s2 title="ResourcePipeline">
1.3 +3 -3 xml-cocoon2/xdocs/i18n-transformer.xml
Index: i18n-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/i18n-transformer.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- i18n-transformer.xml 2001/07/13 09:56:31 1.2
+++ i18n-transformer.xml 2001/07/18 11:11:38 1.3
@@ -63,7 +63,7 @@
</para>]]></source>
<p>
Text inside the
<code><![CDATA[<i18n:text>]]></code> will be used as a key to find the
- translation in the dictionary. All
attributes that are listed in the <code><![CDATA[<i18n:attr>]]></code>
attribute also will be translated and their values will be used as dicionary
keys.
+ translation in the dictionary. All
attributes that are listed in the <code><![CDATA[<i18n:attr>]]></code>
attribute also will be translated and their values will be used as dictionary
keys.
</p>
<note>
This i18n approach was re-designed to
implement i18n of dates, currencies, etc.
@@ -300,13 +300,13 @@
</s1>
<s1 title="Usage Pattern for Dictionary Generator Stylesheet">
<p>
- Desciption is given for a real world example:
+ Description is given for a real world example:
To correct/add Spanish translation in/to an existing dictionary:
</p>
<s2 title="Key generation">
<p>
Generate a dictionary with keys and placeholders for Spanish
translations.
- Optionaly, for one of the languages existing translations can be
kept.
+ Optionally, for one of the languages existing translations can
be kept.
To do it set stylesheet params (manually in stylesheet or in
command-line):
mode = keys (indicates, that only keys must be in
result)
new-lang = es (language to be added)
1.4 +1 -1 xml-cocoon2/xdocs/imagedirectory-generator.xml
Index: imagedirectory-generator.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/imagedirectory-generator.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- imagedirectory-generator.xml 2001/07/16 14:42:29 1.3
+++ imagedirectory-generator.xml 2001/07/18 11:11:38 1.4
@@ -45,7 +45,7 @@
</source>
</s1>
<s1 title="Configuration">
-<p>The following parmeter can be specified in the pipeline for
+<p>The following parameter can be specified in the pipeline for
the generate command:</p>
<ul>
<li>depth (optional) : Sets how deep Image Directory Generator should delve
into the
1.12 +6 -6 xml-cocoon2/xdocs/installing.xml
Index: installing.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/installing.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- installing.xml 2001/07/16 06:36:26 1.11
+++ installing.xml 2001/07/18 11:11:38 1.12
@@ -55,7 +55,7 @@
<li>In "Authentication:" choose ""passwd" file on the cvs
server";</li>
<li>Click "Ok";</li>
<li>Click admin->login;</li>
- <li> When asked for the password: anwer "anoncvs" (without
quotes);</li>
+ <li> When asked for the password: answer "anoncvs" (without
quotes);</li>
<li> Click "create->checkout module";</li>
<li>Module name and path on the server is "xml-cocoon2" (no
quotes);</li>
<li>Choose a dir to put the source code in;</li>
@@ -64,17 +64,17 @@
window;</li>
<li>Wait until you see "*****CVS exited normally with code 0*****"
in the
log window;</li>
- <li>The Cocoon2 source is now on your HD.</li>
+ <li>The Cocoon2 source is now on your harddrive.</li>
</ol>
</s2>
<s2 title="Step-by-step instructions for Unix">
<ol>
<li>Start the shell of your choice.</li>
<li>Enter "cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
login".</li>
- <li>When asked for the password: anwer "anoncvs".</li>
+ <li>When asked for the password: answer "anoncvs".</li>
<li>Enter "cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic -z3
checkout xml-cocoon2". This will create a directory called "xml-cocoon2" where
the Cocoon2 source will be stored.</li>
<li>Wait until cvs has finished.</li>
- <li>The Cocoon2 source is now on your HD.</li>
+ <li>The Cocoon2 source is now on your harddrive.</li>
</ol>
<p>In case you want to update your Cocoon2 source tree to the
current version, change to the "xml-cocoon2" directory and
@@ -84,9 +84,9 @@
<s1 title="Building Cocoon2">
- <s2 title="Set JAVA_HOME enviornment variable">
+ <s2 title="Set JAVA_HOME environment variable">
- <p>Set the JAVA_HOME enviornment variable to point to the root
directory of
+ <p>Set the JAVA_HOME environment variable to point to the root
directory of
the Java Development Kit installed on your machine. To do this simply
type:</p>
<source>
1.6 +1 -1 xml-cocoon2/xdocs/jars.xml
Index: jars.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/jars.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- jars.xml 2001/07/18 09:30:44 1.5
+++ jars.xml 2001/07/18 11:11:38 1.6
@@ -238,7 +238,7 @@
<td>XTTransformer transformer</td>
<td/>
<td>? why have xt <strong>and</strong> xalan. Has this not been
- superseeded by the TraxTransformer ?</td>
+ superseded by the TraxTransformer ?</td>
</tr>
</table>
</s1>
1.4 +1 -1 xml-cocoon2/xdocs/log-transformer.xml
Index: log-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/log-transformer.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- log-transformer.xml 2001/07/17 14:47:20 1.3
+++ log-transformer.xml 2001/07/18 11:11:38 1.4
@@ -15,7 +15,7 @@
<s1 title="Log Transformer">
<p>This transformations main purpose is debugging.
The <code>LogTransformer</code> is a class that can be plugged into a
pipeline
-to print the SAX events which passes thru this transformer in a readable form
+to print the SAX events which passes though this transformer in a readable
form
to a file.</p>
<p>
The file will be specified in a parameter tag in the sitemap pipeline to the
1.2 +4 -4 xml-cocoon2/xdocs/logicsheet-concepts.xml
Index: logicsheet-concepts.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/logicsheet-concepts.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- logicsheet-concepts.xml 2001/05/09 20:50:23 1.1
+++ logicsheet-concepts.xml 2001/07/18 11:11:38 1.2
@@ -158,7 +158,7 @@
<p>
This means that logicsheets must be able to cope with constant
- strings, compex expressions and nested parameter processing.
+ strings, complex expressions and nested parameter processing.
Also, logicsheets must be capable of reporting parameter value
errors and, possibly, halt code generation altogether.
</p>
@@ -201,7 +201,7 @@
<p>
A brute-force logicsheet template may be implemented
- (in XSLT, as discused <jump anchor="xsl-logicsheets">below</jump>)
+ (in XSLT, as discussed <jump anchor="xsl-logicsheets">below</jump>)
as:
</p>
@@ -303,7 +303,7 @@
multiple versions of the same logicsheet
</li>
<li>
- Simpler debugging: syntax errors can niow be traced to bad
+ Simpler debugging: syntax errors can now be traced to bad
parameter values, rather than invalid code
</li>
<li>
@@ -470,7 +470,7 @@
<p>
XSLT provides all the capabilities needed for dynamic markup
- transformation as well for final code generation (descibed
+ transformation as well for final code generation (described
in
<jump href="xsp-internals.html" anchor="logicsheet-generator">
Logicsheet Code Generators
1.4 +3 -3 xml-cocoon2/xdocs/logicsheet-forms.xml
Index: logicsheet-forms.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/logicsheet-forms.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- logicsheet-forms.xml 2001/07/11 08:33:45 1.3
+++ logicsheet-forms.xml 2001/07/18 11:11:38 1.4
@@ -31,7 +31,7 @@
<s2 title="The Descriptor File">
<p>
For details on the syntax of the descriptor file see
- javadocs. Basically it constists of two sections, a list of
+ javadocs. Basically it consists of two sections, a list of
parameters and their properties and a list of constraints or
constraint sets. The file syntax is set up so that it can be
shared with the database actions.
@@ -55,8 +55,8 @@
]]>
</source>
<p>
- The aboce could for example describe expected input from a reservation
- form. Specifications in a constraint set take preceedence over
+ The above could for example describe expected input from a reservation
+ form. Specifications in a constraint set take precedence over
the general ones.
</p>
</s2>
1.2 +1 -1 xml-cocoon2/xdocs/matchers_selectors.xml
Index: matchers_selectors.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/matchers_selectors.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- matchers_selectors.xml 2001/07/11 08:32:43 1.1
+++ matchers_selectors.xml 2001/07/18 11:11:38 1.2
@@ -97,7 +97,7 @@
Actions should be used to <em>"do"</em> something, not to chose
between different sub pipelines. That should be done only, if an error
occurred and you cannot continue the regular pipeline. Of course this
-is a fuzzy criterion and using an action to chose between exacty two
+is a fuzzy criterion and using an action to chose between exactly two
sub pipelines is a very common task i.e. for authentication. Also,
often actions have no nested elements and the further processing is
not affected by the result of the action. </p>
1.3 +1 -1 xml-cocoon2/xdocs/patches.xml
Index: patches.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/patches.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- patches.xml 2001/06/08 10:54:41 1.2
+++ patches.xml 2001/07/18 11:11:38 1.3
@@ -20,7 +20,7 @@
to the <link href="mailto:[email protected]";>cocoon-dev</link>
mailing list.
These patches are not (yet) part of the Cocoon project, but need
reviewing for possible
inclusion. This system was instituted because, due to the large volume of
mail and
- the lack of time of the committers, some patches tended to get forgetten
about. This
+ the lack of time of the committers, some patches tended to get forgotten
about. This
queue does not guarantee that any patch will be reviewed within a
reasonable time frame,
but it does at least make them easier to find!
</p>
1.3 +2 -2 xml-cocoon2/xdocs/sessions.xml
Index: sessions.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/sessions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sessions.xml 2001/05/23 12:32:22 1.2
+++ sessions.xml 2001/07/18 11:11:38 1.3
@@ -17,7 +17,7 @@
because HTTP and related protocols are stateless,
but sometimes we need stateful information about visitors of a Cocoon
site.
For a more precise analysis of a web site, the tracking of visitors
- should work independant of the visitor's browser and of the visitor's
decision
+ should work independent of the visitor's browser and of the visitor's
decision
whether we enabled cookies or not. Last not least, Cocoon 2 should not
be dependant of the method the servlet engine prefers to generate
session IDs.
In this document, it is described step by step what has to be done to
enable
@@ -50,7 +50,7 @@
<ul>
<li>creation of new session IDs</li>
<li>full session control by the underlying Servlet API 2.2
servlet engine</li>
- <li>cookie- and URI-based session managment</li>
+ <li>cookie- and URI-based session management</li>
<li>automatic link rewrite if you like your XSP pages to be
URI-session-aware</li>
</ul>
</s2>
1.4 +9 -9 xml-cocoon2/xdocs/sitemap.xml
Index: sitemap.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/sitemap.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sitemap.xml 2001/07/13 09:56:54 1.3
+++ sitemap.xml 2001/07/18 11:11:38 1.4
@@ -73,10 +73,10 @@
resource authorisation) should be provided.</li>
<li>sitemaps should not limit Cocoon's intrinsic modular
extensibility.</li>
<li>resources must be matched with all possible state variables, not
- only with URI (http parameters, enviornment variables, server
+ only with URI (http parameters, environment variables, server
parameters, time, etc...).</li>
<li>sitemaps should embed the notion of "semantic resources" to be
- future-compatible with sematic crawling and indexing.</li>
+ future-compatible with semantic crawling and indexing.</li>
<li>sitemaps should be flexible enough to allow a complete web site to
be built with Cocoon.</li>
</ol>
@@ -396,7 +396,7 @@
as nodes and leaves.
</p>
<p>The subsitemaps serve two important goals: scalability and
- simplification of maintainance. The different subsitemaps are indepent
+ simplification of maintainance. The different subsitemaps are
independent
and don't affect each other.
</p>
<source>
@@ -431,10 +431,10 @@
Usually you use the same SitemapComponents over and over again in your
sub-sitemaps.
And because you have a contract between the parent and sub sitemaps
(the uri-prefix) you
can deliver common SitemapComponents from the parent sitemap to your
sub-sitemaps as well.
- If you break a sitemap all its sub-sitemaps are broken as well (because
of the hierarchical arragement).
+ If you break a sitemap all its sub-sitemaps are broken as well (because
of the hierarchical arrangement).
</p>
<p>
- However you can create independant subsitemaps, which meet the
following goals:
+ However you can create independent subsitemaps, which meet the
following goals:
</p>
<ol>
<li>Simplify site construction</li>
@@ -445,9 +445,9 @@
<p>
Just build a main sitemap with the minimum needs: A matcher and a
selector.
These two components allow to select and direct to mount two other
sitemaps.
- These sub-sitemaps load the componants they need (which includes
generators
+ These sub-sitemaps load the components they need (which includes
generators
and transformers etc...) and have the map elements for that
site/application.
- The benefit is that each sitemap is completely independant of each
other and
+ The benefit is that each sitemap is completely independent of each
other and
any error in that sitemap does not kill any other sitemap.
</p>
<p>
@@ -525,7 +525,7 @@
<p>
This interfaces identifies classes that produce XML data, sending SAX
events to the configured <code>XMLConsumer</code>.<br/>
- It's beyond the scope of this interface to specify a way in wich the XML
+ It's beyond the scope of this interface to specify a way in which the
XML
data production is started.
</p>
@@ -690,7 +690,7 @@
* calling environment which may be used
* to select values to test the expression.
* @param parameters The sitemap parameters, as specified by
<parameter/> tags.
- * @return boolean Signals successfull test.
+ * @return boolean Signals successful test.
*/
boolean select (String expression, Map objectModel, Parameters
parameters);
}
1.4 +11 -11 xml-cocoon2/xdocs/sql-transformer.xml
Index: sql-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/sql-transformer.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sql-transformer.xml 2001/07/13 09:56:56 1.3
+++ sql-transformer.xml 2001/07/18 11:11:38 1.4
@@ -30,7 +30,7 @@
</ul>
</s1>
-<s1 title="Basic functionallity">
+<s1 title="Basic functionality">
<p>
To be able to query a database, we need XML that describes exactly what we
want
to do. The general structure of this input XML is as follows:
@@ -49,7 +49,7 @@
</source>
<p>
-Nothing prevents you from putting other XML aroung the page element. If you
do,
+Nothing prevents you from putting other XML around the page element. If you
do,
it will stay untouched. The format of the SQL statement or the stored
procedure
is exactly the same as if you would call it directly from java with a
prepared
statement or a callable statement.
@@ -70,7 +70,7 @@
</li>
<li>
isstoredprocedure:
-When you want to use stored procedures, you have to explicitely add this
+When you want to use stored procedures, you have to explicitly add this
attribute to the query element. By default, the transformer assumes that you
want to execute a SQL statement.
<br/>
@@ -120,11 +120,11 @@
</p>
<p>
The 'show-nr-of-rows' instructs the transformer to count the number of rows
in
-the resultset explicitely and to set the result as attribute to the rowset
-element. This attribute is only usefull in combination with an sql
statement,
+the resultset explicitly and to set the result as attribute to the rowset
+element. This attribute is only useful in combination with an sql statement,
not with stored procedures. If a stored procedure returns a resultset and
you
want to know how many rows it contains, you have to count the number of
rows in
-another transformer or your stored procedure has to rerutn it also (last
+another transformer or your stored procedure has to return it also (last
solution is the best one)
</p>
<p>
@@ -170,12 +170,12 @@
</p>
<p>
By now you should be able to use the SQLTransformer, but there are some more
-options you might find usefull...
+options you might find useful...
</p>
</s1>
-<s1 title="Advanced functionallity">
+<s1 title="Advanced functionality">
<s2 title="Substitution">
<p>
Sometimes you need more information before you can execute a query, eg. the
name
@@ -241,7 +241,7 @@
<s2 title="Ancestors">
<p>
-This functionallity is best described by a simple example.
+This functionality is best described by a simple example.
</p>
<p>
Take following input XML:
@@ -313,7 +313,7 @@
<p>
Stored procedures can return data as a parameter. To make use of this
-functionallity in java, you have to register these parameters as 'out
+functionality in java, you have to register these parameters as 'out
parameters'. Since this information is application specific, the
SQLTransformer
uses reflection to retrieve the data in the right format. For this, an extra
element is needed in the input XML:
@@ -375,7 +375,7 @@
element will be created, containing all the data of the resultset.
It is also possible to use an 'in-parameter' element, eg. <in-parameter
sql:nr="1" sql:value="1"/>.
-This functionallity is only provided to be complete, because it is available
in
+This functionality is only provided to be complete, because it is available
in
java itself. You can also use the 'in-parameter' in combination with a SQL
statement.
Used in combination with an out-parameter, a ?-parameter can be an
in-parameter
1.5 +3 -3 xml-cocoon2/xdocs/uc2.xml
Index: uc2.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/uc2.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- uc2.xml 2001/07/16 06:36:26 1.4
+++ uc2.xml 2001/07/18 11:11:38 1.5
@@ -14,7 +14,7 @@
<body>
<s1 title="Overview">
<p>
- This document is inteded for both Users and Developers
+ This document is intended for both Users and Developers
and presents an overall picture of @[EMAIL PROTECTED]
</p>
@@ -133,7 +133,7 @@
<s2 title="Core Cocoon">
<ul>
<li>Avalon framework for logging, configuration, threading, context
etc.</li>
- <li>Cacheing mechanism</li>
+ <li>Caching mechanism</li>
<li>Pipeline handling</li>
<li>Program generation, compilation, loading and execution.</li>
<li>Base classes for generation, transformation, serialization,
components.</li>
@@ -205,7 +205,7 @@
// A bunch of other imports
public class counter_xsp extends XSPGenerator {
- // .. Bookkeepig stuff commented out.
+ // .. Bookkeeping stuff commented out.
/* User Class Declarations */
static private int counter = 0;
private synchronized int count() {
1.3 +2 -2 xml-cocoon2/xdocs/xslt-transformer.xml
Index: xslt-transformer.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xslt-transformer.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xslt-transformer.xml 2001/07/13 09:57:14 1.2
+++ xslt-transformer.xml 2001/07/18 11:11:39 1.3
@@ -14,7 +14,7 @@
<body>
<s1 title="Trax/XSLT Transformer">
<p>The xslt transformer reads an xsl document from the
local file system or from any url.
- It transformes the sax stream using this stylesheet.</p>
+ It transforms the sax stream using this stylesheet.</p>
<p>The xslt transformer is the default transformer .</p>
<ul>
<li>Name : xslt</li>
@@ -35,7 +35,7 @@
This property is false by default. If set to true
the values of a request
parameter is available using a variable in the xslt
with the name of the parameter.</li>
<li>use-browser-capabilities-db: true|false -
This configuration forces the transformer to make all
- properties from the browser capability database
available in the XSLT stylesheetas.
+ properties from the browser capability database
available in the XSLT stylesheet as.
Note that this might have issues concerning
cachability of the generated output of this
transformer as the caching algorithm adds this
values to the validation phase.
The default for this property is false.</li>
1.3 +26 -26 xml-cocoon2/xdocs/xsp-internals.xml
Index: xsp-internals.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xsp-internals.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xsp-internals.xml 2001/05/23 12:32:22 1.2
+++ xsp-internals.xml 2001/07/18 11:11:39 1.3
@@ -218,7 +218,7 @@
</generator>
<filter name="xslt">
<parameter name="stylesheet"
- value="../samples/stylsheets/simple-page.xsl"/>
+ value="../samples/stalemates/simple-page.xsl"/>
</filter>
<serializer name="html">
<parameter name="contentType" value="text/html"/>
@@ -296,10 +296,10 @@
<code>hasContentChanged()</code> method that is tested by
<code>ServerPagesGenerator</code> to assert whether dynamic content
should
not be regenerated for a given request. The default implementation
- unconditionally returns <code>true</code>, but can be overriden by XSP
+ unconditionally returns <code>true</code>, but can be overridden by XSP
pages based on their interpretation of the Cocoon <code>request</code>
object. This is an <em>experimental</em> feature that will become
- meaningful only when a SAX-event cacheing mechanism is added to Cocoon.
+ meaningful only when a SAX-event caching mechanism is added to Cocoon.
</p>
<p>
@@ -435,7 +435,7 @@
</s2>
<anchor id="program-unload"/>
- <s2 title="Unoading Programs">
+ <s2 title="Unloading Programs">
<p>
When a previously loaded program is no longer needed (or becomes
"outdated" as explained below) the language processor may need to
@@ -567,7 +567,7 @@
</p>
<p>
- This method exists to asist markup language code generators in
+ This method exists to assist markup language code generators in
escaping <code>Text</code> XML nodes.
</p>
</s2>
@@ -593,7 +593,7 @@
<ul>
<li>Variable <code>compilerClass</code>. Used to create instances
of the language's
- <jump achor="compiler">compiler</jump>.
+ <jump anchor="compiler">compiler</jump>.
</li>
<li>Variable <code>deleteSources</code>. Used to state whether
intermediate source files should be deleted after successful
@@ -741,7 +741,7 @@
</p>
<ul>
- <li><em>Javac</em>. A wrapper to Sun's bultin compiler
+ <li><em>Javac</em>. A wrapper to Sun's builtin compiler
</li>
<li><em>Jikes</em>. A wrapper to IBM's <em>Jikes</em> compiler
</li>
@@ -780,7 +780,7 @@
<p>
Method <code>doUnload</code> provides an empty default implementation
- that can be overriden by derived compiled languages should unloading
+ that can be overridden by derived compiled languages should unloading
cleanup be actually required.
</p>
@@ -839,7 +839,7 @@
<ul>
<li><code>addDirectory</code>. Passed to the proxied
- <code>RepositortyClassLoader</code>
+ <code>RepositoryClassLoader</code>
</li>
<li><code>loadClass</code>. Passed to the proxied
<code>RepositortyClassLoader</code>
@@ -924,7 +924,7 @@
<note>
Despite being supported by BSF, Rhino Javascript is separately
supported by Cocoon as a compiled language in order to take
- advantage of automatic class reloading and persisent class file
+ advantage of automatic class reloading and persistent class file
storage.
</note>
@@ -1059,7 +1059,7 @@
</s2>
<anchor id="logicsheet-class"/>
- <s2 title="The Logichseet class">
+ <s2 title="The Logicsheet class">
<anchor id="logicsheet"/>
<p>
A <em>logicsheet</em> is an XML filter used to translate user-defined
@@ -1082,7 +1082,7 @@
<p>
Logicsheets are represented in class
<link
href="javadocs/org/apache/cocoon/components/language/markup/Logicsheet.html">
- <code>Logichseet</code>.
+ <code>Logicsheet</code>.
</link>
This
class exposes the following methods:
@@ -1109,7 +1109,7 @@
Currently, <code>Logicsheet</code> is a concrete class. It should
be redefined as an interface in order to decouple it from the use
of XSLT stylesheets. Again, while stylesheets are the "obvious" way
- to implement logichseets, a user-supplied XML filter may also be
+ to implement logicsheets, a user-supplied XML filter may also be
used in some cases.
The current implementation uses an ugly
hack where a Xalan stylesheet processor is used to perform
@@ -1119,7 +1119,7 @@
</s2>
<anchor id="named-logicsheet"/>
- <s2 title="Named Logichseets">
+ <s2 title="Named Logicsheets">
<p>
As explained in
<jump href="logicsheet-concepts.html" anchor="logicsheet-object">
@@ -1169,7 +1169,7 @@
<p>
This feature relieves page authors from the need to explicitly
declare commonly used logicsheets in their documents. Builtin
- logichseets are automatically applied if the document declares
+ logicsheets are automatically applied if the document declares
their same namespace URI.
</p>
@@ -1181,7 +1181,7 @@
</s2>
<anchor id="logicsheet-generator"/>
- <s2 title="Logichseet Code Generators">
+ <s2 title="Logicsheet Code Generators">
<p>
Logicsheets translate dynamic tags to equivalent code-embedding
directives expressed in the markup language at hand. They do not,
@@ -1206,7 +1206,7 @@
<ul>
<li><code>addLogicsheet</code>.
Add a logicsheet to the generator's logicsheet list.
- Logichseets are applied in the order of their addition.
+ Logicsheets are applied in the order of their addition.
</li>
<li><code>generateCode</code>.
Return a string containing a source program resulting from
@@ -1216,14 +1216,14 @@
<p>
Though "regular" logicsheets as such do not emit source code,
- <code>LogicshetCodeGenerator</code> expects its <em>last</em>
+ <code>LogicsheetCodeGenerator</code> expects its <em>last</em>
stylesheet to produce <em>a single element</em> containing only
a text node.
</p>
<p>
- This final, programming language-specific logichseet is
- reponsible for actually expanding code-embedding directives
+ This final, programming language-specific logicsheet is
+ responsible for actually expanding code-embedding directives
into source code.
</p>
@@ -1301,7 +1301,7 @@
<s1 title="The XSP Markup Language">
<p>
So far, programming and markup languages have been described
- in general, without explicitly refering to the XSP language.
+ in general, without explicitly referring to the XSP language.
</p>
<p>
@@ -1315,7 +1315,7 @@
<note>
- The XSP syntax is being revised to allow for the omision of the
+ The XSP syntax is being revised to allow for the omission of the
root <code><xsp:page></code> element. This is convenient
for the (typical) case in which all logic has been conveniently
placed in logicsheets so that XSP pages do not need to embed any
@@ -1397,7 +1397,7 @@
</s2>
<anchor id="xsp-builtin"/>
- <s2 title="XSP Builtin Logichseets">
+ <s2 title="XSP Builtin Logicsheets">
<p>
XSP for Java currently provides only 2 builtin logicsheets:
<code>request</code> and <code>response</code>, associated
@@ -1459,7 +1459,7 @@
</p>
<p>
- This method is reponsible for locating, loading and instantiating
+ This method is responsible for locating, loading and instantiating
a program derived from the given source document. Failing this,
the program is generated and stored in an external, persistent
<em>repository</em>.
@@ -1648,11 +1648,11 @@
passed to subclasses for easier initialization
</li>
<li><code>setParameters</code>.
- An empty method to be overriden by subclasses for parameter-based
+ An empty method to be overridden by subclasses for parameter-based
initialization
</li>
<li><code>setAdditionalConfiguration</code>.
- An empty method to be overriden by subclasses when parameter-based
+ An empty method to be overridden by subclasses when parameter-based
initialization is not sufficient because there are nested
configuration elements in the corresponding sitemap entry
</li>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
