Hi Dmitry,
On 2/5/2013 7:03 PM, Dmitry Sklyut wrote:
<stuff deleted>
When blueprint creates it's proxy, this interface is not
on the objectclass and so the blueprint proxy doesn't expose
it.
Ok.
So is this a viable option for the use case on the forum posting?
Could they just be instructed how to make this change and create any
necessary meta-data?
Ok....that sounds good to me. Perhaps the folks on the forum thread
would be willing to do this...in order to get access to the ECF
IRemoteServiceProxy. They could decide for themselves whether they
would rather do this/above...or one of the other
solutions/workarounds below.
Again...seems like a good option to me. I don't know how 'spec
required' the folks are on the forum thread.
Ok. Still...I guess this could be left up to them...if this is
what they prefer.
This is still a viable option as well...
so to summarize...I think we have three possible solutions:
1) Use springframework.org schema...and add the extra available
interfaces (i.e. both IHello and IRemoteServiceProxy)
2) Use getTargetServiceReference() (last resort)
3) Use 'service.imported' service property to get/use
IRemoteService (rather than IRemoteServiceProxy).
It looks like 3 would be the easiest...if they are willing to write
code (I can provide them with example code if they wish), whereas 1
would be the easiest if they are willing to use the non-blueprint
schema. Agreed?
Thanks,
Scott
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
|