[jbossws-issues] [JBoss JIRA] Commented: (JBWS-3020) Investigate why HandlerScopeTestCase fails

[Jim Ma (JIRA)]

    [ https://jira.jboss.org/browse/JBWS-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12531643#action_12531643 ] 

Jim Ma commented on JBWS-3020:
------------------------------

The setHandlerName() of ProtocolHandler is only called in native stack, it is our api and  not JAXWS standard thing.  Metro and CXF will not set handler name to each Handler. So we need to use another flag to trace the handler execution path . 
Due to  this line code : return (name != null ? name : this.getClass().getSimpleName())  , the ServerHandler's name can be retrieved and the server side handler execution path is not null:null:...


> Investigate why HandlerScopeTestCase fails
> ------------------------------------------
>
>                 Key: JBWS-3020
>                 URL: https://jira.jboss.org/browse/JBWS-3020
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>            Reporter: Richard Opalka
>            Assignee: Jim Ma
>             Fix For:  jbossws-cxf-3.3.0
>
>
> -------------------------------------------------------------------------------
> Test set: org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.412 sec <<< FAILURE!
> testClientAccess(org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase)  Time elapsed: 5.271 sec  <<< FAILURE!
> junit.framework.ComparisonFailure:
> expected: <...SOAP12ClientHandler:SOAPClientHandler:ServiceClientHandler:ServiceWildcardClientHandler:PortClientHandler:PortWildcardClientHandler:GeneralClientHandler:GeneralServerHandler:PortWildcardServerHandler:PortServerHandler:ServiceWildcardServerHandler:ServiceServerHandler:
> SOAPServerHandler:SOAP12ServerHandler:endpoint:SOAP12ServerHandler:SOAPServerHandler:ServiceServerHandler:ServiceWildcardServerHandler:PortServerHandler:PortWildcardServerHandler:GeneralServerHandler:GeneralClientHandler:PortWildcardClientHandler:PortClientHandler:
> ServiceWildcardClientHandler:ServiceClientHandler:SOAPClientHandler:SOAP12ClientHandler> 
> but was:  <...null:null:null:null:null:null:null:GeneralServerHandler:PortWildcardServerHandler:PortServerHandler:ServiceWildcardServerHandler:ServiceServerHandler:SOAPServerHandler:SOAP12ServerHandler:endpoint:SOAP12ServerHandler:SOAPServerHandler:ServiceServerHandler:
> ServiceWildcardServerHandler:PortServerHandler:PortWildcardServerHandler:GeneralServerHandler:null:null:null:null:null:null:null>
> 	at junit.framework.Assert.assertEquals(Assert.java:81)
> 	at junit.framework.Assert.assertEquals(Assert.java:87)
> 	at org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase.assertResponse(HandlerScopeTestCase.java:91)
> 	at org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase.testClientAccess(HandlerScopeTestCase.java:56)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira