理解JAX-WS中Handlers

 JAX-WS提供插件式框架,通过handlers去加强运行的处理能力。Handlers是一个消息拦截器,能够在你的
web service前后进行处理。JAX-WS定义了两种类型的handlers,分别为logical handlers and protocol handlers.
Protocol handlers are specific to a protocol and may access or change the protocol specific aspects of a message.
Logical handlers are protocol-agnostic and act only on the payload of the message.
     在这篇文章中"A little about Handlers in JAX-WS", rama pulavarthi 解释了logical和SOAP handlers的区别。
下面这个图显示了这两个handlers能够访问到message context:


下面这个图显示了这两个handlers在JAX-WS server and client的运行顺序:

 

Logical  Handler实例:

 

Java代码 复制代码
  1. public class LogicalLoggingHandler implements LogicalHandler<LogicalMessageContext> {   
  2.     private static final PrintStream out = System.out;   
  3.   
  4.     public boolean handleMessage(LogicalMessageContext context) {   
  5.         return processMessage(context);   
  6.     }   
  7.   
  8.     public boolean handleFault(LogicalMessageContext context) {   
  9.         return processMessage(context);   
  10.     }   
  11.   
  12.     public void close(MessageContext context) {   
  13.     }   
  14.   
  15.     private boolean processMessage(LogicalMessageContext context) {   
  16.         Boolean outboundProperty = (Boolean)   
  17.                 context.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);   
  18.   
  19.         if (outboundProperty) {   
  20.             out.println("/nOutbound message:");   
  21.         } else {   
  22.             out.println("/nInbound message:");   
  23.         }   
  24.         LogicalMessage lm = context.getMessage();   
  25.         Source payload = lm.getPayload();   
  26.   
  27.         printSource(payload);   
  28.         // Without it, behavior may vary on the kind of source returned in lm.getPayload().   
  29.         // lm.setPayload(modifiedPayload);   
  30.         return true;   
  31.   
  32.     }   
  33.   
  34.     private static void printSource(Source payload) {   
  35.         try {   
  36.             TransformerFactory factory = TransformerFactory.newInstance();   
  37.             Transformer transformer = factory.newTransformer();   
  38.             transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");   
  39.             transformer.setOutputProperty(OutputKeys.METHOD, "xml");   
  40.             transformer.setOutputProperty(OutputKeys.INDENT, "yes");   
  41.             Result result = new StreamResult(out);   
  42.             transformer.transform(payload, result);   
  43.         } catch (TransformerException e) {   
  44.             e.printStackTrace();   
  45.         }   
  46.     }   
  47.   
  48. }  
public class LogicalLoggingHandler implements LogicalHandler<LogicalMessageContext> {
    private static final PrintStream out = System.out;

    public boolean handleMessage(LogicalMessageContext context) {
        return processMessage(context);
    }

    public boolean handleFault(LogicalMessageContext context) {
        return processMessage(context);
    }

    public void close(MessageContext context) {
    }

    private boolean processMessage(LogicalMessageContext context) {
        Boolean outboundProperty = (Boolean)
                context.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);

        if (outboundProperty) {
            out.println("/nOutbound message:");
        } else {
            out.println("/nInbound message:");
        }
        LogicalMessage lm = context.getMessage();
        Source payload = lm.getPayload();

        printSource(payload);
        // Without it, behavior may vary on the kind of source returned in lm.getPayload().
        // lm.setPayload(modifiedPayload);
        return true;

    }

    private static void printSource(Source payload) {
        try {
            TransformerFactory factory = TransformerFactory.newInstance();
            Transformer transformer = factory.newTransformer();
            transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
            transformer.setOutputProperty(OutputKeys.METHOD, "xml");
            transformer.setOutputProperty(OutputKeys.INDENT, "yes");
            Result result = new StreamResult(out);
            transformer.transform(payload, result);
        } catch (TransformerException e) {
            e.printStackTrace();
        }
    }

}

 

SOAP Handler实例:

 

