<div dir="ltr"><div>WildFly 10 and EAP7 both use jackson2 as default providers.<br></div>jackson1 is still there but you need to explicitly enable it.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 26, 2016 at 11:45 PM, Alessio Soldano <span dir="ltr"><<a href="mailto:asoldano@redhat.com" target="_blank">asoldano@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Il 26/09/2016 22:47, Ron Sigal ha scritto:<br>
> I see in <a href="https://access.redhat.com/articles/2158031" rel="noreferrer" target="_blank">https://access.redhat.com/<wbr>articles/2158031</a> "JBoss Enterprise<br>
> Application Platform (EAP) 7 Included Modules" that jackson modules are<br>
> listing as "private" and jackson2 modules are "public".<br>
><br>
> Is that also true for Wildfly 10? I'm not sure how to tell. I see,<br>
> though, that<br>
> <a href="https://docs.jboss.org/author/display/WFLY10/Implicit+module+dependencies+for+deployments" rel="noreferrer" target="_blank">https://docs.jboss.org/author/<wbr>display/WFLY10/Implicit+<wbr>module+dependencies+for+<wbr>deployments</a><br>
> references org.jboss.resteasy.resteasy-<wbr>jackson-provider.<br>
><br>
> What I'm asking, really, is: Do we need to support jackson?<br>
</span>Considering Jackson 2 was released in March 2012, I would say we should<br>
start moving away from jackson 1.x... (excluding the module in WildFly?<br>
marking it as deprecated?)<br>
<br>
As for the implicit module dependencies, I usually go and check the<br>
code; for jaxrs subsystem that's in<br>
org.jboss.as.jaxrs.deployment.<wbr>JaxrsDependencyProcessor (see the<br>
addDependency calls in deploy method).<br>
<span class=""><br>
> Also, I've been meaning to suggest that we do away with<br>
> resteasy-jboss-modules-<<wbr>version>.zip(for AS 7) and rename<br>
> resteasy-jboss-modules-wf8-<<wbr>version>.zip to<br>
> resteasy-jboss-modules-wf-<<wbr>version>.zip (that is, get rid of the "8" in<br>
> "wf8").<br>
</span>+1, I would have done that in the very next future, so feel free to go<br>
ahead on this :-)<br>
<br>
<br>
This said, going back to RESTEASY-1486, please see my first comment<br>
there. I believe JacksonJsonpInterceptor / Jackson2JsonpInterceptor is<br>
not enabled by default, despite the jackson / jackson2 modules being<br>
implicitly added as dependencies to the user deployments [1]. The<br>
META-INF/services/<a href="http://javax.ws.rs">javax.ws.rs</a>.<wbr>ext.Providers in there does not list the<br>
jsonp interceptor, so I believe the user needs to explicitly ask for the<br>
provider to be installed (in the web.xml or programmatically). Am I wrong?<br>
<br>
Cheers<br>
Alessio<br>
<br>
<br>
[1] note, the module dependency that's added to the deployment in the<br>
code has export=false.<br>
<br>
><br>
> -Ron<br>
<div class="HOEnZb"><div class="h5">><br>
<br>
______________________________<wbr>_________________<br>
resteasy-dev mailing list<br>
<a href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/resteasy-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/resteasy-dev</a><br>
</div></div></blockquote></div><br></div>