Java ServerPipeAssemblerContext类代码示例

import com.sun.xml.internal.ws.api.pipe.ServerPipeAssemblerContext; //导入依赖的package包/类
/**
 * On Server-side, HandlerChains cannot be changed after it is deployed.
 * During assembling the Pipelines, we can decide if we really need a
 * SOAPHandlerPipe and LogicalHandlerPipe for a particular Endpoint.
 */
public Pipe createServer(ServerPipeAssemblerContext context) {
    Pipe head = context.getTerminalPipe();
    head = context.createHandlerPipe(head);
    head = context.createMonitoringPipe(head);
    head = context.createServerMUPipe(head);
    head = context.createWsaPipe(head);
    head = context.createSecurityPipe(head);
    return head;
}
 

import com.sun.xml.internal.ws.api.pipe.ServerPipeAssemblerContext; //导入依赖的package包/类
/**
 * Called during the pipeline construction process once to allow a container
 * to register a pipe for monitoring.
 *
 * This pipe will be injected to a point very close to the transport, allowing
 * it to measure the time it takes for processing as well as detecting errors.
 *
 * @param ctxt
 *      Represents abstraction of SEI, WSDL abstraction etc. Context can be used
 *      whether add a new pipe to the head or not.
 *
 * @param tail
 *      Head of the partially constructed pipeline. If the implementation
 *      wishes to add new pipes, it should do so by extending
 *      {@link AbstractFilterPipeImpl} and making sure that this {@link Pipe}
 *      eventually processes messages.
 *
 * @return
 *      The default implementation just returns <tt>tail</tt>, which means
 *      no additional pipe is inserted. If the implementation adds
 *      new pipes, return the new head pipe.
 */
public @NotNull Pipe createMonitoringPipe(ServerPipeAssemblerContext ctxt, @NotNull Pipe tail) {
    return tail;
}
 

import com.sun.xml.internal.ws.api.pipe.ServerPipeAssemblerContext; //导入依赖的package包/类
/**
 * Called during the pipeline construction process once to allow a container
 * to register a pipe for security.
 *
 * This pipe will be injected to a point very close to the transport, allowing
 * it to do some security operations.
 *
 * @param ctxt
 *      Represents abstraction of SEI, WSDL abstraction etc. Context can be used
 *      whether add a new pipe to the head or not.
 *
 * @param tail
 *      Head of the partially constructed pipeline. If the implementation
 *      wishes to add new pipes, it should do so by extending
 *      {@link AbstractFilterPipeImpl} and making sure that this {@link Pipe}
 *      eventually processes messages.
 *
 * @return
 *      The default implementation just returns <tt>tail</tt>, which means
 *      no additional pipe is inserted. If the implementation adds
 *      new pipes, return the new head pipe.
 */
public @NotNull Pipe createSecurityPipe(ServerPipeAssemblerContext ctxt, @NotNull Pipe tail) {
    return tail;
}
 

import com.sun.xml.internal.ws.api.pipe.ServerPipeAssemblerContext; //导入依赖的package包/类
/**
 * Called during the pipeline construction process once to allow a container
 * to register a pipe for monitoring.
 *
 * This pipe will be injected to a point very close to the transport, allowing
 * it to measure the time it takes for processing as well as detecting errors.
 *
 * @param ctxt
 *      Represents abstraction of SEI, WSDL abstraction etc. Context can be used
 *      whether add a new pipe to the head or not.
 *
 * @param tail
 *      Head of the partially constructed pipeline. If the implementation
 *      wishes to add new pipes, it should do so by extending
 *      {@link AbstractFilterPipeImpl} and making sure that this {@link Pipe}
 *      eventually processes messages.
 *
 * @return
 *      The default implementation just returns {@code tail}, which means
 *      no additional pipe is inserted. If the implementation adds
 *      new pipes, return the new head pipe.
 */
public @NotNull Pipe createMonitoringPipe(ServerPipeAssemblerContext ctxt, @NotNull Pipe tail) {
    return tail;
}
 

import com.sun.xml.internal.ws.api.pipe.ServerPipeAssemblerContext; //导入依赖的package包/类
/**
 * Called during the pipeline construction process once to allow a container
 * to register a pipe for security.
 *
 * This pipe will be injected to a point very close to the transport, allowing
 * it to do some security operations.
 *
 * @param ctxt
 *      Represents abstraction of SEI, WSDL abstraction etc. Context can be used
 *      whether add a new pipe to the head or not.
 *
 * @param tail
 *      Head of the partially constructed pipeline. If the implementation
 *      wishes to add new pipes, it should do so by extending
 *      {@link AbstractFilterPipeImpl} and making sure that this {@link Pipe}
 *      eventually processes messages.
 *
 * @return
 *      The default implementation just returns {@code tail}, which means
 *      no additional pipe is inserted. If the implementation adds
 *      new pipes, return the new head pipe.
 */
public @NotNull Pipe createSecurityPipe(ServerPipeAssemblerContext ctxt, @NotNull Pipe tail) {
    return tail;
}