On Fri, Feb 27, 2009 at 10:43 AM, Brian DePradine (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/AXIS2-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Brian DePradine resolved AXIS2-3987. > ------------------------------------ > > Resolution: Won't Fix > > As the message id may be required in some situations, according to the > WS-Addressing spec, no change will be made. >
But if its optional, why do we make it mandatory? That seems to me to be an obvious contradiction, isn't it? It would be a violation of the spec if it couldn't be made optional, right? Rainy day here ... not that I have dog in this hunt. - R >> Axis2 Addressing treats MessageID as a required element >> ------------------------------------------------------- >> >> Key: AXIS2-3987 >> URL: https://issues.apache.org/jira/browse/AXIS2-3987 >> Project: Axis 2.0 (Axis2) >> Issue Type: Bug >> Components: Addressing >> Environment: Ubuntu, jdk 1.5 >> Reporter: Isuru Eranga Suriarachchi >> >> According to both WS-Addressing final and submission specifications, the >> Message Id is an optional element in the header. But when I engaged Axis2 >> addressing to a simple client and set only the Action, it adds a message Id >> as well. I tried the following option as well. But it didn't work. >> options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE); >> So I can't create a message without the optional element "MessageID" using >> Axis2.. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
