<div dir="ltr"><div>Bill,<br><br>I know guys just don't want to say this, but you can expose configuration about implicit imports.<br>it is mostly up to subsystem developer what it wants to do.<br></div>And that would result in jax-rs subsystem actualy having some configuration at all :)<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 12, 2013 at 5:07 PM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
On 9/12/2013 10:54 AM, David M. Lloyd wrote:<br>
> On 09/12/2013 09:45 AM, Bill Burke wrote:<br>
>><br>
>><br>
>> On 9/12/2013 10:10 AM, David M. Lloyd wrote:<br>
>>> On 09/12/2013 08:11 AM, Bill Burke wrote:<br>
>>>> The whole JSON-JAXRS support is a *bleepin* mess....<br>
>>>><br>
>>>> * You have old users that want to use Jettison to generate JSON from JAXB.<br>
>>>> * You have new users that want to use Jackson to generate JSON from JAXB.<br>
>>>> * Jackson 1.x is a completely different Java package than Jackson 2.x.<br>
>>>> With that you have old users that want to use 1.x new users that want to<br>
>>>> use 2.x.<br>
>>>><br>
>>>> Given that, it would be nice to have one place where they can set up the<br>
>>>> default implicit imports that come with Resteasy/JAX-RS subsystem.<br>
>>>> Someplace where they could configure this without it being hardcoded so<br>
>>>> we can support older apps that are migrating to Wildfly . Quite<br>
>>>> honestly I scratch my head trying to figure out why you guys decided it<br>
>>>> was a good idea to hardcode implicit module imports.<br>
>>><br>
>>> Hey just be glad we don't have a flat class path :)<br>
>>><br>
>>> Is there any reason why all three should not be imported by default? (I<br>
>>> am completely ignorant of JAX-RS so forgive me if that's a dumb question.)<br>
>>><br>
>><br>
>> They conflict with one another as JAX-RS binds marshallers based on<br>
>> media type, target java class and target's annotations. Jettison and<br>
>> Jackson have different default JAXB->JSON mappings and there's no way to<br>
>> pick between the two without a special resteasy annotation. As for old<br>
>> vs. new Jackson, there's no way to determine which one to use if no<br>
>> Jackson annotations are being used. Its a cluster-bleep...<br>
><br>
> So that leaves us two options that I can think of:<br>
><br>
> 1. Add a switch to a per-deployment descriptor which indicates which (if<br>
> any) JSON strategy to use<br>
> 2. Add a switch to the jax-rs subsystem configuration which specifies<br>
> which to include by default<br>
><br>
> We could also do both. Either way though the name should be specified<br>
> in english (i.e. "jackson1"/"jackson2"/"jettison"/"none").<br>
><br>
<br>
</div></div>Argg....This is a very crappy approach. Why not just be able to<br>
configure the implicit imports of a subsystem. That makes much more<br>
sense than what you are suggesting.<br>
<div class="im HOEnZb"><br>
<br>
<br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>