This jira is about using LocalResteasyProviderFactory instead of ResteasyProviderFactoryImpl in following methods:

• ResteasyClientBuilderImpl.withConfig(...): the change allow us to save memory since LocalResteasyProviderFactory is designed to use NOOPServerHelper

• ResteasyClientBuilderImpl.providerFactory(...): Actually since the method argument is a ResteasyProviderFactory, it can be either a LocalResteasyProviderFactory or a ResteasyProviderFactoryImpl. In first case there is nothing to say, but in the second case there will be many issues such as:

• more memory consumption on every provider registration since ResteasyProviderFactoryImpl does not take advanatage of NOOPServerHelper
• ResteasyClientBuilderImpl.getConfiguration().getRuntimeType() will return RuntimeType.SERVER instead of RuntimeType.CLIENT