CXF实战之拦截器Interceptor(四)
拦截器(Interceptor)是CXF功能最基本的扩展点,能够在不正确核心模块进行改动的情况下。动态加入非常多功能。拦截器和JAX-WS Handler、Filter的功能相似,当服务被调用时。就会创建一个拦截器链(Interceptor Chain),拦截器链在服务输入(IN)或输出(OUT)阶段实现附加功能。
拦截器能够在client,也能够在服务端加入。当client发起一个WebService请求时。在client会创建输出拦截器链,服务端接收到client的后。会创建输入拦截器链。当服务端返回响应消息时,响应消息会经过服务端的输出拦截链。client接收到服务端的响应时。会创建输入拦截器链,响应消息先经过输入拦截器链处理。拦截器在服务端和client的作用如图所看到的。
拦截器链阶段
拦截器链有多个阶段,每一个阶段都有多个拦截器。拦截器在拦截器链的哪个阶段起作用。能够在拦截器的构造函数中声明。
输入拦截器链有例如以下几个阶段,这些阶段依照在拦截器链中的先后顺序排列。
阶段名称 | 阶段功能描写叙述 |
---|---|
RECEIVE | Transport level processing(接收阶段,传输层处理) |
(PRE/USER/POST)_STREAM | Stream level processing/transformations(流处理/转换阶段) |
READ | This is where header reading typically occurs(SOAPHeader读取) |
(PRE/USER/POST)_PROTOCOL | Protocol processing, such as JAX-WS SOAP handlers(协议处理阶段,比如JAX-WS的Handler处理) |
UNMARSHAL | Unmarshalling of the request(SOAP请求解码阶段) |
(PRE/USER/POST)_LOGICAL | Processing of the umarshalled request(SOAP请求解码处理阶段) |
PRE_INVOKE | Pre invocation actions(调用业务处理之前进入该阶段) |
INVOKE | Invocation of the service(调用业务阶段) |
POST_INVOKE | Invocation of the outgoing chain if there is one(提交业务处理结果,并触发输入连接器) |
输出拦截器链有例如以下几个阶段,这些阶段依照在拦截器链中的先后顺序排列。
阶段名称 | 阶段功能描写叙述 |
---|---|
SETUP | Any set up for the following phases(设置阶段) |
(PRE/USER/POST)_LOGICAL | Processing of objects about to marshalled |
PREPARE_SEND | Opening of the connection(消息发送准备阶段。在该阶段创建Connection) |
PRE_STREAM | 流准备阶段 |
PRE_PROTOCOL | Misc protocol actions(协议准备阶段) |
WRITE | Writing of the protocol message, such as the SOAP Envelope.(写消息阶段) |
MARSHAL | Marshalling of the objects |
(USER/POST)_PROTOCOL | Processing of the protocol message |
(USER/POST)_STREAM | Processing of the byte level message(字节处理阶段,在该阶段把消息转为字节) |
SEND | 消息发送 |
在输出拦截器链的SEND阶段后,还会触发以_ENDING结尾阶段,这些ENDING阶段与以上阶段相应,主要用于清理或者关闭资源。ENDING阶段触发的顺序例如以下:
- SEND_ENDING
- POST_STREAM_ENDING
- USER_STREAM_ENDING
- POST_PROTOCOL_ENDING
- USER_PROTOCOL_ENDING
- MARSHAL_ENDING
- WRITE_ENDING
- PRE_PROTOCOL_ENDING
- PRE_STREAM_ENDING
- PREPARE_SEND_ENDING
- POST_LOGICAL_ENDING
- USER_LOGICAL_ENDING
- PRE_LOGICAL_ENDING
- SETUP_ENDING
CXF默认拦截器链
在CXF中,全部对消息的处理都是通过各种拦截器实现。CXF已经实现了多种拦截器,如操纵消息头、运行认证检查、验证消息数据、日志记录、消息压缩等。有些拦截器在公布服务、訪问服务时已经默认加入到拦截器链。
CXF默认输入拦截器链,假设没有加入额外的拦截器。CXF输入会顺序经过下面拦截器:
拦截器名称 | 拦截器功能 |
---|---|
AttachmentInInterceptor | Parse the mime headers for mime boundaries, finds the “root” part and resets the input stream to it, and stores the other parts in a collection of Attachments |
StaxInInterceptor | Creates an XMLStreamReader from the transport InputStream on the Message |
ReadHeadersInterceptor | Parses the SOAP headers and stores them on the Message |
SoapActionInInterceptor | Parses “soapaction” header and looks up the operation if a unique operation can be found for that action. |
MustUnderstandInterceptor | Checks the MustUnderstand headers, its applicability and process it, if required |
SOAPHandlerInterceptor | SOAP Handler as per JAX-WS |
LogicalHandlerInInterceptor | Logical Handler as per JAX-WS |
CheckFaultInterceptor | Checks for fault, if present aborts interceptor chain and invokes fault handler chain |
URIMappingInterceptor | Can handle HTTP GET, extracts operation info and sets the same in the Message |
DocLiteralnInterceptor | Examines the first element in the SOAP body to determine the appropriate Operation (if soapAction did not find one) and calls the Databinding to read in the data. |
SoapHeaderInterceptor | Perform databinding of the SOAP headers for headers that are mapped to parameters |
WrapperClassInInterceptor | For wrapped doc/lit, the DocLiteralInInterceptor probably read in a single JAXB bean. This interceptor pulls the individual parts out of that bean to construct the Object[] needed to invoke the service. |
SwAInInterceptor | For Soap w/ Attachments, finds the appropriate attachments and assigns them to the correct spot in the parameter list. |
HolderInInterceptor | For OUT and IN/OUT parameters, JAX-WS needs to create Holder objects. This interceptor creates the Holders and puts them in the parameter list. |
ServiceInvokerInInterceptor | Actually invokes the service. |
CXF默认输出拦截器链,假设没有加入额外的拦截器,CXF输入会顺序经过下面拦截器:
拦截器名称 | 拦截器功能 |
---|---|
HolderOutInterceptor | For OUT and IN/OUT params, pulls the values out of the JAX-WS Holder objects (created in HolderInInterceptor) and adds them to the param list for the out message. |
SwAOutInterceptor | For OUT parts that are Soap attachments, pulls them from the list and holds them for later. |
WrapperClassOutInterceptor | For doc/lit wrapped, takes the remaining parts and creates a wrapper JAXB bean to represent the whole message. |
SoapHeaderOutFilterInterceptor | Removes inbound marked headers |
SoapActionOutInterceptor | Sets the SOAP Action |
MessageSenderInterceptor | Calls back to the Destination object to have it setup the output streams, headers, etc… to prepare the outgoing transport. |
SoapPreProtocolOutInterceptor | This interceptor is responsible for setting up the SOAP version and header, so that this is available to any pre-protocol interceptors that require these to be available. |
AttachmentOutInterceptor | If this service uses attachments (either SwA or if MTOM is enabled), it sets up the Attachment marshallers and the mime stuff that is needed. |
StaxOutInterceptor | Creates an XMLStreamWriter from the OutputStream on the Message. |
SoapHandlerInterceptor | JAX-WS SOAPHandler |
SoapOutInterceptor | Writes start element for soap:envelope and complete elements for other header blocks in the message. Adds start element for soap:body too. |
LogicalHandlerOutInterceptor | JAX-WS Logical handler stuff |
WrapperOutInterceptor | If wrapped doc/lit and not using a wrapper bean or if RPC lit, outputs the wrapper element to the stream. |
BareOutInterceptor | Uses the databinding to write the params out. |
SoapOutInterceptor$SoapOutEndingInterceptor | Closes the soap:body and soap:envelope |
StaxOutInterceptor$StaxOutEndingInterceptor | Flushes the stax stream. |
MessageSenderInt$MessageSenderEnding | Closes the exchange, lets the transport know everything is done and should be flushed to the client. |
CXF实战之拦截器Interceptor(四)的更多相关文章
- CXF之五 拦截器Interceptor
拦截器(Interceptor)是CXF功能最主要的扩展点,可以在不对核心模块进行修改的情况下,动态添加很多功能.拦截器和JAX-WS Handler.Filter的功能类似,当服务被调用时,就会创建 ...
- struts2拦截器interceptor的配置方法及使用
转: struts2拦截器interceptor的配置方法及使用 (2015-11-09 10:22:28) 转载▼ 标签: it 365 分类: Struts2 NormalText Code ...
- Flume-NG源码阅读之SourceRunner,及选择器selector和拦截器interceptor的执行
在AbstractConfigurationProvider类中loadSources方法会将所有的source进行封装成SourceRunner放到了Map<String, SourceRun ...
- struts2学习笔记--拦截器(Interceptor)和登录权限验证Demo
理解 Interceptor拦截器类似于我们学过的过滤器,是可以在action执行前后执行的代码.是我们做web开发是经常使用的技术,比如权限控制,日志.我们也可以把多个interceptor连在一起 ...
- struts2拦截器interceptor的三种配置方法
1.struts2拦截器interceptor的三种配置方法 方法1. 普通配置法 <struts> <package name="struts2" extend ...
- SSM-SpringMVC-33:SpringMVC中拦截器Interceptor讲解
------------吾亦无他,唯手熟尔,谦卑若愚,好学若饥------------- 拦截器Interceptor: 对处理方法进行双向的拦截,可以对其做日志记录等 我选择的是实现Handler ...
- 过滤器(Filter)和拦截器(Interceptor)
过滤器(Filter) Servlet中的过滤器Filter是实现了javax.servlet.Filter接口的服务器端程序.它依赖于servlet容器,在实现上,基于函数回调,它可以对几乎所有请求 ...
- 二十五、过滤器Filter,监听器Listener,拦截器Interceptor的区别
1.Servlet:运行在服务器上可以动态生成web页面.servlet的声明周期从被装入到web服务器内存,到服务器关闭结束.一般启动web服务器时会加载servelt的实例进行装入,然后初始化工作 ...
- Flume 拦截器(interceptor)详解
flume 拦截器(interceptor)1.flume拦截器介绍拦截器是简单的插件式组件,设置在source和channel之间.source接收到的事件event,在写入channel之前,拦截 ...
随机推荐
- Noip2005谁拿了最多的奖学金题解
题解 题目本身没什么好说的. 只是一道普及组的题让我领悟到scanf()读字符的真谛.scanf()函数最奇异的功能就是控制串里除格式化字符串之外的字符.若匹配成功则舍去. 所以我们能够"精 ...
- div与span区别及用法
DIV与SPAN区别及div与san用法篇 接下来了解在div+css开发的时候在html网页制作,特别是标签运用中div和span的区别及用法.新手在使用web标准(div css)开发网页的时候, ...
- iOS内存管理 -讲的不错,角度独特
ios的内存管理,包括对象的所有权与引用计数.自动释放.访问器方法与属性.一些会改变引用计数的特殊情况 ----- 对象所有权(ownership) 与引用计数 (retain co ...
- 【python】python彻底卸载的方法【windows安装版卸载的示例】
要想彻底干净的卸载python,如果是使用的安装版的话,其实很简单.[windows安装版] 就是点击安装包. 例如,当前你安装的版本是3.6.5,你想要把它卸载掉. 查看python版本的命令: 只 ...
- 如何调试 Android 上 HTTP(S) 流量
http://greenrobot.me/devpost/how-to-debug-http-and-https-traffic-on-android/ 如何调试 Android 上 HTTP(S) ...
- React中的的JSX
什么是JSX? JSX是JavaScript XML的缩写,其本质是js,表现形式类似于XML,与js区别在于可直接在里面编写html标签. 怎么使用JSX? 语法规则: JSX 的基本语法规则:HT ...
- Linux线程优先级
转自:https://www.cnblogs.com/imapla/p/4234258.html Linux内核的三种调度策略: 1.SCHED_OTHER 分时调度策略 2.SCHED_FIFO ...
- AppStore中使用IDFA后提交应用的注意事项
在ios7.0出来以前,我们都是通过wifi的mac来当作IOS设备的唯一标识符.如何在ios下获取设备的MAC,你可以参数这篇文章:获取ios的MAC地址 在没有使用IDFA之前,我们在ios7及以 ...
- js转义和反转义html htmlencode htmldecode
文章目录 JS实现HTML标签转义及反转义 用Javascript进行HTML转义 1.HTML转义 2.反转义 3.一个有意思的认识 4.完整版本的代码 其他 [转义字符]HTML 字符实体< ...
- RV32C指令集
Risc-V支持16位压缩格式,压缩格式立即数位数更少,能使用的寄存器也比较少,有些指令只能用常用8个整数寄存器(x8-x15)或者(f8-f15). 每个RVC指令都有对应的32位指令,下表列出所有 ...