[jboss-as7-dev] jax-rs deployments have incomplete module imports

[Stuart Douglas]

Sent from my iPhone

On 13/09/2012, at 8:52, Bill Burke <bburke at redhat.com> wrote:

> 
> 
> On 9/12/2012 6:43 PM, Stuart Douglas wrote:
>>> If we changed the JaxrsDependencyProcessor to import Apache HC 4.1.
>>> How would the user upgrade to Apache HC 4.2?  Do they not have to
>>> create a new module for 4.2 and import it within their
>>> jboss-deployment-structure.xml?  Why not have them do one more step
>>> and work with the aggregate module instead?  They can always version
>>> the aggregate module too, right?  If they get used to working with an
>>> aggregate module, isn't it a lot easier for them to support multiple
>>> different versions of Resteasy for different applications?
>> 
>> The user should be able to exclude the Apache HC 4.1 (and any Resteasy
>> modules that depend on it) in jboss-deployment-structure.xml and then
>> bundle 4.2 and any other Resteasy modules directly in their application.
>> This way they do not have to actually modify the app server.
>> 
> 
> Jason also said "I just realized they could class filter the import though which would solve it. They can also take advantage of ordering."  Is that as good of a solution?  Then we have both a mechanism to define JAX-RS imports for the entire app server (instead of it being hardcoded) and a way to override a specific thing.
> 

That will work, it is just slightly more fiddely as class level filtering works on package names.

Stuart

> -- 
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com