Hello,
Unless there is NOGO on this, I'll be committing the patch provided
tomorrow on issue:

   - https://bz.apache.org/bugzilla/show_bug.cgi?id=59038

To recap, we deprecated HC3.1 in 3.0 and announced it would be removed in
3.1 but we didn't remove it.
The only little issue I see in dropping it, is that we didn't deprecate (by
error) SOAP/XML-RPC Request:

   - http://jmeter.apache.org/usermanual/component_
   reference.html#SOAP/XML-RPC_Request
   
<http://jmeter.apache.org/usermanual/component_reference.html#SOAP/XML-RPC_Request>

although we wrote:

   - See Building a WebService Test Plan
   <http://jmeter.apache.org/usermanual/build-ws-test-plan.html> for up to
   date way of test SOAP and REST Webservices

But I'm personally in favor of dropping it for 3.2 as the only remaining
issue was the missing Pre-Emptive Basic Auth which has now been fixed in
HC4.

Regards

Philippe

On Monday, January 4, 2016, sebb <[email protected]> wrote:

> On 27 December 2015 at 17:39, Philippe Mouawad
> <[email protected]> wrote:
> > Hello,
> > I think it is time now that we definitely drop HC3.1 support in JMeter.
> > It hardens maintainability and hides some issues in test cases like Bug
> > 58773 and previously TestCookieManager tests.
> >
> > I think also that giving too much choice to users hardens the learning
> path.
> >
> > I suggest we start by deprecating in 2.14 the following components:
> >
> >    - SoapSampler, we should I think deprecate it already in 2.14 as the
> >    Soap Template covers its features in a more efficient way
> >    - HttpHC3Impl in documentation
> >    - HC3CookieHandler in documentation
>
> OK
>
> > And in next version drop:
> >
> >    - HTTPHC3Impl
> >    - SoapSampler
> >    - HTTPSampler2 used by SoapSampler
> >    - HC3CookieHandler
> >    - HttpHC3Impl
> >    - LoopbackHttpClientSocketFactory
> >    - SlowHttpClientSocketFactory
>
> OK
>
> >
> > --
> > Regards
> > Philippe
>

Reply via email to