synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] Resolved: (SYNAPSE-345) SOAP headers MUST be namespace-qualified
Date Tue, 04 May 2010 06:32:57 GMT


Hiranya Jayathilaka resolved SYNAPSE-345.

    Fix Version/s: 2.0
       Resolution: Fixed

Fixed on the trunk

> SOAP headers MUST be namespace-qualified
> ----------------------------------------
>                 Key: SYNAPSE-345
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>          Components: Extension Mediators
>            Reporter: Glen Daniels
>            Assignee: Hiranya Jayathilaka
>            Priority: Minor
>             Fix For: 2.0
> (I'm not sure if this is "core" or "extension mediators" - maybe you should change the
component name to just "mediators"?)
> Line 103 of is the problem here.  I was originally going to write
an issue about the fact that using "To", "From", etc as aliases for "wsa:To", "wsa:From",
etc meant that users couldn't actually insert headers called <To> or <From>...
but then I remembered that both SOAP 1.1 and SOAP 1.2 explicitly call out the fact that ALL
header blocks must be namespace-qualified.  So it's totally fine to map "To" -> "wsa:To"...
> BUT it's not fine to put in headers with no namespace... so please change line 103 to
either log a problem or throw a fault, whatever you feel is appropriate?
> Thanks!
> --Glen

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:
For additional commands, e-mail:

View raw message