users@jersey.java.net

Re: [Jersey] added jersey-scala library to trunk

From: James Strachan <james.strachan_at_gmail.com>
Date: Mon, 27 Apr 2009 16:33:08 +0100

2009/4/27 Paul Sandoz <Paul.Sandoz_at_sun.com>:
> On Apr 27, 2009, at 3:00 PM, James Strachan wrote:
>>>
>>> I liked your solution, we discussed a while ago, for a single
>>> META-INF/services file that contains a list of classes.
>>>
>>> Strictly speaking it is not necessary to have a META-INF/services file
>>> specific to the interface of what is being implemented. It is sort of a
>>> hangover from how things were initially implemented.
>>
>> I wonder if we had something like a text file containing package names
>> called
>>
>>  META-INF/services/jersey-packages
>>
>> which Jersey could then load all of them it can see on the classpath
>> and use them to search through for resource beans & entity providers
>> and whatnot?
>>
>> Then in effect the packages listed in each
>> META-INF/services/jersey-packages file are concatenated with whatever
>> the user configures in the com.sun.jersey.config.property.packages
>> property?
>>
>
> Yes. I think supporting a jersey-classes property as well is useful because
> the package scanning utilizes techniques that might not work if a special
> class loader is utilized (e.g. one that does not load classes from files).
>
> I am guessing for framework-type libraries it is not as useful to declare a
> package as is the case for an end developer.
>
> Could you log an issue?

Done
https://jersey.dev.java.net/issues/show_bug.cgi?id=282
-- 
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/