[
https://issues.apache.org/jira/browse/CAY-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204429#comment-13204429
]
Wernke zur Borg commented on CAY-1655:
--------------------------------------
Ok, now I realised that I do not need an own DbAdapterFactory at all because
the default factory can instantiate my custom adapter. I only need to fill in
the adapter class in the modeler at the data node.
So far so good. Now I do get the logger injected, but I am still missing the
detailed queries in the log when I set the log level to DEBUG. However, this is
a different topic, so I am fine with this issue being closed.
Thank you Andrus!
> Logger injection to JdbcAdapter subclass does not work
> ------------------------------------------------------
>
> Key: CAY-1655
> URL: https://issues.apache.org/jira/browse/CAY-1655
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
> Affects Versions: 3.1M3
> Environment: Windows 7, MS Access, JdbcOdbc driver
> Reporter: Wernke zur Borg
>
> I created a custom subclass of JdbcAdapter for some special handling with MS
> Access. It is instantiated by a custom DbAdapterFactory subclass, which is
> configured as:
> Module m = new Module() {
> public void configure(Binder binder) {
>
> binder.bind(DbAdapterFactory.class).to(MyCustomDbAdapterFactory.class);
> }
> };
> Now the application runs into a NullPointerException in
> org.apache.cayenne.access.jdbc.SelectAction.performAction() where it says:
> adapter.getJdbcEventLogger()... (line 171)
> This means that the injection of the JdbcEventLogger "logger" in my
> superclass JdbcAdapter has not taken place. It might be important that also
> SelectAction has been subclassed with a custom SelectAction.
> The problem does not occur when I comment the binder.bind(...) line out.
> Workaround: Instantiate a CommonsJdbcEventLogger in the custom JdbcAdapter
> and assign it to the logger (it is protected). But this logger is not aware
> of the log4j log level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
