axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty (JIRA)" <>
Subject [jira] Commented: (AXIS2-3987) Axis2 Addressing treats MessageID as a required element
Date Wed, 27 Aug 2008 00:30:44 GMT


Martin Gainty commented on AXIS2-3987:

sample client code to test WS-Addressing
public class EchoBlockingWsaBasedClient 
      Options options = new Options();
        //Blocking invocation via wsa mapping

        ServiceClient sender = new ServiceClient();

I dont see options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE); 
 in EchoBlockingWsaBasedClient sample client ?

which version Axis are you implementing?

how did you engage the addressing module?
<module name="addressing">

> Axis2 Addressing treats MessageID as a required element
> -------------------------------------------------------
>                 Key: AXIS2-3987
>                 URL:
>             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.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message