*
 * @author mbechler
 */
public class CIFSContextWrapper implements CIFSContext {

    private final CIFSContext delegate;
    private Handler wrappedHandler;

    /**
     * Constructs a wrapper around the specified CIFS context.
     *
     * @param delegate
     *            context to delegate non-override methods to
     *
     */
    public CIFSContextWrapper(final CIFSContext delegate) {

import jcifs.smb.SmbRenewableCredentials;

/**
 * Context wrapper supplying alternate credentials
 *
 * @author mbechler
 *
 */
public final class CIFSContextCredentialWrapper extends CIFSContextWrapper implements CIFSContext {

    private Credentials creds;

    /**
     * Constructs a CIFS context wrapper with custom credentials.
     *
     * @param delegate the context to wrap
     * @param creds

 * allow to create such sub-contexts.
 *
 *
 * Implementors of this interface should extend {@link jcifs.context.BaseContext} or
 * {@link jcifs.context.CIFSContextWrapper} to get forward compatibility.
 *
 * @author mbechler
 *
 */
public interface CIFSContext {

    /**
     * Get a resource
     *
     * @param url the URL of the SMB resource

import org.slf4j.LoggerFactory;

import jcifs.context.SingletonContext;

/**
 * This class now contains only utilities for config parsing.
 *
 * We strongly suggest that you create an explicit {@link jcifs.context.CIFSContextWrapper}
 * with your desired config. It's base implementation {@link jcifs.context.BaseContext}
 * should be sufficient for most needs.
 *
 * If you want to retain the classic singleton behavior you can use