cziegeler 2003/07/04 03:44:18
Modified:
src/blocks/session-fw/java/org/apache/cocoon/webapps/session/context
StandardSessionContextProvider.java
src/blocks/session-fw/conf session.xconf
src/documentation/xdocs/developing/webapps session.xml
Removed:
src/blocks/session-fw/java/org/apache/cocoon/webapps/session/context
ResponseSessionContext.java
Log:
Removing response context
Revision Changes Path
1.4 +1 -5
cocoon-2.1/src/blocks/session-fw/java/org/apache/cocoon/webapps/session/context/StandardSessionContextProvider.java
Index: StandardSessionContextProvider.java
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/session-fw/java/org/apache/cocoon/webapps/session/context/StandardSessionContextProvider.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- StandardSessionContextProvider.java 23 May 2003 12:13:13 -0000
1.3
+++ StandardSessionContextProvider.java 4 Jul 2003 10:44:17 -0000
1.4
@@ -101,10 +101,6 @@
context = new RequestSessionContext();
context.setup(name, null, null);
((RequestSessionContext)context).setup( objectModel,
this.manager );
- } else if ( name.equals(SessionConstants.RESPONSE_CONTEXT) ) {
- context = new ResponseSessionContext();
- context.setup(name, null, null);
- ((ResponseSessionContext)context).setup( objectModel );
}
objectModel.put(this.getClass().getName()+name, context);
}
1.4 +0 -2 cocoon-2.1/src/blocks/session-fw/conf/session.xconf
Index: session.xconf
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/blocks/session-fw/conf/session.xconf,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- session.xconf 23 May 2003 12:13:13 -0000 1.3
+++ session.xconf 4 Jul 2003 10:44:18 -0000 1.4
@@ -19,8 +19,6 @@
<session-context-providers>
<component-instance name="request"
class="org.apache.cocoon.webapps.session.context.StandardSessionContextProvider"/>
- <component-instance name="response"
-
class="org.apache.cocoon.webapps.session.context.StandardSessionContextProvider"/>
<component-instance name="temporary"
class="org.apache.cocoon.webapps.session.context.StandardSessionContextProvider"/>
</session-context-providers>
1.3 +2 -39
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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- session.xml 18 May 2003 11:31:11 -0000 1.2
+++ session.xml 4 Jul 2003 10:44:18 -0000 1.3
@@ -27,7 +27,7 @@
the session transformer.</p>
<p>The chapter "Special Contexts" explains some special
contexts which do not require a session. They are available
everytime. These
- special contexts are the request context, the response context and
the
+ special contexts are the request context and the
temporary context.</p>
</s1>
<s1 title="Session Tracking">
@@ -195,7 +195,7 @@
<s1 title="Special Contexts">
<p>Cocoon creates and maintains special contexts that allow the
applications to access the environment. This allows the read-only
access
- to such things as the current request or the response using the same
XPath
+ to such things as the current request using the same XPath
commands previously described. These context do not require any
session, they
are always available and change on every request.</p>
<s2 title="The Request Context - Accessing the Environment, Part One">
@@ -291,43 +291,6 @@
<isRequestedSessionIdFromCookie>value</isRequestedSessionIdFromCookie>
<isRequestedSessionIdFromCookie>value</isRequestedSessionIdFromCookie>
<isRequestedSessionIdValid>value</isRequestedSessionIdValid></source>
- </s2>
- <s2 title="The Response Context - Accessing the Environment, Part Two">
- <p>The response context is an XML description of the current
- (HTTP) response. This context is a special write only context that
can be
- accessed with the usual commands:</p>
- <p><em><session:setxml context="response"
- path="/header"/></em></p>
- <p>This command will be removed from the XML and the information will
- be added to the response. Headers and cookies can be
- added using the response context .</p>
- <s3 title="Adding headers">
- <p>Headers can be added either by <em>setxml</em> or by
- <em>appendxml</em>. If <em>setxml</em> is used, the header with
the name gets
- the given value, regardless if the header had any value
beforehand or not. If
- <em>appendxml</em> is used the value will be added.</p>
- <source><session:setxml context="response"
path="/header/headername">The value</session:setxml>
-
- or
-
-<session:appendxml context="response" path="/header/headername">The
value</session:appendxml></source>
- </s3>
- <s3 title="Adding cookies">
- <p>Cookies can be added either by setxml or by appendxml. There is
- no difference between these commands.</p>
- <source><session:setxml context="response" path="/cookie">
- <!-- Now follows the cookie definition -->
- <name>The cookie name</name>
- <value>The value of the cookie</value>
- <!-- The following are optional -->
- <path>value</path>
- <domain>value</domain>
- <secure>true or false</secure>
- <comment>value</comment>
- <maxAge>value</maxAge>
- <version>value</version>
-</session:setxml></source>
- </s3>
</s2>
<s2 title="The Temporary Context">
<p>The temporary context with the name <em>"temp"</em> is available
on
