About setFlow(Flow), I thought, prevailing opinion was that maintaining get/setFlow
consistency is better. I am fine, if we are taking that approach.
About encoder/decorder annotations:
I dont think, the application doing their own encoding/decoding is a predominant usecase
within outbound support. It is likely that large majority of the applications might be
okay with container doing that for application.
And my understanding of Keith's proposal is that, application will not be registering
methods with the container. Rather, application will write appropriate logic at
relevant parts of the application to encode/decode flow. And if I understood it
right, I am fine with that proposal.
Don't get me wrong. I am all for new trendy ways of development. It is just that
for this usecase, It doesn't sound important enough decision making reason.
But we should do more on annotations and CDI/CDI-like programming where possible.
On 4/3/2013 6:52 PM, Jean Deruelle wrote:
Re: SIP Outbound first draft of use cases