snip... On Wed, Oct 29, 2008 at 3:14 PM, Scott Kurz <[EMAIL PROTECTED]> wrote:
> OK, I see that the annotation is helpful especially from the client side to > deduce the Java class of the callback interface (on the service/target side > we have the type of the @Callback to guide us). Also on the service side there may be more than one service interface with a callback so you need to be able to find which callback reference to inject into. Maybe my point here are mute as the spec says that the WSDL2Java mapping should be done in accordance with JAX-WS so I guess you could say that the runtime should perform the mapping itself and determine which Java interface implements the callback in question. I don't believe Tuscany does this at the moment but I might be wrong. > > > If we were able to pursue my idea (and we decided we wanted to), then from > the perspective of a client component we could start from the > callbackInterface on the component reference interface definition and look > at what interfaces the client implements (one of which should be the > callback). > > ---- > > I realize I should broaden my question a bit... it's not strictly speaking > the top-down case I'm asking about but more generally the case in which the > component definition explicitly connects the forward/callback interfaces on > the component reference definition. > >
