[wildfly-dev] Jackson 1 and 2 coexistence
Bill Burke
bburke at redhat.com
Mon May 6 10:32:36 EDT 2013
On 5/6/2013 10:28 AM, David M. Lloyd wrote:
> On 05/06/2013 09:06 AM, Bill Burke wrote:
>> Jackson 2 has a different package name from Jackson 1, so they are
>> completely incompatible. My suggestion?
>>
>> * Ship with both jackson 1 and jackson 2 modules
>> * Ship with both Restasy jackson 1 and 2 providers
>> * Make Jackson2 the default Resteasy provider
>>
>> For resteasy-based apps, the negative is that anybody relying on
>> jackson1 apis directly will have to either upgrade (which I think is as
>> easy as changing package names) or manually set up the apropriate
>> jboss-module includes/excludes.
>>
>> Thoughts? Let me know if you have any objections to this approach as I
>> want to document this within Resteasy and push the appropriate changes
>> to Wildfly.
>
> Are RestEasy providers selected on a serverwide basis or by deployment?
>
There are implicit default imports for resteasy. Json (jackson) support
is one of them. Does that answer your question?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
More information about the wildfly-dev
mailing list