[
https://issues.apache.org/jira/browse/FELIX-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149484#comment-13149484
]
Karl Pauls commented on FELIX-3219:
-----------------------------------
Well, the problem is that we can't assume that the jar file of the bundle is on
disc (or at least, not as simple as that) -- hence, we use this wrapper to be
able to work with any kind of content. I guess, one could be smart and switch
on the content (i.e., if it is pointing to a jar on disc), just make it be a
fileinputstream, otherwise (i.e., if it is a reference: to a dir) use the
bundeinputstream.
What is the issue you having on your vm (and what vm is it :-)?
> BundleInputStream class complexity
> ----------------------------------
>
> Key: FELIX-3219
> URL: https://issues.apache.org/jira/browse/FELIX-3219
> Project: Felix
> Issue Type: Improvement
> Components: Framework Security
> Affects Versions: framework.security-1.4.1
> Reporter: Andie Similon
> Priority: Minor
>
> What exactly is the purpose of the BundleInputStream class in the framework
> security package. Is there any reason why this was introduced? We are having
> issues with this class with our VM, when we replace it by a simple
> FileInputStream it seems to work fine.
--
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
