[rules-dev] Use of java.util.logging.Logger in JPAVariablePersister

[Salaboy]

By the way I've already remove that class in the trunk. 

- CTO @ http://www.plugtree.com
- MyJourney @ http://salaboy.wordpress.com
- Co-Founder @ http://www.jbug.com.ar
- Mauricio "Salaboy" Salatino -

On 22/10/2010, at 03:49, Antoine Toulme <antoine at lunar-ocean.com> wrote:

> OK!
> 
> On Thu, Oct 21, 2010 at 21:04, Mark Proctor <mproctor at codehaus.org> wrote:
> On 22/10/2010 05:47, Antoine Toulme wrote:
>> 
>> Hi,
>> 
>> I thought Drools was standardizing over slf4j. Is there a reason why a java.util.logging.Logger class is used ?
>> 
>> Here is some of the code:
>> Logger.getLogger(JPAVariablePersister.class.getName()).log(Level.SEVERE, null, t);
>> 
>> Should slf4j be used instead ? Note it's used by JtaTransactionManager and SingleSessionCommandService in the         same project.
> Just missed code, feel free to replace.
> 
> Mark
>> 
>> Thanks,
>> 
>> Antoine
>> 
>> _______________________________________________
>> rules-dev mailing list
>> rules-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-dev
> 
> 
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
> 
> 
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20101022/46d1e5c1/attachment-0001.html