Skip to content
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

To Feign or not... ;-) #8

Open
berndgoetz opened this issue Nov 26, 2016 · 1 comment
Open

To Feign or not... ;-) #8

berndgoetz opened this issue Nov 26, 2016 · 1 comment

Comments

@berndgoetz
Copy link

Hello Josh,

I've been watching your whirlwind tour through Config, Discovery, Proxy, Circuit Breaker setup at https://www.infoq.com/presentations/spring-boot-cloud-case-study - Congratulations! Very insightful, educational and entertaining!

I've been reproducing what you did there, following you step by step. In the presentation, you use the Feign client to connect to the reservation-service backend, but I could not get that running with it, but you did, at least in the presentation. I then checked your code here, at https://github.com/joshlong/cloud-native-workshop/tree/master/code, and saw that there is no Feign client used, either. I'm using Spring Boot 1.4.2. Any insights to that?

Regards,

@brennanreese
Copy link

brennanreese commented Jan 15, 2018

Update: I was hitting the wrong URL. If you have any issues with getting the list of names back, be sure you are hitting localhost:9999/reservations/names and not localhost:9999/reservation-service/reservations/names. Took me a day to figure that out -_-. I was able to get the feign client to work after I re-watched the presentation like 4 times and noticed the URL.

Same situation as @berndgoetz . In this presentation in Singapore: https://www.youtube.com/watch?v=I053xBvPhSY you had the @RepositoryRestResource on the reservation repo and were using Feign on the reservation-client. That setup looked very awesome so I went through and tried it, and am getting weird errors about trying to convert String to Long. Just wondering if you can still get that setup working or did something break since 2016, hence not using @RepositoryRestResource anymore. Just curious. Love the talks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants