handlerchainprocessor.java
来自「开源的axis2框架的源码。用于开发WEBSERVER」· Java 代码 · 共 589 行 · 第 1/2 页
JAVA
589 行
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
package org.apache.axis2.jaxws.handler;
import org.apache.axis2.jaxws.ExceptionFactory;
import org.apache.axis2.jaxws.context.factory.MessageContextFactory;
import org.apache.axis2.jaxws.i18n.Messages;
import org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils;
import org.apache.axis2.jaxws.message.Message;
import org.apache.axis2.jaxws.message.Protocol;
import org.apache.axis2.jaxws.message.XMLFault;
import org.apache.axis2.jaxws.message.factory.MessageFactory;
import org.apache.axis2.jaxws.message.util.XMLFaultUtils;
import org.apache.axis2.jaxws.registry.FactoryRegistry;
import org.apache.axis2.jaxws.utility.SAAJFactory;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPConstants;
import javax.xml.soap.SOAPFault;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.ProtocolException;
import javax.xml.ws.WebServiceException;
import javax.xml.ws.handler.Handler;
import javax.xml.ws.handler.LogicalHandler;
import javax.xml.ws.handler.soap.SOAPHandler;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
public class HandlerChainProcessor {
private static final Log log = LogFactory.getLog(HandlerChainProcessor.class);
public enum Direction {
IN, OUT
};
// the type of message, not indicative of one-way vs. request-response
public enum MEP {
REQUEST, RESPONSE
};
private javax.xml.ws.handler.MessageContext currentMC; // just a pointer
private LogicalMessageContext logicalMC = null;
private SoapMessageContext soapMC = null;
private MEPContext mepCtx;
private List<Handler> handlers = null;
// track start/end of logical and protocol handlers in the list
// The two scenarios are: 1) run logical handlers only, 2) run all handlers
// logical start is always 0
// protocol start is always logicalLength + 1
// list end is always handlers.size()-1
private int logicalLength = 0;
private final static int SUCCESSFUL = 0;
private final static int FAILED = 1;
private final static int PROTOCOL_EXCEPTION = 2;
private final static int OTHER_EXCEPTION = 3;
// save it if Handler.handleMessage throws one in
// HandlerChainProcessor.handleMessage
private RuntimeException savedException;
private Protocol proto; // need to save it incase we have to make a fault message
/*
* HandlerChainProcess expects null, empty list, or an already-sorted
* list. If the chain passed into here came from our HandlerChainResolver,
* it is sorted already. If a client app created or manipulated the list,
* it may not be sorted. The processChain and processFault methods check
* for this by calling verifyChain.
*/
public HandlerChainProcessor(List<Handler> chain, Protocol proto) {
if (chain == null) {
handlers = new ArrayList<Handler>();
}
else
handlers = chain;
this.proto = proto;
}
/*
* sortChain will properly sort the chain, logical then protocol, since it may be
* a chain built or modified by a client application. Also keep track of
* start/end for each type of handler.
*/
private void sortChain() throws WebServiceException {
ArrayList<Handler> logicalHandlers = new ArrayList<Handler>();
ArrayList<Handler> protocolHandlers = new ArrayList<Handler>();
Iterator handlerIterator = handlers.iterator();
while (handlerIterator.hasNext()) {
// this is a safe cast since the handlerResolver and binding.setHandlerChain
// and InvocationContext.setHandlerChain verifies it before we get here
Handler handler = (Handler)handlerIterator.next();
// JAXWS 9.2.1.2 sort them by Logical, then SOAP
if (LogicalHandler.class.isAssignableFrom(handler.getClass()))
logicalHandlers.add((LogicalHandler) handler);
else if (SOAPHandler.class.isAssignableFrom(handler.getClass()))
// instanceof ProtocolHandler
protocolHandlers.add((SOAPHandler) handler);
else if (Handler.class.isAssignableFrom(handler.getClass())) {
// TODO: NLS better error message
throw ExceptionFactory.makeWebServiceException(Messages
.getMessage("handlerChainErr1", handler
.getClass().getName()));
} else {
// TODO: NLS better error message
throw ExceptionFactory.makeWebServiceException(Messages
.getMessage("handlerChainErr2", handler
.getClass().getName()));
}
}
logicalLength = logicalHandlers.size();
// JAXWS 9.2.1.2 sort them by Logical, then SOAP
handlers.clear();
handlers.addAll(logicalHandlers);
handlers.addAll(protocolHandlers);
}
/**
* @param mc
* By the time processChain method is called, we already have the sorted chain,
* and now we have the direction, MEP, MessageContext, and if a response is expected. We should
* be able to handle everything from here, no pun intended.
*
* Two things a user of processChain should check when the method completes:
* 1. Has the MessageContext.MESSAGE_OUTBOUND_PROPERTY changed, indicating reversal of message direction
* 2. Has the message been converted to a fault message? (indicated by a flag in the message)
*/
public boolean processChain(MEPContext mepCtx, Direction direction, MEP mep,
boolean expectResponse) {
if (handlers.size() == 0)
return true;
this.mepCtx = mepCtx;
sortChain();
initContext(direction);
if (direction == Direction.OUT) { // 9.3.2 outbound
currentMC.put(javax.xml.ws.handler.MessageContext.MESSAGE_OUTBOUND_PROPERTY,
(direction == Direction.OUT));
callGenericHandlers(mep, expectResponse, 0, handlers.size() - 1, direction);
} else { // IN case - 9.3.2 inbound
currentMC.put(javax.xml.ws.handler.MessageContext.MESSAGE_OUTBOUND_PROPERTY,
(direction == Direction.OUT));
callGenericHandlers(mep, expectResponse, handlers.size() - 1, 0, direction);
}
// message context may have been changed to be response, and message
// converted
// according to the JAXWS spec 9.3.2.1 footnote 2
if ((Boolean) (currentMC.get(javax.xml.ws.handler.MessageContext.MESSAGE_OUTBOUND_PROPERTY)) != (direction == Direction.OUT))
return false;
return true;
}
/*
* This is the implementation of JAX-WS 2.0 section 9.3.2.1
*/
private void callGenericHandlers(MEP mep, boolean expectResponse, int start, int end,
Direction direction) throws RuntimeException {
// if this is a response message, expectResponse should always be false
if (mep == MEP.RESPONSE)
expectResponse = false;
int i = start;
int result = SUCCESSFUL;
// declared and initialized just in case we need them
// in a reverse flow situation
int newStart = 0, newStart_inclusive = 0, newEnd = 0;
Direction newDirection = direction;
if (direction == Direction.OUT) {
while ((i <= end) && (result == SUCCESSFUL)) {
result = handleMessage(((Handler)handlers.get(i)), direction, expectResponse);
newStart = i - 1;
newStart_inclusive = i;
newEnd = 0;
newDirection = Direction.IN;
i++;
if (result == SUCCESSFUL) // don't switch if failed, since we'll be reversing directions
switchContext(direction, i);
}
} else { // IN case
while ((i >= end) && (result == SUCCESSFUL)) {
result = handleMessage(((Handler)handlers.get(i)), direction, expectResponse);
newStart = i + 1;
newStart_inclusive = i;
newEnd = handlers.size() - 1;
newDirection = Direction.OUT;
i--;
if (result == SUCCESSFUL) // don't switch if failed, since we'll be reversing directions
switchContext(direction, i);
}
}
if (newDirection == direction) // we didn't actually process anything, probably due to empty list
return; // no need to continue
// 9.3.2.3 in all situations, we want to close as many handlers as
// were invoked prior to completion or exception throwing
if (expectResponse) {
if (result == FAILED) {
// we should only use callGenericHandlers_avoidRecursion in this case
callGenericHandlers_avoidRecursion(newStart, newEnd, newDirection);
callCloseHandlers(newStart_inclusive, newEnd, newDirection);
} else if (result == PROTOCOL_EXCEPTION) {
try {
callGenericHandleFault(newStart, newEnd, newDirection);
callCloseHandlers(newStart_inclusive, newEnd, newDirection);
} catch (RuntimeException re) {
callCloseHandlers(newStart_inclusive, newEnd, newDirection);
// TODO: NLS log and throw
throw re;
}
} else if (result == OTHER_EXCEPTION) {
callCloseHandlers(newStart_inclusive, newEnd, newDirection);
// savedException initialized in HandlerChainProcessor.handleMessage
// TODO: NLS log and throw
throw savedException;
}
} else { // everything was successful OR finished processing handlers
/*
* This is a little confusing. There are several cases we should be
* aware of. An incoming request with false expectResponse is
* equivalent to server inbound one-way, for example.
*
* An outgoing response is server outbound, and is always marked
* with a false expectResponse. The problem, however, is that the
* direction for the call to closehandlers will be incorrect. In
* this case, the handlers should be closed in the opposite order of
* the ORIGINAL invocation.
*/
if (mep.equals(MEP.REQUEST)) {
// a request that requires no response is a one-way message
// and we should only close whomever got invoked
callCloseHandlers(newStart_inclusive, newEnd, newDirection);
}
else {
// it's a response, so we can safely assume that
// ALL the handlers were invoked on the request,
// so we need to close ALL of them
if (direction.equals(Direction.IN)) {
callCloseHandlers(handlers.size() - 1, 0, direction);
} else {
callCloseHandlers(0, handlers.size() - 1, direction);
}
if (savedException != null) {
// we have a saved exception, throw it (JAX-WS 9.3.2.1 "Throw any
// other runtime exception --> No response" case.
throw savedException;
}
}
}
}
/*
* callGenericHandlers_avoidRecursion should ONLY be called from one place.
* TODO: We cannot necessarily assume no false returns and no exceptions will be
* thrown from here even though the handlers we will be calling have all already
* succeeded in callGenericHandlers.
*/
private void callGenericHandlers_avoidRecursion(int start,
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?