Well I guess we need to be a bit more precise about what the likely impact is. IIUC from the commit the model is that the JDKInvoker and implementation invoker implement the transition between the local (to them) component implementation and Tuscany's internal representation of holders. Between these and the binding there are a set of interceptors on both reference and binding sides. So potentially any interceptor, and the binding runtimes themselves of course, could be impacted by the presence of holders.
..snip > --------------------------------------- > > There was a limit for the 1.x support that we only allow one parameter as > Holder<T>. To complete the feature, we will have change the output type of an > operation to take more than one parts. It could be a bit involved. > Doesn't even one parameter as a holder imply two return values? One for the holder and one for the return (which would also be a holder according to JAXWS). Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
