[
https://jira.jboss.org/browse/SHRINKWRAP-204?page=com.atlassian.jira.plug...
]
Aslak Knutsen commented on SHRINKWRAP-204:
------------------------------------------
One should 'always expect' a RuntimeException, but that's not the point.
As you your self said: File systems are none atomic, so exceptions on operations like
openStream are used and expected by users and should be handled.
That being problems opening the stream or reading the stream, it is all expressed via
exceptions.
The API use IOExceptions for this, so why should we throw something unexpected from our
implementation ?
ArchiveFileSystem.openInputStream returns null on missing Asset,
should throw IOException
-----------------------------------------------------------------------------------------
Key: SHRINKWRAP-204
URL:
https://jira.jboss.org/browse/SHRINKWRAP-204
Project: ShrinkWrap
Issue Type: Bug
Components: ext-vfs3
Affects Versions: 1.0.0-alpha-10
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.0.0-alpha-11
Opening a InputStream to a non existing Asset should result in IOException
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira