I'm +1 on this. Do the deprecated setters and most importantly the
deprecated engageModule(QName).
Paul
On 3/21/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Hi Asankha:
We can certainly add deprecated methods for the setters and the
constructors, but not for getName() (since it would only differ by
return type). That being the case, I figured just take the hit now
rather than only having the set half of the API continue to work.
Let me know if you think we should add the deprecated setters, though!
--Glen
Asankha C. Perera wrote:
> Glen
>
> I agree its good overall, but I am a bit concerned about a public API
> change if its without deprecation of the previous methods. Synapse can
> upgrade our code - but there may be other projects/code outside that may
> get broken. Just a concern..
>
> asankha
>
>>> How about
>>>
>>> public void engageModule(String modName) {
>>> engageModule(new QName(modName));
>>> }
>>
>> Funny you should ask... How about I just do the same thing with Module
>> names (Stringify them) right now and be done with it?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
