What do you all think of generating the uniqueId on the server side? The
question of uniqueness then becomes much, much easier. We could simply
store the id in a cookie cactus_test_id (like jsessionid) and have
subsequent requests pull the value of the cookie from the response and
resend it with th
isplay:
[echo] - Cactus Servlet Sample 20030625 -
[echo] java.class.path =
/home/rubys/jakarta/xml-commons/java/external/build/xml-apis.jar:/home/rubys/jakarta/xml-xerces2/java/build/xmlParserAPIs.jar:/home/rubys/jakarta/xml-xerces2/java/build/xercesImpl.jar:.:/usr/java/j2sdk1.4.1_
isplay:
[echo] - Cactus Servlet Sample 20030625 -
[echo] java.class.path =
/home/rubys/jakarta/xml-commons/java/external/build/xml-apis.jar:/home/rubys/jakarta/xml-xerces2/java/build/xmlParserAPIs.jar:/home/rubys/jakarta/xml-xerces2/java/build/xercesImpl.jar:.:/usr/java/j2sdk1.4.1_
cmlenz 2003/06/25 01:18:31
Modified:documentation/docs/xdocs/participating howto_build.xml
documentation/docs/xdocs sitemap.xml
Log:
Updates to the "Build from sources" doc (not yet complete)
Revision ChangesPath
1.8 +122 -76
jakarta-cactus/docume
cmlenz 2003/06/25 01:17:53
Modified:documentation/docs/skins/jakarta.apache.org/css apache.css
Log:
Remove the weird corners from headlines and table headers
Revision ChangesPath
1.15 +4 -6
jakarta-cactus/documentation/docs/skins/jakarta.apache.org/css/apache.
