Support `@Stereotype`
See original GitHub issueThe FT spec doesn’t mention Stereotypes, so there is no test in the TCK and implementations don’t have to support it.
It would be useful to, e.g., define a @Stereotype
-annotation @Gateway
with the complete default FT handling and use it for all gateway classes.
As a fallback it should at least be explicitly documented as not supported.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Addressing Stereotype Threat is Critical to Diversity ... - Frontiers
Empirical evidence has supported the idea that when individuals face stereotype threat, they are less likely to pursue leadership roles, ...
Read more >How to Beat Stereotypes by Seeing People as Individuals
Why we stereotype. Psychologists call our mental shortcuts “heuristics”—and we need them to help our brains navigate the world.
Read more >Stereotypes - BetterHelp
The therapists at BetterHelp can help you understand the harm that stereotypes contribute to in your life and how to work to fight...
Read more >Strategies and Resources About Stereotype Threat
What is a stereotype threat? “A type of social identity threat that occurs when one fears being judged in terms of a group-based...
Read more >How do we rid ourselves of stereotypes? - Getting Race Right
Contact (deliberately seeking opportunities to get to know people from stereotyped groups). These techniques are designed to help someone break the stereotype ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I will defer this one. However, I will add a statement on the spec to say “The stereotype support is optional.”
Okay, now I understand. This limitation of the CDI spec regarding stereotypes does restrict its usefulness, even when it never occurred to me before. I guess the main use-case is to define stereotypes on the class level anyway. When I have a bunch of gateway classes to encapsulate the access to remote systems that I want to protect with FT, wouldn’t it be useful to define the default FT behaviour in a
@Gateway
stereotype annotation? I could change anything at the class or at the method level, but the defaults are there. I could not remove something, e.g. the timeout, but I could change it to any value.I think this would be very valuable. Don’t you agree?