DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-794
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Trivial Trivial
Assignee: Unassigned
Reporter: Raman Gupta
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
DataNucleus Core

NPE during logging when plugin refers to non-existent extension point in OSGi

Created: 17/Dec/11 02:46 AM   Updated: 18/Feb/14 09:22 AM   Resolved: 17/Dec/11 09:12 AM
Component/s: None
Affects Version/s: 3.0.4
Fix Version/s: 3.0.5

File Attachments: 1. Text File NUCCORE-794.patch (0.8 kB)

 Description  « Hide
When a plugin is loaded and refers to a non-existent extension point, DataNucleus logs it at WARN level. However, this log statement results in an NPE when running in an OSGi environment, since it does extension.getPlugin().getManifestLocation().toString(). However, manifestLocation is always null in an OSGi environment (it is not set by OSGiPluginRegistry).

Sort Order: Ascending order - Click to sort in descending order
Raman Gupta added a comment - 17/Dec/11 02:46 AM
The attached patch removes the toString portion of this log statement which is unnecessary since that is done implicitly by the logger, and so solves the issue.

Andy Jefferson added a comment - 17/Dec/11 09:12 AM
SVN trunk has this now. Thx