[
https://issues.apache.org/jira/browse/JCR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1162.
--------------------------------
Resolution: Fixed
Fixed the issue in revision 585176. Instead of extra logging I made an
exception thrown by close() result in a RepositoryException being thrown as
there's no way to know how serious the problem is.
> Improve logging in NodeTypeRegistry.persistCustomNodeTypeDefs
> -------------------------------------------------------------
>
> Key: JCR-1162
> URL: https://issues.apache.org/jira/browse/JCR-1162
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core, nodetype
> Reporter: Martijn Hendriks
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 1.4
>
>
> When the closing of out in the finally block of persistCustomNodeTypeDefs
> throws an IOException this is ignored. At least some logging should take
> place, because an IOException here might still mean that the custom nodetype
> definitions were not stored correctly. This is the case, for instance, when a
> DatabaseFileSystem is used: the call to out.close triggers the SQL statement
> execution which causes an IOException if it fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
