[
https://issues.apache.org/jira/browse/FELIX-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542754#comment-16542754
]
Karl Pauls commented on FELIX-5886:
-----------------------------------
Yes, it looks like we log a little to aggressively in case of a referenced
exploded dir. We should only log an error if we can't load the bytes of an
existing entry for some reason but _not_ if the entry doesn't exit at all.
Oh well, at a minimum, it only looks ugly because of the error log message - it
doesn't impact anything else (except having ugly log messages when nothing
really happened). For now, these can be ignored.
Good find - thanks a lot for reporting!
> Error logged by
> org.apache.felix.framework.BundleWiringImpl.getClassByDelegation
> --------------------------------------------------------------------------------
>
> Key: FELIX-5886
> URL: https://issues.apache.org/jira/browse/FELIX-5886
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-6.0.0
> Reporter: Christian Schneider
> Assignee: Karl Pauls
> Priority: Minor
> Fix For: framework-6.0.1
>
>
> I just tried to run the tests of felix systemready against the current felix
> framework 6.0.0. I get a lot of error log messages like below. The tests
> still succeed though.
>
> ERROR: DirectoryContent: Unable to read bytes for file
> org/osgi/service/http/context/ServletContextHelper.class from file
> /Users/cschneid/checkout/felix-trunk/systemready/target/classes/org/osgi/service/http/context/ServletContextHelper.class
> For the full stack trace see:
> [https://paste.apache.org/42g8]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
