I think we should keep the following piece. As the comment said,"create a remote service ref" , so it can delegate to the binding implementation to handle remote case.
// Lookup the component in the domain Component component = componentManager.getComponent(componentName); if (component == null) { // The component is not local in the partition, try to create a remote service ref return createServiceReference(businessInterface, name); } I agree if we already find the component ( component !=null case), we should check if the service is defined on the component and throw the service not found exception if it is not defined. I think the current implementation already does it in the ComponentContextImpl... Yang. On Thu, Apr 10, 2008 at 4:17 AM, Wang Feng <[EMAIL PROTECTED]> wrote: > +1 throw an exception. > > The scenario like this class.getMethod(methodName). > If a matching method is not found,it will throw NoSuchMethodException. > > Thanks, > Wang Feng > > > On 2008-04-10,ant elder <[EMAIL PROTECTED]> wrote: > > >TUSCANY-2145 asks about SCADomain.getService () returning a proxy even when > >the service doesn't exist, but looking back through the SVN history it looks > >like this is intentional. Before I close the JIRA does anyone have any > >comments on if this is/isn't the correct behaviour? > > > > ...ant > > > > > --------------------------------------------------------------------- > 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]