Hi Markus! This comes up every few years. I'm not sure if this fully answers the question, but here was one of the longer answers:
- https://lists.apache.org/thread/7ph55qo1zlprhgtxwr5x1x9xgry016d8 Feel free to follow up with more questions or thoughts -- completely ok. -David > On Aug 11, 2024, at 8:23 AM, Markus Jung <ju...@apache.org> wrote: > > Hey all, > > I’ve been looking at the concurrency TCK for a bit now and noticed we still > have a somewhat large gap to be fully implementing the Concurrency 3.0 spec. > One thing that is new in the concurrency 3.0 spec is annotations to define > different services (ContextService, ManagedExecutorService, etc) via > annotations on beans. I’ve discovered that Jon already implemented this > behavior for @ContextServiceDefinition by doing the following: > 1. AnnotationDeployer scans beans for @ContextServiceDefinition > 2. It creates a ContextService object and stores it in the JndiConsumer > 3. ConvertContextServiceDefinitions picks this up and turns it into a real > Resource that is added into the AppModule > > What confuses me is the intermediate step 2, ContextService looks like it is > an autogenerated class from some XSD file, but the XSD is nowhere to be found. > @Jonathan (or anyone, really), maybe you can shed some light onto this? Me > and Richard are suspecting these classes have been generated back in the EE6 > days (looking at the XSD files) and modified as needed ever since. > > > Thanks > > Markus
