mpoeschl 01/12/25 10:19:18
Modified: xdocs index.xml
xdocs/howto cache-service.xml factory-service.xml
intake-service.xml jsp-service.xml
localization-service.xml mimetype-service.xml
naming-service.xml pool-service.xml
scheduler-service.xml security-service.xml
upload-service.xml template-service.xml
velocity-service.xml xmlrpc-service.xml
xslt-service.xml
Log:
fix configuration doc
Revision Changes Path
1.2 +8 -4 jakarta-turbine-fulcrum/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 2001/07/19 09:03:24 1.1
+++ index.xml 2001/12/25 18:19:17 1.2
@@ -10,10 +10,14 @@
<body>
<section name="What is Fulcrum?">
-
- <p>
- Fulcrum is a services framework.
- </p>
+ <p>
+ Fulcrum is a services framework.
+ </p>
+ <p>
+ Fulcrum was developed as part of the Turbine Framework. It is now
+ decoupled and can be used by itself. Starting with version 2.2 Turbine
+ will use the decoupled Fulcrum.
+ </p>
</section>
1.2 +4 -5 jakarta-turbine-fulcrum/xdocs/howto/cache-service.xml
Index: cache-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/cache-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cache-service.xml 2001/12/17 16:31:36 1.1
+++ cache-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Global Cache Service</title>
+ <title>Fulcrum Services - Global Cache Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -26,7 +26,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -36,8 +36,7 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.GlobalCacheService.classname=org.apache.turbine.services.cache.TurbineGlobalCacheService
-.
+services.GlobalCacheService.classname=org.apache.fulcrum.cache.TurbineGlobalCacheService.
.
.
@@ -95,7 +94,7 @@
You can also place an expiration time on your objects so the Service will
automatically remove them when they expire. If you don't specify an expiration
time, the Service uses the default time set by the property
-<em>cache.check.frequency</em> in the TurbineResources.properties
+<em>cache.check.frequency</em> in the Fulcrum.properties
file. To see an example, look at the file <strong>TestGlobalCache.java</strong>
located in the actions folder.
</p>
1.2 +10 -10 jakarta-turbine-fulcrum/xdocs/howto/factory-service.xml
Index: factory-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/factory-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- factory-service.xml 2001/12/17 16:31:36 1.1
+++ factory-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Factory Service</title>
+ <title>Fulcrum Services - Factory Service</title>
<author email="[EMAIL PROTECTED]">Ilkka Priha</author>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -34,7 +34,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -44,12 +44,12 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.FactoryService.classname=org.apache.turbine.services.factory.TurbineFactoryService
+services.FactoryService.classname=org.apache.fulcrum.factory.TurbineFactoryService
.
.
.
# -------------------------------------------------------------------
-#
+#
# F A C T O R Y S E R V I C E
#
# -------------------------------------------------------------------
@@ -83,7 +83,7 @@
<p>
In Turbine, the Factory Service is currently only used internally by the Pool
Service.
Applications can also use the service instead of Class.forName() and for unifying
-initialization, configuration and access to vendor specific object factories.
+initialization, configuration and access to vendor specific object factories.
The following is a simplified example of a customized DOM parser factory:
</p>
@@ -98,7 +98,7 @@
import org.apache.turbine.services.factory.Factory;
/**
- * A factory for instantiating DOM parsers.
+ * A factory for instantiating DOM parsers.
*/
public class DomBuilderFactory implements Factory
{
@@ -189,11 +189,11 @@
<source><![CDATA[
// Access the service singleton.
-FactoryService service = (FactoryService)
+FactoryService service = (FactoryService)
TurbineServices.getInstance().getService(FactoryService.SERVICE_NAME);
-
-// Create a new DOM parser.
-DocumentBuilder parser =
+
+// Create a new DOM parser.
+DocumentBuilder parser =
service.getInstance("javax.xml.parsers.DocumentBuilder");
]]></source>
1.2 +65 -67 jakarta-turbine-fulcrum/xdocs/howto/intake-service.xml
Index: intake-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/intake-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- intake-service.xml 2001/12/17 16:31:36 1.1
+++ intake-service.xml 2001/12/25 18:19:17 1.2
@@ -3,7 +3,7 @@
<document>
<properties>
- <title>Turbine Services - Intake Service</title>
+ <title>Fulcrum Services - Intake Service</title>
<author email="[EMAIL PROTECTED]">John McNally</author>
<author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
@@ -59,7 +59,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -70,18 +70,16 @@
# service.[name].[property]=[value]
services.IntakeService.classname= \
-org.apache.turbine.services.intake.TurbineIntakeService
+org.apache.fulcrum.intake.TurbineIntakeService
# -------------------------------------------------------------------
-#
+#
# I N T A K E S E R V I C E
#
# -------------------------------------------------------------------
# The location of the xml file specifying valid inputs
services.IntakeService.xml.path=WEB-INF/conf/intake.xml
-
-tool.request.intake=org.apache.turbine.services.intake.IntakeTool
]]></source>
</section>
@@ -95,8 +93,8 @@
<p>
Intake is made available in the Velocity context with the default value
-of $intake. The name of the variable that is used is what is configured
-for the tool. For example, the current configuration is "tool.request.intake".
+of $intake. The name of the variable that is used is what is configured
+for the tool. For example, the current configuration is "tool.request.intake".
To change the name of the variable to "foo", it would be "tool.request.foo".
</p>
@@ -123,11 +121,11 @@
<source><![CDATA[
<input-data basePackage="org.tigris.scarab.">
-<group name="AttributeValue" key="attv"
+<group name="AttributeValue" key="attv"
mapToObject="om.AttributeValue">
<field name="Value" key="val" type="String">
<rule name="maxLength" value="255">Value length cannot be > 255</rule>
- <required-message>This module requires data for this
+ <required-message>This module requires data for this
attribute.
</required-message>
</field>
@@ -138,7 +136,7 @@
</field>
<field name="OptionId" key="optionid" type="NumberKey">
<rule name="mask" value="^$|[0-9]+">Please select a valid choice</rule>
- <required-message>This module requires that you select an option
+ <required-message>This module requires that you select an option
for this attribute.
</required-message>
</field>
@@ -148,7 +146,7 @@
<field name="Username" key="u" type="String">
<rule name="minLength" value="1">Please enter an email address</rule>
<rule name="mask" value=".+@.+\..+">Please enter a valid email
address</rule>
- </field>
+ </field>
<field name="Password" key="p" type="String">
<rule name="minLength" value="1">Please enter a password</rule>
</field>
@@ -168,9 +166,9 @@
<p>
The group tag has a class attribute which is the name that will be used
-within templates and java code to refer to the group. It also contains a
+within templates and java code to refer to the group. It also contains a
key attribute which will be used in the query parameters. The key is
-not referenced in any code, so it can be a short name (even 1 character) as
+not referenced in any code, so it can be a short name (even 1 character) as
long as it is uniquely identifies the group from the rest.
</p>
<p>
@@ -185,7 +183,7 @@
the field as well as assigning the field data to the bean after successful
validation. The field must have a type, which can be simple types such as
String and Integer. It is planned that more complex types, such as
-Email, Url, or Date, will be added that will add functionality that is
+Email, Url, or Date, will be added that will add functionality that is
difficult or not possible with a simple regex mask.
</p>
<p>
@@ -214,7 +212,7 @@
<field name="Username" key="u" type="String">
<rule name="minLength" value="1">Please enter an email address</rule>
<rule name="mask" value=".+@.+\..+">Please enter a valid email address</rule>
-</field>
+</field>
<field name="Password" key="p" type="String">
<rule name="minLength" value="1">Please enter a password</rule>
</field>
@@ -242,10 +240,10 @@
(1) <form action="$link.setPage("Login.vm")" method="POST" name="login" >
(2) <input type="hidden" name="action" value="Login">
(3) #if ($data.Parameters.nextTemplate)
-(4) <input type="hidden" name="nextTemplate"
+(4) <input type="hidden" name="nextTemplate"
value="$data.Parameters.nextTemplate">
#else
-(5) <input type="hidden" name="nextTemplate" value="Start.vm">
+(5) <input type="hidden" name="nextTemplate" value="Start.vm">
#end
<p>
@@ -267,7 +265,7 @@
(11) $loginGroup.Password.Message<br>
#end
(12) <input name= "$loginGroup.Password.Key"
- value="" size="25" type="text"
+ value="" size="25" type="text"
onChange="document.login.submit();">
</p>
@@ -349,19 +347,19 @@
</p>
<p>
-Below is an example of the HTML that is sent to the browser after the
+Below is an example of the HTML that is sent to the browser after the
page has been requested:
</p>
<source><![CDATA[
-<form action="http://foo:8080/scarab/servlet/scarab/template/Login.vm";
+<form action="http://foo:8080/scarab/servlet/scarab/template/Login.vm";
method="POST" name="login" >
<input type="hidden" name="action" value="Login">
- <input type="hidden" name="nextTemplate" value="Start.vm">
-
+ <input type="hidden" name="nextTemplate" value="Start.vm">
+
<p>
Email Address:
-
+
<input name= "login_0u"
value="" size="25" type="text">
</p>
@@ -408,18 +406,18 @@
{
IntakeTool intake = (IntakeTool) context.get("intake");
- if ( intake.isAllValid() && checkUser(data, context) )
+ if ( intake.isAllValid() && checkUser(data, context) )
{
String template = data.getParameters()
- .getString(ScarabConstants.NEXT_TEMPLATE,
+ .getString(ScarabConstants.NEXT_TEMPLATE,
TurbineResources.getString("template.homepage", "Start.vm") );
setTemplate(data, template);
}
- else
+ else
{
// Retrieve an anonymous user
data.setUser (TurbineSecurity.getAnonymousUser());
- setTemplate(data,
+ setTemplate(data,
data.getParameters()
.getString(ScarabConstants.TEMPLATE, "Login.vm"));
}
@@ -474,7 +472,7 @@
<section name="Attribute Value example">
<source><![CDATA[
-<group name="AttributeValue" key="attv"
+<group name="AttributeValue" key="attv"
mapToObject="om.AttributeValue">
]]></source>
@@ -493,7 +491,7 @@
<source><![CDATA[
<field name="Value" key="val" type="String">
<rule name="maxLength" value="255">Value length cannot be > 255</rule>
- <required-message>This module requires data for this
+ <required-message>This module requires data for this
attribute.
</required-message>
</field>
@@ -517,7 +515,7 @@
#set ( $action = $link.setPage("EditUrl.vm").setAction("SaveUrl") )
<form action="$action"
method="post">
-
+
#set ( $attributeValue = $issue.AttributeValue("URL") )
#set ( $group = $intake.AttributeValue.mapTo($attributeValue) )
@@ -550,8 +548,8 @@
to retrieve the key information for the field. This would evaluate to
"attv_0url". What this is a combination of the group key (attv), a "_0"
is the result of retrieving the "$intake.AttributeValue.Default" and the
-"url" is the field key. The value attribute would evaluate to just an
-empty String the first time around. The $intake.declareGroups() is a
+"url" is the field key. The value attribute would evaluate to just an
+empty String the first time around. The $intake.declareGroups() is a
special method that will create a hidden input field that declares which
groups have been added to the page. We will discuss that in more detail
further down.
@@ -563,7 +561,7 @@
</p>
<source><![CDATA[
-<form action="http://server/s/servlet/s/template/EnterUrl.vm/action/EnterUrlAction";
+<form action="http://server/s/servlet/s/template/EnterUrl.vm/action/EnterUrlAction";
method="post">
Enter Url:
@@ -586,9 +584,9 @@
{
IntakeTool intake = (IntakeTool)context
.get(ScarabConstants.INTAKE_TOOL);
-
+
// check to see if the fields are valid
- if ( intake.isAllValid() )
+ if ( intake.isAllValid() )
{
// get the "AttributeValue" Group
AttributeValue av = new AttributeValue();
@@ -612,7 +610,7 @@
<source><![CDATA[
<field name="Value" key="val" type="String">
<rule name="maxLength" value="255">Value length cannot be > 255</rule>
- <required-message>This module requires data for this
+ <required-message>This module requires data for this
attribute.
</required-message>
</field>
@@ -626,12 +624,12 @@
</section>
<section name="Multiple groups of the same class in one form">
-
+
<p>
This example uses a form from Scarab that assigns values to various
attribute's that are relevant for an issue (bug). Attributes include
-summary, operating system, platform, assigned to, etc. Some of the
-attributes are required, but not all.
+summary, operating system, platform, assigned to, etc. Some of the
+attributes are required, but not all.
</p>
<p>
@@ -651,14 +649,14 @@
<hr><br>Please fill in the following:<br><br>
#foreach ( $attVal in $issue.OrderedModuleAttributeValues )
- #set ( $attrInput = $intake.AttributeValue.mapTo($attVal) )
+ #set ( $attrInput = $intake.AttributeValue.mapTo($attVal) )
#if ( $attVal.Attribute.AttributeType.ValidationKey )
#set ( $field = $attVal.Attribute.AttributeType.ValidationKey )
#elseif ($attVal.Attribute.AttributeType.Name == "combo-box" )
#set ( $field = "OptionId" )
#else
- #set ( $field = "Value" )
+ #set ( $field = "Value" )
#end
#if ( $attVal.isRequired() )
@@ -680,9 +678,9 @@
#attrValueErrorMsg ( $attVal $field )
</font>
<br>
- #if ($attVal.Attribute.AttributeType.Name == "long-string" )
+ #if ($attVal.Attribute.AttributeType.Name == "long-string" )
- <textarea name= "$attrInput.Value.Key" cols="40"
+ <textarea name= "$attrInput.Value.Key" cols="40"
rows="5">$!attrInput.Value</textarea>
#else
@@ -695,7 +693,7 @@
#end
<p>
- <input type="submit"
+ <input type="submit"
name="eventSubmit_doEnterissue" value="Submit Issue">
$intake.declareGroups()
@@ -706,7 +704,7 @@
The main new thing added here is that the $intake group is mapped to a business
object. A business object that is to be used in this way is expected to
implement the Retrievable interface, which provides a method to get a
-String key which uniquely identifies the object.
+String key which uniquely identifies the object.
</p>
<p>
The action:
@@ -729,28 +727,28 @@
summary.setRequired(true);
issue.setVocabulary(new Vocabulary(summary.toString()));
- if ( intake.isAllValid() )
+ if ( intake.isAllValid() )
{
Iterator i = issue.getModuleAttributeValuesMap()
.values().iterator();
- while (i.hasNext())
+ while (i.hasNext())
{
aval = (AttributeValue)i.next();
group = intake.get("AttributeValue", aval.getQueryKey());
- if ( group != null )
+ if ( group != null )
{
group.setProperties(aval);
- }
+ }
}
-
- if ( issue.containsMinimumAttributeValues() )
+
+ if ( issue.containsMinimumAttributeValues() )
{
issue.save();
String template = data.getParameters()
- .getString(ScarabConstants.NEXT_TEMPLATE,
+ .getString(ScarabConstants.NEXT_TEMPLATE,
"entry,Wizard3.vm");
- setTemplate(data, template);
+ setTemplate(data, template);
}
}
}
@@ -766,43 +764,43 @@
<source><![CDATA[
Dan Diephouse wrote:
->
+>
> I want to validate a form that updates my business object properties
> with intake. I got the latest cvs of turbine-2 repository and built a
> new distribution of the turbine jar. I can easily use intake to add
> validate items I add to my databse, but I'm running in to a snag when
> trying to modify them. I've defined by business object in the intake
> validation file. I use the following code to update my item:
->
+>
> IntakeTool intake = (IntakeTool) context.get("intake");
->
+>
> ParameterParser pp = data.getParameters();
->
+>
> if ( intake.isAllValid() ) {
> Job j = new Job();
> j.setNew(false);
> group.setProperties(j);
->
+>
> JobPeer.doUpdate(j);
->
+>
> Error--> data.getParameters().add("jobid", j.getJobId().toString());
> data.setMessage("Job updated.");
> } else {
> data.setMessage("There was an error updating the job.
> Check below for further information.");
> }
->
+>
> It runs OK, until I try and retrieve the JobId. I get a Null Pointer
> exception. Is there something I'm doing wrong here? Or is this a bug?
> Do I need to specify that this is not a new object to intake? I would
> include my template, but there are lots of fields so its really long.
> But here's a little summary with most fields gone:
->
+>
> #set ( $job = $basecamp.getJob() ) - This gets a job from a pull tool
> #set ( $jobGroup = $intake.Job.mapTo($job) )
-> <input type=hidden name="$jobGroup.JobId.Key"
+> <input type=hidden name="$jobGroup.JobId.Key"
> value="$jobGroup.JobId.Value">
->
+>
> #if ( !$jobGroup.Title.isValid() )
> $jobGroup.Title.Message<br>
> #end
@@ -813,9 +811,9 @@
> .
> .
> $intake.declareGroups()
->
+>
> Thanks,
->
+>
> Dan Diephouse
This is not how i usually do things, but I guess it could work. One
@@ -827,7 +825,7 @@
Here is what I consider a normal course of events:
-1. In the template:
+1. In the template:
$job = $foo.Job
#set ( $jobGroup = $intake.Job.mapTo($job) )
1.2 +4 -4 jakarta-turbine-fulcrum/xdocs/howto/jsp-service.xml
Index: jsp-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/jsp-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jsp-service.xml 2001/12/17 16:31:36 1.1
+++ jsp-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - JSP Service</title>
+ <title>Fulcrum Services - JSP Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -30,7 +30,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -40,12 +40,12 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.JspService.classname=org.apache.turbine.services.jsp.TurbineJspService
+services.JspService.classname=org.apache.fulcrum.jsp.TurbineJspService
.
.
.
# -------------------------------------------------------------------
-#
+#
# J S P S E R V I C E
#
# -------------------------------------------------------------------
1.2 +3 -3 jakarta-turbine-fulcrum/xdocs/howto/localization-service.xml
Index: localization-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/localization-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- localization-service.xml 2001/12/17 16:31:36 1.1
+++ localization-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Localization Service</title>
+ <title>Fulcrum Services - Localization Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -21,7 +21,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -31,7 +31,7 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.GlobalCacheService.classname=org.apache.turbine.services.cache.TurbineGlobalCacheService
+services.GlobalCacheService.classname=org.apache.fulcrum.cache.TurbineGlobalCacheService
.
.
.
1.2 +18 -18 jakarta-turbine-fulcrum/xdocs/howto/mimetype-service.xml
Index: mimetype-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/mimetype-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mimetype-service.xml 2001/12/17 16:31:36 1.1
+++ mimetype-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Mimetype Service</title>
+ <title>Fulcrum Services - Mimetype Service</title>
<author email="[EMAIL PROTECTED]">Ilkka Priha</author>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -25,7 +25,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -35,29 +35,29 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.MimeTypeService.classname=org.apache.turbine.services.mimetype.TurbineMimeTypeService
+services.MimeTypeService.classname=org.apache.fulcrum.mimetype.TurbineMimeTypeService
.
.
.
# -------------------------------------------------------------------
-#
+#
# M I M E T Y P E S E R V I C E
#
# -------------------------------------------------------------------
-# This property specifies a file containing mappings between MIME
+# This property specifies a file containing mappings between MIME
# content types and the corresponding file name extensions. The
-# service itself contains a hardcoded set of most common mappings.
-# The file must use the same syntax as the mime.types file of
-# the Apache Server, i.e.
+# service itself contains a hardcoded set of most common mappings.
+# The file must use the same syntax as the mime.types file of
+# the Apache Server, i.e.
# <mimetype> <ext1> <ext2>...
#
#services.MimeTypeService.mime.types=/WEB-INF/conf/mime.types
-# This property specifies a file containing mappings between locales
-# and the corresponding character encodings. The service itself
-# contains a hardcoded set of most common mappings.
-# The file should use the Java property file syntax, i.e.
+# This property specifies a file containing mappings between locales
+# and the corresponding character encodings. The service itself
+# contains a hardcoded set of most common mappings.
+# The file should use the Java property file syntax, i.e.
# <lang_country_variant>=<charset>
#
#services.MimeTypeService.charsets=/WEB-INF/conf/charset.properties
@@ -76,7 +76,7 @@
<p>
The mappings between locales and the corresponding character encodings
-are specified using the Java property file syntax, where the locale
+are specified using the Java property file syntax, where the locale
specification is the key of the property key and the charset is the value
of the property. The locale specification consists of three parts:
</p>
@@ -87,7 +87,7 @@
<p>
The variant can be whatever is appropriate for the application, like a
-markup language specification, a browser specification, etc. The service
+markup language specification, a browser specification, etc. The service
looks for charsets using the following search order:
</p>
@@ -104,14 +104,14 @@
<p>
The service contains defaults for several language mappings and more specific
ones can be specified in an optional property file, e.g. __wml=UTF-8. The name
-of the property file can be given with a service property named "charsets".
+of the property file can be given with a service property named "charsets".
The service caches results of the search, which should guarantee good performance.
</p>
<p>
The mappings between MIME types and the corresponding file name extensions
are specified using the same syntax as the mime.types file of the Apache Server,
-i.e.:
+i.e.:
</p>
<source><![CDATA[
@@ -119,14 +119,14 @@
]]></source>
<p>
-The service contains defaults for most common MIME types, like text/plain,
+The service contains defaults for most common MIME types, like text/plain,
text/html, text/x-hdml, text/vnd.wap.wml, image/gif and image/jpeg. More
specific ones can be specified in an optional MIME types file. The name of
the MIME types file can be given with a service property named "mime.types".
</p>
<p>
-The TurbineMimeTypes class is a static accessor for the most common
+The TurbineMimeTypes class is a static accessor for the most common
MimeType Service methods.
</p>
1.2 +3 -3 jakarta-turbine-fulcrum/xdocs/howto/naming-service.xml
Index: naming-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/naming-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- naming-service.xml 2001/12/17 16:31:36 1.1
+++ naming-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Naming Service</title>
+ <title>Fulcrum Services - Naming Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
<author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
@@ -24,7 +24,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -34,7 +34,7 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.NamingService.classname=org.apache.turbine.services.naming.TurbineNamingService
+services.NamingService.classname=org.apache.fulcrum.naming.TurbineNamingService
.
.
.
1.2 +22 -22 jakarta-turbine-fulcrum/xdocs/howto/pool-service.xml
Index: pool-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/pool-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pool-service.xml 2001/12/17 16:31:36 1.1
+++ pool-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Pool Service</title>
+ <title>Fulcrum Services - Pool Service</title>
<author email="[EMAIL PROTECTED]">Ilkka Priha</author>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -12,34 +12,34 @@
<section name="Pool Service">
<p>
-The Pool Service extends the functionality of the Factory Service by adding
+The Pool Service extends the functionality of the Factory Service by adding
support for pooling objects intantiated from the given class name or
-Class object reference. Pooling of objects stabilizes memory consumption and
-reduces garbage collection making response times in server applications
+Class object reference. Pooling of objects stabilizes memory consumption and
+reduces garbage collection making response times in server applications
more predictable.
</p>
<p>
-When a new instance is requested from the service, it first checks its pool
-if one is available. If the the pool is empty, a new object will be instantiated
-from the given class. If the class is specified by its name, the request to create
+When a new instance is requested from the service, it first checks its pool
+if one is available. If the the pool is empty, a new object will be instantiated
+from the given class. If the class is specified by its name, the request to create
an instance will be forwarded to the Factory Service.
</p>
<p>
-For pooled objects implementing the Recyclable interface, a recycle method
-will be called, when they are taken from the pool, and a dispose method,
-when they are returned to the pool. Implementations of the methods should
-clear and initialize the pooled instances correspondingly. Objects
-that do not implement the interface can also be pooled, if they do not
-need to perform any specific actions during pooling. A RecyclableSupport class
+For pooled objects implementing the Recyclable interface, a recycle method
+will be called, when they are taken from the pool, and a dispose method,
+when they are returned to the pool. Implementations of the methods should
+clear and initialize the pooled instances correspondingly. Objects
+that do not implement the interface can also be pooled, if they do not
+need to perform any specific actions during pooling. A RecyclableSupport class
can be extended to get a minimal implementation of the interface.
</p>
<p>
An ArrayCtorRecyclable interface extends the Recyclable interface providing
a more efficient recycle method with less reflection for recycling frequently
-used objects having constuctors with parameters.
+used objects having constuctors with parameters.
</p>
</section>
@@ -48,7 +48,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -58,12 +58,12 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.PoolService.classname=org.apache.turbine.services.pool.TurbinePoolService
+services.PoolService.classname=org.apache.fulcrum.pool.TurbinePoolService
.
.
.
# -------------------------------------------------------------------
-#
+#
# P O O L S E R V I C E
#
# -------------------------------------------------------------------
@@ -85,22 +85,22 @@
<p>
The Pool Service can be called instead of the Factory Service, when instantiating
objects that are needed repeatedly e.g. for processing client requests. Intances
-of RunData implementations, ParameterParser and CookieParser implementations,
+of RunData implementations, ParameterParser and CookieParser implementations,
Pull Service tools, etc, are typical examples of pooled objects. Used objects
-must be returned to the Pool Service for recycling. The TurbinePool class is a
+must be returned to the Pool Service for recycling. The TurbinePool class is a
static accessor for common methods of the Pool Service:
</p>
<source><![CDATA[
// Get a pooled DOM parser.
-DocumentBuilder parser =
+DocumentBuilder parser =
TurbinePool.getInstance("javax.xml.parsers.DocumentBuilder");
-
+
// Parse an XML document.
Document doc = parser.parse(myfile);
// Return the parser to the pool.
-TurbinePool.putInstance(parser);
+TurbinePool.putInstance(parser);
]]></source>
</section>
1.2 +5 -5 jakarta-turbine-fulcrum/xdocs/howto/scheduler-service.xml
Index: scheduler-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/scheduler-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- scheduler-service.xml 2001/12/17 15:04:56 1.1
+++ scheduler-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Scheduler Service</title>
+ <title>Fulcrum Services - Scheduler Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -29,7 +29,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
- #
+ #
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -39,7 +39,7 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-
services.SchedulerService.classname=org.apache.turbine.services.schedule.TurbineSchedulerService
+
services.SchedulerService.classname=org.apache.fulcrum.schedule.TurbineSchedulerService
.
.
.
@@ -103,7 +103,7 @@
"task: " + job.getTask() + " ran @: " +
new Date(System.currentTimeMillis()).toString() +
" taskcount " + taskcount);
-
+
//iterate the task counter
taskcount++;
}
@@ -263,7 +263,7 @@
</section>
<section name="Properties Based Scheduler">
-
+
<p>
Service for a cron like scheduler that uses the
TurbineResources.properties file instead of the database.
1.2 +7 -7 jakarta-turbine-fulcrum/xdocs/howto/security-service.xml
Index: security-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/security-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- security-service.xml 2001/12/17 16:31:36 1.1
+++ security-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Security Service</title>
+ <title>Fulcrum Services - Security Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -19,7 +19,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -29,20 +29,20 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.SecurityService.classname=org.apache.turbine.services.cache.<type>SecurityService
+services.SecurityService.classname=org.apache.fulcrum.security.SecurityService
.
.
.
# -------------------------------------------------------------------
-#
+#
# S E C U R I T Y S E R V I C E
#
# -------------------------------------------------------------------
#
# This is the class that implements the User interface.
-# You want to override this setting only if you want your User
-# implementation to provide application specific addtional
+# You want to override this setting only if you want your User
+# implementation to provide application specific addtional
# functionality.
#
# Default: org.apache.turbine.om.security.TurbineUser
@@ -52,7 +52,7 @@
#
# This setting is DBSecurityService specific - this class is consulted for the names
-# of the columns in the users' tables for the purpose of creating join queries.
+# of the columns in the users' tables for the purpose of creating join queries.
# If you use your own User implementation in conjunction with DBSecurityService,
# it's peer class must implement org.apache.turbine.om.security.peer.UserPeer
interface,
# and you need to specify the name of the peer class here.
1.2 +3 -3 jakarta-turbine-fulcrum/xdocs/howto/upload-service.xml
Index: upload-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/upload-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- upload-service.xml 2001/12/17 16:31:36 1.1
+++ upload-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Upload Service</title>
+ <title>Fulcrum Services - Upload Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -22,7 +22,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -32,7 +32,7 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.UploadService.classname=org.apache.turbine.services.upload.TurbineUploadService
+services.UploadService.classname=org.apache.fulcrum.upload.TurbineUploadService
.
.
.
1.2 +4 -4 jakarta-turbine-fulcrum/xdocs/howto/template-service.xml
Index: template-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/template-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- template-service.xml 2001/12/17 16:31:36 1.1
+++ template-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Template Service</title>
+ <title>Fulcrum Services - Template Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -19,7 +19,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -29,12 +29,12 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.TemplateService.classname=org.apache.turbine.services.template.TurbineTemplateService
+services.TemplateService.classname=org.apache.fulcrum.template.TurbineTemplateService
.
.
.
# -------------------------------------------------------------------
-#
+#
# T E M P L A T E S E R V I C E
#
# -------------------------------------------------------------------
1.2 +5 -5 jakarta-turbine-fulcrum/xdocs/howto/velocity-service.xml
Index: velocity-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/velocity-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- velocity-service.xml 2001/12/17 16:31:36 1.1
+++ velocity-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - Velocity Service</title>
+ <title>Fulcrum Services - Velocity Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -19,7 +19,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -29,19 +29,19 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.VelocityService.classname=org.apache.turbine.services.cache.TurbineVelocityService
+services.VelocityService.classname=org.apache.fulcrum.velocity.TurbineVelocityService
.
.
.
# -------------------------------------------------------------------
-#
+#
# V E L O C I T Y S E R V I C E
#
# -------------------------------------------------------------------
# The location of Velocity configuration file, relative to webapp root
# These properties will override the default properties set by Velocity.
-# You should specify the path to the templates directories as well as
+# You should specify the path to the templates directories as well as
# the path to the log file and they should also be relative to webapp root
services.VelocityService.template.extension=vm
1.2 +9 -9 jakarta-turbine-fulcrum/xdocs/howto/xmlrpc-service.xml
Index: xmlrpc-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/xmlrpc-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xmlrpc-service.xml 2001/12/17 16:31:36 1.1
+++ xmlrpc-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - XML-RPC Service</title>
+ <title>Fulcrum Services - XML-RPC Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -27,7 +27,7 @@
org.apache.turbine.services.xmlrpc.util.FileHandler</strong>
class that will perform these operations for you. Please refer
to the usage section below for more details.
-</p>
+</p>
</section>
@@ -35,7 +35,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -45,12 +45,12 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.XmlRpcService.classname=org.apache.turbine.services.xmlrpc.TurbineXmlRpcService
+services.XmlRpcService.classname=org.apache.fulcrum.xmlrpc.TurbineXmlRpcService
.
.
.
# -------------------------------------------------------------------
-#
+#
# X M L R P C S E R V I C E
#
# -------------------------------------------------------------------
@@ -68,8 +68,8 @@
services.XmlRpcService.port=12345
-# If any classes are specified here, the Service will create an
-# instance of them here and start up a listener on the specified
+# If any classes are specified here, the Service will create an
+# instance of them here and start up a listener on the specified
# port.
#
# Note that the handlers demonstrated are not very useful. You
@@ -95,7 +95,7 @@
services.XmlRpcService.handler.file =
org.apache.turbine.services.xmlrpc.util.FileHandler
services.XmlRpcService.paranoid = false
services.XmlRpcService.acceptClient = 192.168.1.*
-services.XmlRpcService.denyClient =
+services.XmlRpcService.denyClient =
]]></source>
@@ -117,7 +117,7 @@
{
/**
* We will test the following three operations:
- *
+ *
* 1) Send a file to a remove server
* 2) Get a file from a remote server
* 3) Remove a file to a remove server
1.2 +5 -5 jakarta-turbine-fulcrum/xdocs/howto/xslt-service.xml
Index: xslt-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/xdocs/howto/xslt-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xslt-service.xml 2001/12/17 16:31:36 1.1
+++ xslt-service.xml 2001/12/25 18:19:17 1.2
@@ -2,7 +2,7 @@
<document>
<properties>
- <title>Turbine Services - XSLT Service</title>
+ <title>Fulcrum Services - XSLT Service</title>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
@@ -25,7 +25,7 @@
<source><![CDATA[
# -------------------------------------------------------------------
-#
+#
# S E R V I C E S
#
# -------------------------------------------------------------------
@@ -35,12 +35,12 @@
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
-services.XSLTService.classname=org.apache.turbine.services.xslt.TurbineXSLTService
+services.XSLTService.classname=org.apache.fulcrum.xslt.TurbineXSLTService
.
.
.
# -------------------------------------------------------------------
-#
+#
# X S L T S E R V I C E
#
# -------------------------------------------------------------------
@@ -56,7 +56,7 @@
<p>
Please look at the
<strong>org.apache.turbine.modules.layouts.VelocityXslLayout</strong>
for an example usage pattern.
-</p>
+</p>
</section>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
