[VFS-621] Add API VFS.setManager(FileSystemManager)

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2
• Assignee: Gary D. Gregory
• Reporter: Gary D. Gregory
• Created: 09/Aug/16 23:55
• Updated: 11/Aug/16 17:01
• Resolved: 10/Aug/16 00:04

Description

Add API VFS.setManager(FileSystemManager).

Initialize VFS with the right class loader for OSGi types of scenarios to work. Must be called before any VFS APIs are called.

Instead of:

        final StandardFileSystemManager fsm = new StandardFileSystemManager();
        final ClassLoader classLoader = fsm.getClass().getClassLoader();
        fsm.setClassLoader(classLoader);
        try {
            FieldUtils.writeDeclaredStaticField(VFS.class, "instance", fsm, true);
            fsm.init();
        } catch (final FileSystemException | IllegalAccessException e) {
            ...
        }

do:

        final StandardFileSystemManager fsm = new StandardFileSystemManager();
        final ClassLoader classLoader = fsm.getClass().getClassLoader();
        fsm.setClassLoader(classLoader);
        VFS.setManager(fsm);
        fsm.init();

Issue Links

• is related to: VFS-424 VFS 2.0 class loading breaks in OSGi, regression from 1.0