You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/11/21 15:27:14 UTC
DO NOT REPLY [Bug 24891] New: -
raw-request-param returns null when used with cinclude
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24891>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24891
raw-request-param returns null when used with cinclude
Summary: raw-request-param returns null when used with cinclude
Product: Cocoon 2
Version: Current CVS 2.1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: sitemap components
AssignedTo: dev@cocoon.apache.org
ReportedBy: jon.evans@misgl.com
As reported to users@cocoon
We have found what we believe to be a bug, when using raw-request-param
to get the value of a param passed via a cinclude.
Basically, the raw-request-param input module seems to work OK, unless
the param got passed via a cinclude, in which case it returns null.
We have built a test case for it, which I will attach (1595 bytes).
Archive: test.zip
Length Date Time Name
-------- ---- ---- ----
0 11-21-03 10:30 test/
46 11-21-03 10:11 test/testrequest.xml
1290 11-21-03 10:22 test/sitemap.xmap
617 11-21-03 10:23 test/testrequest.xsl
156 11-21-03 10:19 test/testcinclude.xml
-------- -------
2109 5 files
Instructions:
unzip this to a sitemap which mounts sub-sitemaps (e.g. the top
directory of a deployed cocoon)
browse to http://localhost:8080/cocoon/test/testrequest?test=foo+bar
you should get some output showing the value of "test", from both
request-param and raw-request-param.
Now browse to http://localhost:8080/cocoon/test/testrequestviacinclude
This matcher starts with an xml file containing a cinclude request for
cocoon:/testrequest?test=foo+bar+baz . This time, the output page will
indicate:
Value of param "test" from request input module: "foo bar baz"
Value of param "test" from raw-request input module: ""
Hopefully there is enough information there for someone to either
confirm that it is a bug, or point out my mistake.