Java代码 复制代码
  1. public class SOAPLoggingHandler implements SOAPHandler<SOAPMessageContext> {   
  2.        
  3.     private static PrintStream out = System.out;   
  4.        
  5.     public Set<QName> getHeaders() {   
  6.         return null;   
  7.     }   
  8.        
  9.     public boolean handleMessage(SOAPMessageContext smc) {   
  10.         logToSystemOut(smc);   
  11.         return true;   
  12.     }   
  13.        
  14.     public boolean handleFault(SOAPMessageContext smc) {   
  15.         logToSystemOut(smc);   
  16.         return true;   
  17.     }   
  18.        
  19.     public void close(MessageContext messageContext) {   
  20.     }   
  21.        
  22.     private void logToSystemOut(SOAPMessageContext smc) {   
  23.         Boolean outboundProperty = (Boolean)   
  24.             smc.get (MessageContext.MESSAGE_OUTBOUND_PROPERTY);   
  25.            
  26.         if (outboundProperty.booleanValue()) {   
  27.             out.println("/nOutbound message:");   
  28.         } else {   
  29.             out.println("/nInbound message:");   
  30.         }   
  31.            
  32.         SOAPMessage message = smc.getMessage();   
  33.         try {   
  34.             message.writeTo(out);   
  35.             out.println("");      
  36.         } catch (Exception e) {   
  37.             out.println("Exception in handler: " + e);   
  38.         }   
  39.     }   
  40. }  
public class SOAPLoggingHandler implements SOAPHandler<SOAPMessageContext> {
    
    private static PrintStream out = System.out;
    
    public Set<QName> getHeaders() {
        return null;
    }
    
    public boolean handleMessage(SOAPMessageContext smc) {
        logToSystemOut(smc);
        return true;
    }
    
    public boolean handleFault(SOAPMessageContext smc) {
        logToSystemOut(smc);
        return true;
    }
    
    public void close(MessageContext messageContext) {
    }
    
    private void logToSystemOut(SOAPMessageContext smc) {
        Boolean outboundProperty = (Boolean)
            smc.get (MessageContext.MESSAGE_OUTBOUND_PROPERTY);
        
        if (outboundProperty.booleanValue()) {
            out.println("/nOutbound message:");
        } else {
            out.println("/nInbound message:");
        }
        
        SOAPMessage message = smc.getMessage();
        try {
            message.writeTo(out);
            out.println("");   
        } catch (Exception e) {
            out.println("Exception in handler: " + e);
        }
    }
}

 

 

  • D8dcc2a1-f31c-37da-80d0-979b927fcc3f-thumb
  • 大小: 24.1 KB
  • F4a00259-75ff-3b46-af3e-a5a2e5a9aa3c-thumb
  • 大小: 20.4 KB
评论
melin 2008-05-10   回复
默认情况下CXF拦截器的处理顺序:
Java代码 复制代码
  1. receive [LoggingInInterceptor, ResponseTimeMessageInInterceptor, AttachmentInInterceptor]   
  2. pre-stream [LoggingOutInterceptor]   
  3. post-stream [StaxInInterceptor]   
  4. read [ReadHeadersInterceptor, SoapActionInInterceptor]   
  5. pre-protocol [MustUnderstandInterceptor, SOAPHandlerInterceptor, LogicalHandlerInInterceptor]   
  6. post-protocol [CheckFaultInterceptor]   
  7. unmarshal [URIMappingInterceptor, DocLiteralInInterceptor, SoapHeaderInterceptor]   
  8. post-logical [WrapperClassInInterceptor]   
  9. pre-invoke [SwAInInterceptor, HolderInInterceptor]   
  10. invoke [ServiceInvokerInterceptor]   
  11. post-invoke [OutgoingChainInterceptor]  
  receive [LoggingInInterceptor, ResponseTimeMessageInInterceptor, AttachmentInInterceptor]
  pre-stream [LoggingOutInterceptor]
  post-stream [StaxInInterceptor]
  read [ReadHeadersInterceptor, SoapActionInInterceptor]
  pre-protocol [MustUnderstandInterceptor, SOAPHandlerInterceptor, LogicalHandlerInInterceptor]
  post-protocol [CheckFaultInterceptor]
  unmarshal [URIMappingInterceptor, DocLiteralInInterceptor, SoapHeaderInterceptor]
  post-logical [WrapperClassInInterceptor]
  pre-invoke [SwAInInterceptor, HolderInInterceptor]
  invoke [ServiceInvokerInterceptor]
  post-invoke [OutgoingChainInterceptor]


melin 2008-05-10   回复
上面两个图搞反了。
原文出自 http://weblogs.java.net/blog/ramapulavarthi
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值