ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Taylor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-154) Missing WS-Addressing "MessageID" header when invoking a WSA compliant external services
Date Fri, 17 Aug 2007 18:50:30 GMT

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

Richard Taylor updated ODE-154:
-------------------------------

    Attachment: wsa.patch

See associated comment that was recently submitted.  Should have typed it here I suppose =b.
 Please let me know if there are any questions / concerns with the patch.

> Missing WS-Addressing "MessageID" header when invoking a WSA compliant external services
> ----------------------------------------------------------------------------------------
>
>                 Key: ODE-154
>                 URL: https://issues.apache.org/jira/browse/ODE-154
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>    Affects Versions: 1.1
>         Environment: JDK 1.5.0_11
> Axis2 Distribution
> WinXP x64
>            Reporter: Richard Taylor
>            Assignee: Matthieu Riou
>             Fix For: 1.1
>
>         Attachments: wsa.patch
>
>
> When I try to invoke an external service that implements WS-Addressing, I get an error
returned saying "A required header representing a Message Addressing Property is not present."
 The header it is referring to is "wsa:MessageID".  Ode properly sends the wsa:To and wsa:Action
headers, but apparently not the MessageID.   The missing header was confirmed using TCPMon
> It is possible that a MessageID is properly inserted when using BPEL Correlation IDs
or something along those lines, in other words this may be a user error.  But I could not
find any mention of it in Ode documentation.  Nor could I find the the proper method call
to Options.setMessageId() in the source code while setting up the outgoing message.
> The issue appears to be somewhere in the area of org.apache.ode.axis2.ExternalService.invoke().
 I believe we should be calling options.setMessageId() somewhere in there.
> I'm not sure if this affects the JBI distribution as well.

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


Mime
View raw message