Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some osgi doc. #35

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Some osgi doc. #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,25 @@ Jimfs also supports creating file systems that, for example, use Windows-style p
extent) behavior. In general, however, file system behavior is modeled after UNIX and may not
exactly match any particular real file system or platform.

OSGi considerations
-----------------

The SPI mechanism that registers file system providers is not
OSGi-friendly. It will load the provider class into the system class
loader, and then if you try to use `Paths.get(URI)` from inside your
OSGi code, you'll fail with an `IllegalAccessException`.

There are two ways around this. In spite of the fact that the Jimfs
jar has full OSGi metadata, you can set up the `com.google.common.jimfs`
as part of the system bundle. This is, by far, the most convenient if
you are just using Jimfs for testing.

Your alternative is to never use `Paths.get(URI)` or any other API
that uses the SPI to obtain the file system provider. If you always
create your own `FileSystem` objects and call `getPath(...)` on them,
it all works fine.


License
-------

Expand Down