[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2616) Fix handlerscope testcase

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Thu Apr 16 04:58:22 EDT 2009


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

Alessio Soldano commented on JBWS-2616:
---------------------------------------

Even if we have a FIXME (CXF-1253) for the CXF stack, that's related to client side only; we should at least verify the handler's ordering for the server side.

> Fix handlerscope testcase
> -------------------------
>
>                 Key: JBWS-2616
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2616
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-metro, jbossws-native
>            Reporter: Alessio Soldano
>             Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0
>
>
> The handlerscope testcase in framework is based on getting the handler's name and appending it to the payload. Unfortunately the API does not provide means of getting the name from an handler, so what the test does is stack specific (native).
> We should have different handler classes used in that testcase.
> From a first try on this, it seems to me this is also shadowing some issues with wildcards in port-name-pattern and multiple protocol with the cxf stack.

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

        



More information about the jbossws-issues mailing list