axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-3709) Improve handler-chains.xml parsing
Date Mon, 07 Apr 2008 05:40:26 GMT

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

Jarek Gawor resolved AXIS2-3709.
--------------------------------

       Resolution: Fixed
    Fix Version/s: nightly
                   1.4

Committed fixes to trunk (revision 645379) and 1_4 branch (revision 645384).


> Improve handler-chains.xml parsing
> ----------------------------------
>
>                 Key: AXIS2-3709
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3709
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: 1.4, nightly
>
>         Attachments: AXIS2-3709.patch
>
>
> Right now the handler-chains.xml file is parsed using JAXB. The problem with JAXB parsing
is that it returns null for an invalid qname. For example, when the namespace of the qname
cannot be resolved. So for example, when the handler-chains.xml contains an invalid qname
for service-name or port-name and JAXB returns null then the HandlerResolver will treat it
as if the service-name/port-name was not specified at all. And therefore HandlerResolver will
return a handler that it should not.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message