You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by cz...@apache.org on 2003/05/18 13:31:12 UTC
cvs commit: cocoon-2.1/src/documentation/xdocs/developing/webapps portal.xml session.xml
cziegeler 2003/05/18 04:31:12
Modified: src/documentation/xdocs/developing/webapps portal.xml
session.xml
Log:
Changing namespace form cocoon.apache.org/session to apache.org/cocoon/session
Revision Changes Path
1.2 +2 -2 cocoon-2.1/src/documentation/xdocs/developing/webapps/portal.xml
Index: portal.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/developing/webapps/portal.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- portal.xml 9 Mar 2003 00:07:46 -0000 1.1
+++ portal.xml 18 May 2003 11:31:11 -0000 1.2
@@ -1184,7 +1184,7 @@
customization view for a coplet. The following example dispalys a form for a
mail coplet which requires the configuration for a mail host, a user name and a
password.</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<!-- Define a form -->
<session:form name="popmail" method="POST">
<session:action>
@@ -1208,7 +1208,7 @@
<p>Writing the resource for the coplet is as easy. The coplet can use
the <em>getxml</em> command to retrieve to configuration from the
<em>portal</em> context:</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<!-- Get the configuration information out of the portal context -->
<!-- and feed it into the getmail command -->
<session:getmail>
1.2 +7 -7 cocoon-2.1/src/documentation/xdocs/developing/webapps/session.xml
Index: session.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/developing/webapps/session.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- session.xml 9 Mar 2003 00:07:46 -0000 1.1
+++ session.xml 18 May 2003 11:31:11 -0000 1.2
@@ -62,7 +62,7 @@
in the sitemap and can be used inside a document. All tags must be prefixed
with the session namespace. So the actual tag used in the document will read
<em><session:xxxx></em>. The current namespace URI for the session
- transformer is <em>"http://cocoon.apache.org/session/1.0"</em>.</p>
+ transformer is <em>"http://apache.org/cocoon/session/1.0"</em>.</p>
</s2>
<s2 title="Context-Tags">
<p>A context is basically an application specific block of XML data in
@@ -118,7 +118,7 @@
<p>The following example shows the use of several commands and in
particular how the <em>mergexml</em> command can be used to manipulate context
data.</p>
- <source><resource xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><resource xmlns:session="http://apache.org/cocoon/session/1.0">
<session:createcontext name="trackdemo"/>
<!-- build context data -->
<session:setxml context="trackdemo" path="/">
@@ -370,7 +370,7 @@
<p>The "form-handling-page" is a pipeline which is declared in the
sitemap and uses the session transformer. It could also read the following
xml:</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<forename>
<session:getxml context="request" path="/parameter/forename"/>
</forename>
@@ -383,7 +383,7 @@
inserts the value submitted by the user into the xml stream.</p>
<p>If you want to write the information in a session context, you must
wrap the whole xml inside a setxml:</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<session:setxml context="userdata" path="/user">
<forename>
<session:getxml context="request" path="/parameter/forename"/>
@@ -409,7 +409,7 @@
and in addition the information about where the submitted values should be
stored inside the session.</p>
<p>The example from the previous chapter could look like this:</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<session:form name="myform">
<session:action>the-next-page</session:action>
<session:content>
@@ -426,7 +426,7 @@
contains form values which should be stored in the specified context under the
given path. The session transformer transforms by removing the namespace and
the context attribute:</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<form action="the-next-page">
<inputxml name="forename" type="text"/>
<inputxml name="surname" type="text"/>
@@ -442,7 +442,7 @@
<p>For editing values - if the context already contains information
about the user - <em>inputxml</em> inserts the current value inside the tag. So
the xml streamed would after a second run would look like this:</p>
- <source><page xmlns:session="http://cocoon.apache.org/session/1.0">
+ <source><page xmlns:session="http://apache.org/cocoon/session/1.0">
<form action="the-next-page">
<inputxml name="forename" type="text">Walter</inputxml>
<inputxml name="surname" type="text">Walterson</inputxml>