hi,
I confirm this issue, i spotted it when i tried 2.4-SNAPSHOT (i ask
about it in another post to this list: *[Jersey] Re: Resource
init/destroy* but had no response).
I was hopping this will be fixed before the release...
The behavior i spotted was that only ONE resource or provider was
registered by package.
Guilhem Legal
Le 28/10/2013 15:00, Miles, Eric (CONT) a écrit :
> I have several Providers defined (ContainerRequestFilter,
> ExceptionMapper, etc) that are annotated with @Provider and were
> scanned in via ResourceConfig.packages(String…) in Jersey 2.3.1.
> After upgrading to Jersey 2.4, component scanning no longer works. I
> have to manually ResourceConfig.register(NameOfClass.class) to get
> those providers registered.
>
> Anyone else having this issue? Did anything change for package
> scanning that I need to be aware of?
>
> Thanks,
> Eric
>
> ------------------------------------------------------------------------
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates. The information
> transmitted herewith is intended only for use by the individual or
> entity to which it is addressed. If the reader of this message is not
> the intended recipient, you are hereby notified that any review,
> retransmission, dissemination, distribution, copying or other use of,
> or taking of any action in reliance upon this information is strictly
> prohibited. If you have received this communication in error, please
> contact the sender and delete the material from your computer.
>