[
https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554795
]
Rice Yeh commented on COCOON-1831:
----------------------------------
In my mind, iterating the call stack form the first call frame to the last call
frame to put values from each frame in a map ( which has value's name as key)
does have value from the later call frame over-write the previous frame's value
in the map. It is just so nature. So be honest, i do not really understand your
question. But, will just passing parameters from caller (you refer it as
'parent') satisfy the overriding nature I mentioned in
http://www.mail-archive.com/[email protected]/msg52250.html? If yes, then
go with your way, I might not really understand the code in servlet service. Or
we just have different concept on values' overriding.
In the following, i recite my example in
http://www.mail-archive.com/[email protected]/msg52250.html.
"Attribute values (here attribute refers to the general meaning, it includes
the parameters,
headers and attributes in request and the attributes in session and context)
in s2 can override values in s1. For example the value of an attribute a1 is
vs1 in s1, when s1 call s2, s2 might have attribute a1 with value vs2
because a1 is overridden (here, I am not sure whether it is correct to use
the word 'override'). However, for another block s3 called by s1 which does
not override a1, the value of a1 is still vs1"
Regards,
Rice
> Passing parameters to sub calls
> -------------------------------
>
> Key: COCOON-1831
> URL: https://issues.apache.org/jira/browse/COCOON-1831
> Project: Cocoon
> Issue Type: New Feature
> Components: - Servlet service framework
> Reporter: Reinhard Poetz
> Assignee: Reinhard Poetz
> Attachments: cocoon-servlet-service-impl.patch,
> cocoon-servlet-service-impl.patch
>
>
> When a servlet service request is created, parameters from the parent request
> are ignored. This means that the sub request is performed as a fresh and
> clean new call. This would avoid any possible side-effects, but is very
> inconvenient in practice because you don't even know the request header
> parameters from the original (external) request. Additionally you can only
> pass information which is part of the returned stream, which is e.g. a
> blocker to use the servlet protocol together with the control flow
> implementations. Those make use of special request parameters to transport
> the model ("bizdata") to the view layer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
