[
https://issues.apache.org/jira/browse/CXF-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Liu updated CXF-3472:
---------------------------
Description:
Current, all response message processing of HTTPConduit is in the class
WrappedOutputStream, e.g. handleResponse(), and handleResponseInternal()
method. It is not very easy to extend HTTPConduit and override both method if
we want to add more functions during processing response. because the class
WrappedOutputStream need some input parameter and the its sub-class cannot get
these private properties.
Can cxf move both meothd from WrappedOutputStream class to HTTPConduit?
thanks.
David
was:
Current, all response message processing of HTTPConduit is in the class
WrappedOutputStream, e.g. handleResponse(), and handleResponseInternal()
method. It is not very easy to extend HTTPConduit and override both method if
we want to add more functions during processing response.
Can cxf move both meothd from WrappedOutputStream class to HTTPConduit?
thanks.
David
> Make HTTPConduit easy to extend and override
> --------------------------------------------
>
> Key: CXF-3472
> URL: https://issues.apache.org/jira/browse/CXF-3472
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: David Liu
>
> Current, all response message processing of HTTPConduit is in the class
> WrappedOutputStream, e.g. handleResponse(), and handleResponseInternal()
> method. It is not very easy to extend HTTPConduit and override both method if
> we want to add more functions during processing response. because the class
> WrappedOutputStream need some input parameter and the its sub-class cannot
> get these private properties.
> Can cxf move both meothd from WrappedOutputStream class to HTTPConduit?
> thanks.
> David
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
