On 6/5/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Amila Suriarachchi wrote: > I have fixed this by changing the phases. i.e. security come before > addressing. I don't think changing phases is the solution for this.
yes correct solution is to put the addressing before security and fix the rampart issue. If some one set
isProcessed as true, then no-one better not set it to false, unless there is a very special reason. Why I put that flag is to make must understand checker to know which headers are processed and which ones are not. So all the module authors should adhere to it. Rather than changing the phases. can u please make sure rampart handlers does the proper thing?
yes, I informed ruchith and now he should have fixed it. What I am telling is if we had set mustunderstand true by default some one would have seen this much earlier.
> When cosidering this senario I see some advantage of setting this flag. > Although there is no problem with > the addressing. We can swith on the mustunderstand > in client side using client options but can not think a way in server > side. (when sending the request) I am sorry I can not understand what you are trying to explain here. Can you please elaborate a bit?
Lets take this senario of a inout message. First client send the request to server. since we do not have set the mustunderstand true, the addressing headers does not contain it. so if we want to have it we can set it using the client options. Then server gets the request and send a reply back to client. for this request we can not set the must understand properties true if it is not the default may. I don't know whether it is possible using the axis2.xml or the services.xml. Amila. Thanks,
Chinthaka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGZHjGjON2uBzUhh8RAu/pAJ9QJ6cit4oehaKWSoueIOiS47dxiwCeK5iK KineLK0LfqI+McNtgD/R3tI= =PAZN -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Amila Suriarachchi, WSO2 Inc.
