I've asked this in the user forum too:<div><a href="https://community.jboss.org/thread/213370?tstart=0">https://community.jboss.org/thread/213370?tstart=0</a><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 14 November 2012 14:33, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
there is pros and cons in both (think spring (java config VS verbose xml)<br>
<br>
I guess if we keep it minimal a xml file is fine...<br>
<br>
-M<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Nov 14, 2012 at 2:22 PM, Daniel Bevenius<br>
<<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
> Thanks for the feedback guys!<br>
> Going to wait a little longer so everyone who wants to can have a say.<br>
><br>
><br>
> On 14 November 2012 14:16, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
>><br>
>> Hi firends,<br>
>> My preference goes for XML config. CORS is more a "external" config aspect<br>
>> rather than being part of the "domain/core".<br>
>> Seb<br>
>><br>
>><br>
>><br>
>> On Wed, Nov 14, 2012 at 12:26 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>><br>
>> wrote:<br>
>>><br>
>>> Hi my friend, at first glance looks like the XML option is more readable.<br>
>>><br>
>>> But before we move forward I'd like to hear more opinions about it.<br>
>>><br>
>>><br>
>>> --<br>
>>> "The measure of a man is what he does with power" - Plato<br>
>>> -<br>
>>> @abstractj<br>
>>> -<br>
>>> Volenti Nihil Difficile<br>
>>><br>
>>><br>
>>><br>
>>> On Tuesday, November 13, 2012 at 2:15 PM, Daniel Bevenius wrote:<br>
>>><br>
>>> > To help clarify the options here the following gist contains examples<br>
>>> > of the two suggestions provided so far:<br>
>>> > <a href="https://gist.github.com/4066691" target="_blank">https://gist.github.com/4066691</a><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > On 13 November 2012 16:49, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a><br>
>>> > (mailto:<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>)> wrote:<br>
>>> > > > i dislike xml configuration files, so i would vote for an<br>
>>> > > > Annotation.<br>
>>> > ><br>
>>> > > Yeah, I agree and we are avoiding any xml right now.<br>
>>> > > So, how about we provide some hopefully good defaults for CORS and<br>
>>> > > then users can provide there own @Producer. We will provide at builder api<br>
>>> > > to create the config instance so it won't be a lot of work for users.<br>
>>> > ><br>
>>> > > Should CORS be enabled by default?<br>
>>> > ><br>
>>> > ><br>
>>> > > On 13 November 2012 13:35, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a><br>
>>> > > (mailto:<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>)> wrote:<br>
>>> > > ><br>
>>> > > > On Nov 13, 2012, at 4:18 AM, Daniel Bevenius<br>
>>> > > > <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a> (mailto:<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>)> wrote:<br>
>>> > > > > I'm working on adding CORS support there are several things that<br>
>>> > > > > can be configured in this case. Below is an example of the options that are<br>
>>> > > > > currently available:<br>
>>> > > > > public interface CorsConfiguration {<br>
>>> > > > > public abstract boolean isCorsSupportEnabled();<br>
>>> > > > > public abstract boolean exposeHeaders();<br>
>>> > > > > public abstract String getExposeHeaders();<br>
>>> > > > > public abstract boolean anyOrigin();<br>
>>> > > > > public abstract boolean allowCookies();<br>
>>> > > > > public abstract boolean hasMaxAge();<br>
>>> > > > > public abstract long getMaxAge();<br>
>>> > > > > public abstract Set<String> getValidRequestMethods();<br>
>>> > > > > public abstract Set<String> getValidRequestHeaders();<br>
>>> > > > > }<br>
>>> > > > > How do we want users to configure these configuration options?<br>
>>> > > > > Using a CDI annotation with "sensible" default values or specify them in<br>
>>> > > > > web.xml (<a href="http://web.xml" target="_blank">http://web.xml</a>)?<br>
>>> > > ><br>
>>> > > ><br>
>>> > > > i dislike xml configuration files, so i would vote for an<br>
>>> > > > Annotation. but thats personal preference<br>
>>> > > ><br>
>>> > > ><br>
>>> > > > > cheers,<br>
>>> > > > > /Dan<br>
>>> > > > ><br>
>>> > > > ><br>
>>> > > > > _______________________________________________<br>
>>> > > > > aerogear-dev mailing list<br>
>>> > > > > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>> > > > > (mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>)<br>
>>> > > > > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>> > > ><br>
>>> > > ><br>
>>> > > ><br>
>>> > > > _______________________________________________<br>
>>> > > > aerogear-dev mailing list<br>
>>> > > > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> (mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>)<br>
>>> > > > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>> > ><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > aerogear-dev mailing list<br>
>>> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> (mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>)<br>
>>> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> aerogear-dev mailing list<br>
>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Matthias Wessendorf<br>
<br>
blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>