Muhwas, I dont understand what you are saying here.
Surely, the actual service has a specific interface - it isn't simply "anything", so you can only cast to the actual business interface it actually implements.
Or did you envisage your client code introspecting the returned service proxy and dealing with whatever it found? The latter case is possible but it is not a pattern I would encourage people to use - the code is likely to get very complex. I can see a possible use for it in writing test clients, where the parameters are actually presented in a GUI for a user to fill dynamically. However, this is not typical of real business code.
Yours, Mike. muhwas wrote:
by the way i used this CompositeContext compositeContext = CurrentCompositeContext.getContext(); // get service reference using service component name in client side default.scdl return compositeContext.locateService(java.lang.Object.class,serviceName); and then i casted it to what ever interface type i want to. so i think passing in interface doesn't nessasary. --- scabooz <[EMAIL PROTECTED]> wrote:
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
