[
https://issues.apache.org/jira/browse/FINERACT-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212023#comment-17212023
]
Michael Vorburger edited comment on FINERACT-1200 at 10/11/20, 8:13 PM:
------------------------------------------------------------------------
At least at startup, there's some logging:
{noformat}
11 jpa-pu WARN [main] openjpa.Runtime - An error occurred while registering
a ClassTransformer with PersistenceUnitInfo: name 'jpa-pu', root URL
[file:/Users/ptuomola/Development/apache-fineract/fineract/fineract-provider/bin/main|file:///Users/ptuomola/Development/apache-fineract/fineract/fineract-provider/bin/main].
The error has been consumed. To see it, set your openjpa.Runtime log level to
TRACE. Load-time class transformation will not be available.*
2020-10-11 22:38:51.991 INFO 17392 — [ main]
j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory
for persistence unit 'jpa-pu'
84 jpa-pu INFO [main] openjpa.jdbc.JDBC - Using dictionary class
"org.apache.fineract.infrastructure.core.domain.MySQLDictionaryCustom".*
1305 jpa-pu INFO [main] openjpa.Runtime - Starting OpenJPA 3.1.2*
1338 jpa-pu INFO [main] openjpa.jdbc.JDBC - Connected to MySQL version 0.1
using JDBC driver Drizzle-JDBC version 0.1.{noformat}
I think we can set the logger in META-INF/persistence.xml... need to give it a
try
was (Author: ptuomola):
At least at startup, there's some logging:
*11 jpa-pu WARN [main] openjpa.Runtime - An error occurred while
registering a ClassTransformer with PersistenceUnitInfo: name 'jpa-pu', root
URL
[file:/Users/ptuomola/Development/apache-fineract/fineract/fineract-provider/bin/main].
The error has been consumed. To see it, set your openjpa.Runtime log level to
TRACE. Load-time class transformation will not be available.*
2020-10-11 22:38:51.991 INFO 17392 --- [ main]
j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory
for persistence unit 'jpa-pu'
*84 jpa-pu INFO [main] openjpa.jdbc.JDBC - Using dictionary class
"org.apache.fineract.infrastructure.core.domain.MySQLDictionaryCustom".*
*1305 jpa-pu INFO [main] openjpa.Runtime - Starting OpenJPA 3.1.2*
*1338 jpa-pu INFO [main] openjpa.jdbc.JDBC - Connected to MySQL version 0.1
using JDBC driver Drizzle-JDBC version 0.1.*
I think we can set the logger in META-INF/persistence.xml... need to give it a
try
> OpenJPA logging to slf4j
> ------------------------
>
> Key: FINERACT-1200
> URL: https://issues.apache.org/jira/browse/FINERACT-1200
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Assignee: Petri Tuomola
> Priority: Major
> Fix For: 1.5.0
>
>
> FINERACT-1168 raises that, among others, OpenJPA currently logs directly to
> STDOUT should be routed to slf4j.. while I've noticed the related myself, I
> have not seen any (run time, not build time) output from OpenJPA -
> [~ptuomola] do you have any specific example of what you meant?
> Either way, this should be possible simply by setting {{openjpa.Log}} to
> {{slf4j}} "somewhere", according to
> https://openjpa.apache.org/builds/3.1.2/apache-openjpa/docs/index.html#ref_guide_logging_slf4j.
> Where is the "appropriate" place to set such properties?
> Of course, if we do FINERACT-849, then this becomes a moot point.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
