Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates
 209.85.215.169 as permitted sender)
Message-ID: <4ED79E7D.1040504@gmail.com>
Date: Thu, 01 Dec 2011 15:34:21 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: dev@cxf.apache.org
Subject: Re: [proposal] Cross-Origin JAX-RS annotations
References: 
 <CALhtWkcoE6vdH+8PWG_fQWxfRrOgkmcsHLUJC551VAJ5n23OhA@mail.gmail.com>
In-Reply-To: 
 <CALhtWkcoE6vdH+8PWG_fQWxfRrOgkmcsHLUJC551VAJ5n23OhA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 01/12/11 14:51, Benson Margulies wrote:
> I propose to add the following
>
> @CorsAllowAllOrigins
> @CorsAllowOrigins(  "origin1.", ... "originN" )
> @CorsAllowMethods( "meth1" ... "methn" )
> @CorsExposeMethods( ... )
> @CorsMaxAge(integer)
> @CorsAllowCredentials(boolean)
>
> and make the filter look for them on resources and classes in the usual way.
>
> Any objections?

Can we collapse it all into a single annotation but with many properties ?
@Cors(origins = "...",
       methods = "a b c"
       allowCredentials = true
       )

I'd prefer if possible to avoid the explosion of annotations.

Re @CorsAllowMethods( "meth1" ... "methn" ) (or methods = "a b") - is it 
HTTP methods ?
Then how it work on a method annotated with say @POST ? May be it should 
be a single method value only ?
Re CorsAllowOrigins, is it relative URIs ? We'd probably need to think 
of introducing properties such as absolute.uri, etc, to be reused by 
other annotation such as SchemaLocation & XMLInstruction

Thanks, Sergey