[weld-dev] Does the generated bean proxy use SLF4J?

[Pete Muir]

No apologies needed, just wanting to make sure it got your attention in the Christmas period ;-)

On 30 Dec 2010, at 08:50, 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). 
> 
> Stuart
> 
> Sent from my iPhone
> 
> On 29/12/2010, at 20:51, Pete Muir <pmuir at redhat.com> wrote:
> 
>> Stuart?
>> 
>> On 28 Dec 2010, at 10:48, Sivakumar Thyagarajan wrote:
>> 
>>> Hi
>>> 
>>> A clarification requested. Does the generated bean proxy ever use SLF4J?
>>> 
>>> Earlier, I had added [1] 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 [2]. 
>>> 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.
>>> 
>>> Thanks
>>> --Siva.
>>> [1] 
>>> http://svnsearch.org/svnsearch/repos/GLASSFISH/search?author=sivakumart&filename=pom.xml#4296824472030
>>> [2] http://java.net/jira/browse/GLASSFISH-11683
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>> 
>> 
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
> 
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev