*
 * @author mbechler
 *
 */
public class SMBProtocolDowngradeException extends CIFSException {

    /**
     * Serial version UID for serialization compatibility.
     */
    private static final long serialVersionUID = 1913365058349456689L;

    /**
     * Creates a new SMBProtocolDowngradeException with no message.
     */
    public SMBProtocolDowngradeException() {

import java.io.IOException;
import java.io.PrintWriter;
import java.io.StringWriter;

import jcifs.smb1.smb1.WinError;
import jcifs.smb1.util.Hexdump;

/**
 * DCE/RPC exception class for SMB1 compatibility
 */
public class DcerpcException extends IOException implements DcerpcError, WinError {

    static String getMessageByDcerpcError(final int errcode) {
        int min = 0;
        int max = DCERPC_FAULT_CODES.length;

	cli.BoolFlag{
		Name:   "compat",
		Usage:  "enable strict S3 compatibility by turning off certain performance optimizations",
		Hidden: true,
	},
	// This flag is hidden and to be used only during certain performance testing.
	cli.BoolFlag{
		Name:   "no-compat",
		Usage:  "disable strict S3 compatibility by turning on certain performance optimizations",
		Hidden: true,
	},
}

Not every module contributes to every runtime.

The core-runtime module defines each runtime:

- The target JVM for the runtime. Each runtime has its own JVM compatibility constraints.
- Some base services that are available to code hosted by the runtime. This varies by runtime.

import jcifs.internal.smb2.rdma.RdmaMemoryRegion;
import jcifs.internal.smb2.rdma.RdmaProvider;

/**
 * TCP fallback RDMA provider.
 *
 * This provider uses regular TCP connections but maintains the RDMA
 * interface for compatibility. It only supports send/receive operations
 * and does not provide true RDMA read/write capabilities.
 */
public class TcpRdmaProvider implements RdmaProvider {

    /**
     * Creates a new TCP RDMA provider instance

 */

package jcifs.internal.util;

/**
 * Utility class providing string manipulation methods for the jCIFS library.
 * Contains helper methods for string operations, including backported JDK functionality
 * for compatibility with older Java versions.
 */
public final class StringUtil {

    /**
     *
     */
    private StringUtil() {
    }

    /**

            <option value="$PROJECT_DIR$/build-logic-settings/configuration-cache-compatibility" />
            <option value="$PROJECT_DIR$/build-logic-settings/default-settings-plugins" />
            <option value="$PROJECT_DIR$/build-logic-settings/version-catalogs" />
            <option value="$PROJECT_DIR$/build-logic/binary-compatibility" />
            <option value="$PROJECT_DIR$/build-logic/build-update-utils" />

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

package jcifs.smb1.dcerpc;

/**
 * DCE/RPC protocol constants for SMB1 compatibility
 */
public interface DcerpcConstants {

    /**
     * NDR syntax UUID for DCE/RPC protocol
     */
    UUID DCERPC_UUID_SYNTAX_NDR = new UUID("8a885d04-1ceb-11c9-9fe8-08002b104860");

    /**

    val accepted: List<ReportMessage>
) {

    val isEmpty: Boolean
        get() = errors.isEmpty() && warnings.isEmpty() && information.isEmpty()

    fun toText() =
        StringBuilder("Binary compatibility\n").apply {
            listOf("Errors" to errors, "Warnings" to warnings, "Information" to information, "Accepted" to accepted).forEach { (name, list) ->
                if (list.isNotEmpty()) {

   * JUnit test case you are running under. To avoid failing in the face of an exception regardless
   * of JUnit version, implement a {@link SloppyTearDown} instead.
   *
   * <p>tl4j details: For backwards compatibility, {@code junit3.TearDownTestCase} currently does
   * not fail a test when an exception is thrown from one of its {@link TearDown} instances, but
   * this is subject to change. Also, {@code junit4.TearDownTestCase} will.
   *