com.sun.xml.ws.util.pipe.StandalonePipeAssembler Maven / Gradle / Ivy
/*
* The contents of this file are subject to the terms
* of the Common Development and Distribution License
* (the License). You may not use this file except in
* compliance with the License.
*
* You can obtain a copy of the license at
* https://glassfish.dev.java.net/public/CDDLv1.0.html.
* See the License for the specific language governing
* permissions and limitations under the License.
*
* When distributing Covered Code, include this CDDL
* Header Notice in each file and include the License file
* at https://glassfish.dev.java.net/public/CDDLv1.0.html.
* If applicable, add the following below the CDDL Header,
* with the fields enclosed by brackets [] replaced by
* you own identifying information:
* "Portions Copyrighted [year] [name of copyright owner]"
*
* Copyright 2006 Sun Microsystems Inc. All Rights Reserved
*/
/*
* Copyright (c) 2006 Your Corporation. All Rights Reserved.
*/
package com.sun.xml.ws.util.pipe;
import com.sun.istack.NotNull;
import com.sun.xml.ws.api.pipe.ClientPipeAssemblerContext;
import com.sun.xml.ws.api.pipe.Pipe;
import com.sun.xml.ws.api.pipe.PipelineAssembler;
import com.sun.xml.ws.api.pipe.ServerPipeAssemblerContext;
/**
* Default Pipeline assembler for JAX-WS client and server side runtimes. It
* assembles various pipes into a pipeline that a message needs to be passed
* through.
*
* @author Kohsuke Kawaguchi
* @author Jitendra Kotamraju
*/
public class StandalonePipeAssembler implements PipelineAssembler {
@NotNull
public Pipe createClient(ClientPipeAssemblerContext context) {
Pipe head = context.createTransportPipe();
head = context.createSecurityPipe(head);
if (dump) {
// for debugging inject a dump pipe. this is left in the production code,
// as it would be very handy for a trouble-shooting at the production site.
head = context.createDumpPipe("client", System.out, head);
}
head = context.createWsaPipe(head);
head = context.createClientMUPipe(head);
return context.createHandlerPipe(head);
}
/**
* 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;
}
/**
* Are we going to dump the message to System.out?
*/
private static final boolean dump;
static {
boolean b = false;
try {
b = Boolean.getBoolean(StandalonePipeAssembler.class.getName()+".dump");
} catch (Throwable t) {
// treat it as false
}
dump = b;
}
}