[
https://issues.apache.org/jira/browse/OWB-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-377.
-------------------------------
Resolution: Fixed
I also had to fix a few logging invocations where the exception was the last
parameter instead of being 2nd.
> revise logging
> --------------
>
> Key: OWB-377
> URL: https://issues.apache.org/jira/browse/OWB-377
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: M4
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.0.0
>
>
> There are a few logging issues in our code currentla
> a) we do a bit too much info logging atm. For example
> > 18.03.2010 01:45:47 org.apache.webbeans.spi.ServiceLoader fireEvent
> > WARNUNG: Unable to find service with class name :
> > org.apache.webbeans.spi.TransactionService
> gets thrown at each user, even if he did intend to not use transactions.
> This should get logged as debug at most.
> b) our logger uses variable arguments. So
> > logger.debug("Resolving is successful with systemId : ", new
> > Object[]{systemId});
> should be written as
> > logger.debug("Resolving is successful with systemId : ", systemId);
> wrapping the parameters in an additional Object[] doesn't work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
