At the current state all the logging messages generated by EclipseLink are
ignored by slf4j, this means that they are not stored into the log file.
The main problem derived from here is that if we try to bring up two different
instances of the pipeline it will hang due to a derby error. These err messages
never get stored into the logging file (it's shown in the terminal if the ws
was launched manually though).
Here there is a wrapper to use Slf4j as logger for EclipseLink.
https://gist.github.com/msosvi/1325764
The main issue is that now we must have explicit dependencies to EclipseLink in
the poms somewhere, maybe this is not a big deal.
Original issue reported on code.google.com by capitan....@gmail.com on 5 Apr 2013 at 2:53
Original issue reported on code.google.com by
capitan....@gmail.comon 5 Apr 2013 at 2:53