| [swordfish-dev] Exception handling when endpoint resolvement from the SR fails |
|
Greetings the Swordfish Team In case the SR is unavailable the following exception stack trace will be added to the console log: SEVERE: An exception occured while trying to resolve service name via supplied wsdls
org.eclipse.swordfish.core.SwordfishException: The Service
Registry is not accessible on URL http://localhost:9001/registry at org.eclipse.swordfish.internal.resolver.backend.remote.SwordfishRegistryProvider.getServiceProviderDescriptions(SwordfishRegistryProvider.java:76) at org.eclipse.swordfish.internal.resolver.backend.remote.SwordfishRegistryProvider.getServiceProviderDescriptions(SwordfishRegistryProvider.java:1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.osgi.service.importer.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:59) at org.springframework.osgi.service.importer.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:67) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.osgi.service.importer.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:34) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.osgi.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:59) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) In case the SR doesn’t contain an appropriate wsdl: SEVERE: An exception occured while trying to resolve service name via supplied wsdls
org.eclipse.swordfish.core.SwordfishException: Error resolving
endpoint - no service description has been found for the interface: {http://service.dynamic.samples.swordfish.eclipse.org/}FlightService at org.eclipse.swordfish.internal.core.interceptor.EndpointResolverInterceptor.process(EndpointResolverInterceptor.java:124) at org.eclipse.swordfish.internal.core.integration.nmr.SwordfishExchangeListener.exchangeSent(SwordfishExchangeListener.java:79) at org.apache.servicemix.nmr.core.ChannelImpl.dispatch(ChannelImpl.java:282) at org.apache.servicemix.nmr.core.ChannelImpl.sendSync(ChannelImpl.java:141) at org.apache.servicemix.nmr.core.ChannelImpl.sendSync(ChannelImpl.java:127) at org.eclipse.swordfish.samples.dynamic.consumer.SimpleClient.sendRequestSynchronously(SimpleClient.java:98) So my question: Is the current exception handling implementation sufficient or we need to make changes to the described behavior? Regards Volodymyr __________ Information from ESET NOD32 Antivirus, version of virus signature database 4401 (20090906) __________ The message was checked by ESET NOD32 Antivirus. http://www.esetnod32.ru |