[
https://issues.apache.org/jira/browse/COCOON-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487442
]
Daniel Fagerstrom commented on COCOON-2038:
-------------------------------------------
The explicit super call is because I didn't find any good way to call sitemaps
in a "call through" way long time ago when I implemented the first version of
the blocks fw. But of course it would be neater to not need to use an explicit
super call.
As the servlet service fw is supposed to work with any servlet the implicit
super call mechanism need to use general servlet mechanisms. One way would be
to call the base servlet and check for the status code of the http response
object. If it is "200 OK" and possibly some other responses in the 2xx (and
maybe 3xx) series, the response is just returned. If the response is "404 Not
Found" (and maybe for some response codes in the 4xx and 5xx series) the super
servlet is called. Otherwise the error response code is just returned.
The mechanism should probably be implemented somewhere in the
ServletServiceContext as most of the rest of the OO stuff is implemented there.
> Implement true Object Oriented approach for handling super calls
> ----------------------------------------------------------------
>
> Key: COCOON-2038
> URL: https://issues.apache.org/jira/browse/COCOON-2038
> Project: Cocoon
> Issue Type: Task
> Components: - Servlet service framework
> Reporter: Grzegorz Kossakowski
> Fix For: 2.2-dev (Current SVN)
>
>
> As discussed here: http://thread.gmane.org/gmane.text.xml.cocoon.devel/72317
> implementation of super calls should be changed to make it more OO-like.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
