[
https://issues.apache.org/jira/browse/JCLOUDS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199053#comment-14199053
]
Adrian Cole commented on JCLOUDS-770:
-------------------------------------
As I'm sure questions will arise.. why MockWebServer? Reason is that tests
based on MWS are resilient to design changes. Ex. we can completely replace how
annotations are processed without rewriting the test. Moreover, unlike
ExpectTest, MWS has no dependency on how jclouds represents http requests. That
means that even changes to our class structure around http requests can be made
without rewriting tests! JCLOUDS-771
> Stop depending on jclouds internals like RestAnnotationProcessor
> ----------------------------------------------------------------
>
> Key: JCLOUDS-770
> URL: https://issues.apache.org/jira/browse/JCLOUDS-770
> Project: jclouds
> Issue Type: Task
> Components: jclouds-core
> Reporter: Adrian Cole
> Labels: technical_debt
>
> Folks including me and [~diwaker] aren't in love with
> RestAnnotationProcessor. This class is a survivor of my naive attempt to
> process annotations based on knowledge I had in 2009. There are far better
> and cheaper ways to implement jclouds interfaces than this. However, we can't
> move off it until we stop depending on it!!
> Old jclouds interfaces, particularly s3, haven't been modernized in years.
> Eventhough new apis should know enough to write MockWebServer tests, no-one
> has ported the old tests that subclass BaseRestApiTest, which holds a
> reference to RestAnnotationProcessor.
> Let's use this issue to track complete migrating off a dependency on
> BaseRestApiTest. Note that in some cases (ahem vcloud, cloudservers, ahem),
> this is best accomplished by deleting the antique providers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
