Some examples of what I meant.. For the service instance I'm invoking I'd like to know: * target JVM is it the same as the client instance? (is this a "Node" in Tuscany terms?, sorry of my ignorance) * target classloader (if it's not the same or a child I can't do PBR) * target DB (if it's the same maybe I can do PBR) * is target annotated with @AllowsPBR
And again, I'm ignorant to what extent this is already possible... Scott On Jan 23, 2008 1:36 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > Scott Kurz wrote: > > The binding-feed code suggests a way to deal with JIRAs 1678,1680. > > That is, the mediator is called directly from within the binding > > implementation, > > rather than relying on the DBInterceptor being set up on the wire at > > Composite start time with a static DB transform established at that > > time. > > > > A key piece of the puzzle would be the ability to query what's "on the > > other side of the binding". For example, I might have a binding > > impl with a co-located (same-JVM) optimized path in which I don't want > > to do a transform if the service impl uses the same DB as the client. > > But I'll need to query some metadata in order to know what the DB > > of the service impl is (as well as maybe other info like what > > classloader is uses and if it's the same or a parent of mine or not) > > > > I guess that takes us to the info stored along with the domain/node .. > > but I'm not too familiar with that code. > > > > I'm going to try to find some time to play around with this . > > Here's my 2c, as I'm the one who implemented what you saw in > binding-feed after struggling with the auto-magic data transformations > getting in my way. > > I think we should experiment and see if other bindings can invoke the > data mediator as well. > > I'm not quite sure what you meant by "query what's on the other side of > the binding". Could you give a specific example? > > -- > Jean-Sebastien > > --------------------------------------------------------------------- > 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]
