OK, thanks for the clarification...
Note, there's some weakness in the current approach to do with the proxy
being injected for custom interfaces even if no provider for a given
non-standard interface exists, something that Andrey was working upon.
At the moment, in such cases, NPE will be thrown when the application
code access such a context which is expected, though we will try to
optimize it and remove the injected proxies earlier if it is known that
NPE will be inevitable, a bit of work will need to be done to get it
optimized
Cheers, Sergey
On 24/07/14 09:21, iris ding wrote:
Sergey,
I mean if we want to support parameter type(custom context) in setter method
other than those specified in spec, we can not add check about parameter
type.
Iris Ding
--
View this message in context:
http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5746829.html
Sent from the cxf-dev mailing list archive at Nabble.com.
