Yes, this is better than the previous suggestion and +1 to do this after
the RC
asankha
Paul Fremantle wrote:
Actually I'm not sure I like this. Sorry for the indecision :-)
The problem is there are three possibilities: force rest on, force
soap on, or leave alone. I was trying to capture those, and also allow
further options.
I think maybe the right syntax is:
force="rest|soap|soap11|soap12"
Since the word force implies that you are overriding the default.
Paul
On 11/21/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
A while back I added a mediator that sets the isRest() flag in
MessageContext to help switch between soap and rest/pox.
I think a more logical place to specify this is in the endpoint
definition. So I propose we add two optional attributes to <endpoint>
rest - means force rest on (mc.setRest(true))
soap - means force rest off (mc.setRest(false))
Ant also pointed out it would be good to add soap11 and soap12
alternatives. I'm going to wait until after the RC for that.
If neither rest/soap is specified it won't change the current value.
And you can't specify both :-)
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
