cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COCOON-1831) Passing parameters to sub calls
Date Fri, 28 Dec 2007 09:32:43 GMT

     [ https://issues.apache.org/jira/browse/COCOON-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Reinhard Poetz updated COCOON-1831:
-----------------------------------

    Affects version (Component): Parent values: Servlet Service Framework(10175). 
                    Description: 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. 
                        Summary: Passing parameters to sub calls  (was: Finish blocks-fw implementation)

> 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.


Mime
View raw message