-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Javanica fallback not found when contained in super class #1177
Comments
@dmgcodevil Any thoughts on this one? |
Interesting, will take a look. Ok.
|
We have the exact same scenario and problem as ctoestreich describes in this issue. However, we are not using Groovy or Grails, just plain Java. I'm going to attempt a workaround for this in my project by declaring the fallback methods as 'abstract' in the super class (which happens to be abstract in my project), thus forcing the subclasses to implement them. This workaround obviously won't work for everyone, so it would be good to make the fallback method search more robust so it can find inherited methods too! |
ping @dmgcodevil any thoughts? |
Hi was busy with other activities, on the next weekend I will recall all
|
My workaround to implement in the subclasses is working for now. It would be great to resolve this though, thank you in advance! |
@mattrjacobs can we close ? |
Yes, thanks @dmgcodevil ! |
We are using the Annotated methods on classes where a service extends another service
And then inside CartService there is a some methods like
When using the service
wishListService
in a class the following exception is thrownIt would appear that when calling reflection for the class in com.netflix.hystrix.contrib.javinca.utils.MethodProvider line 92
return Optional.of(type.getDeclaredMethod(name, parameterTypes));
it does not resolve the super classes fallback method.We are using groovy and grails and this may be a factor in the evaluation of the type methods via reflection. However calling the following DOES resolve the method.
The text was updated successfully, but these errors were encountered: