[jax-rs-spec users] [jsr339-experts] Re: Re: A couple of other questions

From: Sastry Malladi <>
Date: Tue, 20 Dec 2011 13:41:17 -0800 (PST)

Any thoughts/interest on my proposal/direction  ?


 From: Sastry Malladi <>
To: Marek Potociar <>
Cc: "" <>
Sent: Thursday, December 15, 2011 5:18 PM
Subject: [jax-rs-spec users] [jsr339-experts] Re: A couple of other questions

>> Do you have any concrete proposal in mind?

How about we add an "environment" parameter to the newClient() method on ClientFactory, so that when the caller invokes
Client client = ClientFactory.newClient("myEnv")

the implementations looks for a configuration file (say, filter-config.xml)  under "myEnv" resource folder using the current classloader, and registers those filters specified there, as if the user called client.configuration().register(..) for each of those.

This is the general idea, but can expand and give more details, if we want to go down this path.


 From: Marek Potociar <>
To: Sastry Malladi <>
Cc: "" <>
Sent: Saturday, December 10, 2011 12:14 PM
Subject: Re: [jsr339-experts] A couple of other questions

On 12/10/2011 02:21 AM, Sastry Malladi wrote:
> Client API
> Configuration of handlers/filters is done through configuration().register() - The order of execution depends on
> @BindingPriority.  How does a specific environment register certain client side filters by default, instead of each
> client application registering their own ? I guess I'm looking for  @GlobalBinding equivalent on the client side.
> Provide custom Client and Target classes, which registers these filters by default and have the client use these custom
> classes  ? A simpler way to "install" default filters would be good.

Do you have any concrete proposal in mind?

> Async API
>    In order to support this, do we require a servlet 3.x framework or is the jax-rs implementation expected to support
> the continuations (suspend/resume)  inherently ?

 functionality is not bound to servlet 3.x dependency.

> thanks,
> Sastry