| Re: [jakartaee-platform-dev] [cdi-dev] Discussion: The new structure of EE integration sections |
> I think we decided earlier that we move the EE integration concerns from the CDI specification to a CDI EE specification (still part of the CDI project).By introducing a new CDI-integration spec, I assumed a new spec project and a spec team. If that's not the case, it should be clarified in the proposal.Proposal 1 didn't mention that the new specification would be handled by the same CDI project. If that's the case, then I see this just as a cosmetic change, not much to dispute about. I wouldn't even introduce a new official specification, just separate the EE-related artifacts (API, PDF, TCK). What I mean, there can still be one formal specification project that just delivers 2 sets of specs (SE spec and EE-integration spec on top of it). Not much would change in https://jakarta.ee/specifications/cdi/, just a new version of CDI would produce 2 separated sets of deliverables. Is that possible?
I think this is the best option until other specs adopt relevant parts of the CDI-EE integration and then we can discontinue such separate CDI-EE specification. Meanwhile, we should work with the other spec teams on how they can adopt these integrations.Ondro_______________________________________________On Mon, Nov 20, 2023 at 8:24 AM Ladislav Thon via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:I think we decided earlier that we move the EE integration concerns from the CDI specification to a CDI EE specification (still part of the CDI project). I agree it would be best if all specifications owned the CDI integration concerns, but as Scott mentioned, they don't want to, so it seems safe to assume that CDI EE is here to stay. With that in mind, I think it would be fine to specify the JPA / CDI integration there, too.LT_______________________________________________On Fri, Nov 17, 2023 at 8:09 PM Arjan Tijms via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:_______________________________________________Hi,On Fri, 17 Nov 2023 at 17:43, Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:If spec has the CDI dependencies, the TCKs will have dependencies on CDI. I think Lukas does not want the spec to rely on CDI.Sorry for repeating it, but Jakarta Persistence already depends on CDI.See https://jakarta.ee/specifications/persistence/3.1/jakarta-persistence-spec-3.1#entity-listeners
"Entity listener classes in Jakarta EE environments support dependency injection through the Contexts and Dependency Injection API (CDI) [7] when CDI is enabled[41]. An entity listener class that makes use of CDI injection may also define lifecycle callback methods annotated with the PostConstruct and PreDestroy annotations. These methods will be invoked after injection has taken place and before the entity listener instance is destroyed respectively.
The persistence provider is responsible for using the CDI SPI to create instances of the entity listener class; to perform injection upon such instances; to invoke their PostConstruct and PreDestroy methods, if any; and to dispose of the entity listener instances."(emphasis mine)Kind regards,Arjan Tijms
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.