On 8/16/07, Rich Taylor <[EMAIL PROTECTED]> wrote: > > I've been looking at this over the past day or two and it appears to be > missing a step or two. The ReplyTo and MessageId values are set but then > never read in SessionOutHandler and placed into the soap header. The > result > is that these new values are not present in the soap message going out. > Let me know if I'm missing something. I'm trying to finish it up myself > and > will submit a patch. I also have a question.
Actually for other options (not MessageId and ReplyTo) the information is set on the MessageContext options (basically a map) and read from the options in the SessionOutHandler. However Axis2 1.3 has specific methods directly on the MessageContext for MessageId and ReplyTo so I was hoping for them to be filling up the header directly. Apparently not. Anyway as you're currently working on it, it would be very nice to get a patch directly from you. > Currently the WS-Addressing "To" and "Action" headers are always specified > regardless of whether or not the service provider supports WS-Addressing. > Would it make sense to detect whether or not the service provider supports > WS-Addressing, if they do then enable the To and Action headers, and > ReplyTo > and MessageID headers as needed? Is there a reason to specify the > WS-Addressing "To" and "Action" headers in all cases, even when the > service > provider doesn't implement WS-Addressing? There may be uses for these > that > I'm not aware of. The headers are added to support the stateful exchange protocol (see [1]) and allow implicit correlation (see [2]). Ideally the support for these features should be declared using some policy and only used when declared but we don't support WS-Policy yet. So for now they're always present and it didn't seem to be too much of a problem so far. That being said, WS-Policy support would definitely be nice. Thanks, Matthieu [1] http://ode.apache.org/stateful-exchange-protocol.html [2] http://ode.apache.org/user-guide.html#UserGuide-ImplicitCorrelations Thanks, > Rich > > > > On 8/9/07, Matthieu Riou (JIRA) <[EMAIL PROTECTED]> wrote: > > > > > > [ > > > https://issues.apache.org/jira/browse/ODE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > > > Matthieu Riou resolved ODE-154. > > ------------------------------- > > > > Resolution: Fixed > > Assignee: Matthieu Riou > > > > I've just checked a fix in the trunk. Please give it a try and let me > know > > how it goes. > > > > > 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 > > > > > > > > > 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. > > > > >
