RE: Request parameters in a cocoon:/
In my experience the request parameters seem to be preserved. I am using the interpreted sitemap (not sure if that makes a difference) and have several places in my sitemap where I am certain they are working. For example: map:match pattern=*.xsp map:generate type=serverpages src=xsp/(1).xsp/ map:transform src=stylesheets/copySelf.xsl / map:serialize type=xml/ /map:match map:match pattern=bigPage map:aggregate element=page map:part src=cocoon:/data1.xsp/ map:part src=cocoon:/data2.xsp/ map:part src=cocoon:/data3.xsp/ /map:aggregate map:transform src=stylesheets/bigPage.xsl / map:serialize / /map:match -Original Message- From: ROSSEL Olivier [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 5:43 AM To: '[EMAIL PROTECTED]' Subject: Request parameters in a cocoon:/ When you call a cocoon:/ from your pipeline, the sitemap calls itself. But inside this new call, you lose the initial request parameters. Is there a way to set new request-parameters for the cocoon:/ call? Or keep the intial request parameters when the sitemap calls itself? This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameters in a cocoon:/
map:match pattern=*.xsp map:generate type=serverpages src=xsp/(1).xsp/ map:transform src=stylesheets/copySelf.xsl / map:serialize type=xml/ /map:match map:match pattern=bigPage map:aggregate element=page map:part src=cocoon:/data1.xsp/ map:part src=cocoon:/data2.xsp/ map:part src=cocoon:/data3.xsp/ /map:aggregate map:transform src=stylesheets/bigPage.xsl / map:serialize / /map:match My quiestion is that if I send this URl to Cocoon: http://.../bigPage?foo=1bar=0 Will I be able to retrieve those data in the copySelf.xsl? (defining use-stylesheet-parameters for it, of course) This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameters in a cocoon:/
Good question -- I have not tried that scenario. As a workaround, instead of extracting request parameters from a stylesheet, you could something like this in the xsp fooxsp:exprrequest.getParameter(foo)/xsp:expr/foo barxsp:exprrequest.getParameter(bar)/xsp:expr/bar and use XSLT to get the params during transformation. -Original Message- From: ROSSEL Olivier [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 11:26 AM To: '[EMAIL PROTECTED]' Subject: RE: Request parameters in a cocoon:/ My quiestion is that if I send this URl to Cocoon: http://.../bigPage?foo=1bar=0 Will I be able to retrieve those data in the copySelf.xsl? (defining use-stylesheet-parameters for it, of course) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameters in a cocoon:/
Good question -- I have not tried that scenario. As a workaround, instead of extracting request parameters from a stylesheet, you could something like this in the xsp fooxsp:exprrequest.getParameter(foo)/xsp:expr/foo barxsp:exprrequest.getParameter(bar)/xsp:expr/bar and use XSLT to get the params during transformation. I think that a cocoon:/ call resets all the requestParameters. It seems that you can retrieve them if you manage to include them as *part of* the URL of the cocoon:/. This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request parameters in a cocoon:/
ROSSEL Olivier wrote: Good question -- I have not tried that scenario. As a workaround, instead of extracting request parameters from a stylesheet, you could something like this in the xsp fooxsp:exprrequest.getParameter(foo)/xsp:expr/foo barxsp:exprrequest.getParameter(bar)/xsp:expr/bar and use XSLT to get the params during transformation. I think that a cocoon:/ call resets all the requestParameters. Maybe, but it should not! Its purpose is to create a new request with old AND new parameters (AFAIU) It seems that you can retrieve them if you manage to include them as *part of* the URL of the cocoon:/. That works great. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameters in a cocoon:/
I think that a cocoon:/ call resets all the requestParameters. Maybe, but it should not! Are you sure? Its purpose is to create a new request with old AND new parameters (AFAIU) Well, if you have ideas about how I can pass NEW request parameters for the cocoon:/ call, I am really interested. Using a GET-style URL (cocoon:/toto.xsp?foo=1) fails for me (C2.0.2). This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request parameters in a cocoon:/
Modifying Ryan's example a little bit...
map:match pattern=*.xsp
map:generate type=serverpages src=xsp/(1).xsp/
map:transform src=stylesheets/copySelf.xsl
map:parameter name=use-request-parameters value=true /
/map:transform
map:serialize type=xml/
/map:match
map:match pattern=bigPage
map:act type=request
map:parameter name=parameters value=true /
map:aggregate element=page
map:part src=cocoon:/data1.xsp{requestQuery}/
map:part src=cocoon:/data2.xsp{requestQuery}/
map:part src=cocoon:/data3.xsp{requestQuery}/
/map:aggregate
/map:act
map:transform src=stylesheets/bigPage.xsl /
map:serialize /
/map:match
This passes the original request parameters to all of the cocoon:/ calls
and allows you to use them in the copySelf stylesheet.
I hope this helps.
- Lee
-Original Message-
From: ROSSEL Olivier [mailto:[EMAIL PROTECTED]]
Sent: October 16, 2002 10:26 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Request parameters in a cocoon:/
map:match pattern=*.xsp
map:generate type=serverpages src=xsp/(1).xsp/
map:transform src=stylesheets/copySelf.xsl /
map:serialize type=xml/
/map:match
map:match pattern=bigPage
map:aggregate element=page
map:part src=cocoon:/data1.xsp/
map:part src=cocoon:/data2.xsp/
map:part src=cocoon:/data3.xsp/
/map:aggregate
map:transform src=stylesheets/bigPage.xsl /
map:serialize /
/map:match
My quiestion is that if I send this URl to Cocoon:
http://.../bigPage?foo=1bar=0
Will I be able to retrieve those data in the copySelf.xsl?
(defining use-stylesheet-parameters for it, of course)
This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management and
security reasons. This access is controlled under Regulation of
Investigatory Powers Act 2000, Lawful Business Practises.
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
