assertEquals("file:", protocolHelper.getFileProtocols()[0]);
        assertEquals("smb:", protocolHelper.getFileProtocols()[1]);
        assertEquals("smbx:", protocolHelper.getFileProtocols()[2]);

        assertTrue(protocolHelper.isValidFileProtocol("smbx://test"));

        protocolHelper.addFileProtocol("smbx");
        assertEquals(2, protocolHelper.getWebProtocols().length);

jcifs-ng will be a proper choice for many users. 
There are a lot of SMB devices in the world.
Some of them only work with the old jcifs library.
If you want to support many SMB devices, CodeLibs jcifs library will be helpful.
For example, since [Fess](https://github.com/codelibs/fess) needs to support many SMB devices, it uses this library.

import jcifs.internal.smb1.com.SmbComWriteResponse;
import jcifs.internal.smb2.info.Smb2SetInfoRequest;
import jcifs.internal.smb2.io.Smb2WriteRequest;
import jcifs.internal.smb2.io.Smb2WriteResponse;


/**
 * This <code>OutputStream</code> can write bytes to a file on an SMB file server.
 */

public class SmbFileOutputStream extends OutputStream {

import jcifs.internal.smb1.trans2.Trans2FindFirst2Response;
import jcifs.internal.smb2.ServerMessageBlock2;
import jcifs.internal.smb2.ioctl.Smb2IoctlRequest;
import jcifs.internal.smb2.ioctl.Smb2IoctlResponse;
import jcifs.internal.smb2.ioctl.ValidateNegotiateInfoRequest;
import jcifs.internal.smb2.ioctl.ValidateNegotiateInfoResponse;
import jcifs.internal.smb2.nego.Smb2NegotiateRequest;
import jcifs.internal.smb2.nego.Smb2NegotiateResponse;

import jcifs.SmbSession;
import jcifs.internal.smb1.com.SmbComClose;
import jcifs.internal.smb1.com.SmbComNTCreateAndX;
import jcifs.internal.smb1.com.SmbComNTCreateAndXResponse;
import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.smb2.create.Smb2CloseRequest;
import jcifs.internal.smb2.create.Smb2CreateRequest;
import jcifs.smb.SmbSessionInternal;
import jcifs.smb.SmbTransportInternal;
import jcifs.smb.SmbTreeInternal;

import java.util.EnumSet;
import java.util.Set;

import jcifs.internal.smb2.Smb2Constants;


/**
 * @author mbechler
 *
 */
public enum DialectVersion {

    /**
     * Legacy SMB1/CIFS
     */
    SMB1,

    /**
     * SMB 2.02 - Windows Vista+
     */
    SMB202(Smb2Constants.SMB2_DIALECT_0202),

    /**
     * SMB 2.1 - Windows 7/Server 2008R2
     */

                return cfg;
            }
        });

        MUTATIONS.put("smb1-noSigning", new TestMutation() {

            @Override
            public Map<String, String> mutate ( Map<String, String> cfg ) {
                cfg.put("jcifs.smb.client.maxVersion", "SMB1");
                cfg.put("jcifs.smb.client.signingPreferred", "false");

 */
package jcifs.internal.smb2.notify;


import java.util.ArrayList;
import java.util.List;

import jcifs.Configuration;
import jcifs.FileNotifyInformation;
import jcifs.internal.NotifyResponse;
import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.smb1.trans.nt.FileNotifyInformationImpl;
import jcifs.internal.smb2.ServerMessageBlock2Response;
import jcifs.internal.util.SMBUtil;

            /*
             * A word about communicating header info to andx smbs
             *
             * This is where we recursively invoke the provided andx smb
             * object to write it's parameter words and bytes to our outgoing
             * array. Incedentally when these andx smbs are created they are not
             * necessarily populated with header data because they're not writing

import jcifs.internal.smb1.SMB1SigningDigest;
import jcifs.internal.smb1.ServerMessageBlock;
import jcifs.internal.smb1.com.SmbComBlankResponse;
import jcifs.internal.smb1.com.SmbComLogoffAndX;
import jcifs.internal.smb1.com.SmbComNegotiateResponse;
import jcifs.internal.smb1.com.SmbComSessionSetupAndX;
import jcifs.internal.smb1.com.SmbComSessionSetupAndXResponse;
import jcifs.internal.smb1.com.SmbComTreeConnectAndX;