JAX-WS: The port-name-pattern regular expression processing is incorrect
------------------------------------------------------------------------

                 Key: AXIS2-4397
                 URL: https://issues.apache.org/jira/browse/AXIS2-4397
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
            Reporter: Rich Scheuerle
            Assignee: Rich Scheuerle


Scenario:
A customer can supply JAX-WS application handlers with their application.  The 
customer indicates which handlers are run by providing an xml file describing 
the handler chain.          
                                                                
The following example xml file indicates that test.MyHandler handler should be 
run for all ports (*).                        
                                                                
<jws:handler-chains                                             
xmlns:jws="http://java.sun.com/xml/ns/javaee";>                  
  <jws:handler-chain name="MyHandlerChain">                     
      <jws:protocol-bindings>some value</jws:protocol-bindings> 
     <jws:port-name-pattern>*</jws:port-name-pattern>           
      <jws:handler>                                             
         <jws:handler-class>test.MyHandler</jws:handler-class>  
      </jws:handler>                                            
  </jws-handler-chain>                                          
</jws:handler-chains>                                           
                                                                
Due to an error introduced by a prior fix, this scenario will not succeed.  The 
test.MyHandler handler will not run, and no errors are reported by the JAX-WS 
engine.  
                                                                
This failure is limited to the case where the customer uses a single wildcard 
(*) in the <jws:port-name-pattern> or  <jws:service-name-pattern>.

Solution:
The JAX-WS runtime code that performs the regular expression evaluation for the 
<jws:port-name-pattern> and  <jws:service-name-pattern> elements is incorrect.  
I am working on a fix that will correct the algorithm.  I will also provide 
unit tests to verify the behavior.

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

Reply via email to