[jira] Resolved: (CXF-1345) Support configuring JAX-WS handlers based on port-name-pattern QName

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-1345.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.5
                   2.2.1

> Support configuring JAX-WS handlers based on port-name-pattern QName
> --------------------------------------------------------------------
>
>                 Key: CXF-1345
>                 URL: https://issues.apache.org/jira/browse/CXF-1345
>             Project: CXF
>          Issue Type: New Feature
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1
>            Reporter: Jervis Liu
>             Fix For: 2.2.1, 2.1.5
>
>
> Support configuring JAX-WS handlers based on port-name-pattern QName. I.e., following configuration needs to be supported:
> <handler-chain>
> 		<service-name-pattern
> 			xmlns:ns1="http://apache.org/handler_test">
> 			ns1:SoapService1
> 		</service-name-pattern>
> 		<handler>
> 			<handler-name>Handler1</handler-name>
> 			<handler-class>
> 				org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilderTest$TestLogicalHandler
> 			</handler-class>
> 		</handler>
> </handler-chain>
> At the moment, CXF only compares the local part of service-name-pattern, not the name space, i.e., only "SoapService1" takes effect, "ns1" is ignored. To do this, we need to implement our own parser to parse handler config files, as JAXB does not return a QName for service-name-pattern. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.