On Thursday 30 December 2010 02:20 PM, Stuart Douglas wrote:
No, the proxies do not need slf4j. Sorry about the late response, I
have been on holidays and have not had regular Internet access (and spent a long time
sitting on the side of the road broken down on the way home).
Thanks for your response in the midst of your holidays. This helps. I
removed the slf4j deps in GlassFish's weld-integration-fragment bundle.
Sent from my iPhone
On 29/12/2010, at 20:51, Pete Muir<pmuir(a)redhat.com> wrote:
> On 28 Dec 2010, at 10:48, Sivakumar Thyagarajan wrote:
>> A clarification requested. Does the generated bean proxy ever use SLF4J?
>> Earlier, I had added  the SLF4J api and implementation packages to
>> the weld-integration-fragment bundle in GlassFish that exports all the
>> packages that are needed for bean proxies, but I see that preventing an
>> application component to use their own SLF4j api or impl binding .
>> Removing the SLF4J packages doesn't cause any issues with my tests and I
>> was wondering if SLF4J is used by the generated proxy class in any
>> other scenarios.
>>  http://java.net/jira/browse/GLASSFISH-11683