Le mar. 4 avr. 2023 à 10:22, Thomas Andraschko <andraschko.tho...@gmail.com> a écrit :
> In theory we could remove TX (if all cases are handled by JTA) and move the > EntityManagerResolver + JPA descriptor parsing to Data itself. > > In general i think our goal should be to port the DS features, if still not > existing in EE10, to EE10. Not to remove everything not widely used. > This allows users to migrate to EE10 with some adjustments. > This assumes it is used but this is really unsure, stats we have (central) are really about CI zone and major is our best chance to drop what is not needed to focus our effort on what is actually used. Indeed not a blocker but my 2cts would be to drop what we can to potentially add it back if we get a lot of demand rather than the opposite which means we'll keep dragging things to maintain almost nobody needs. > > > Am Di., 4. Apr. 2023 um 10:06 Uhr schrieb Romain Manni-Bucau < > rmannibu...@gmail.com>: > > > Hi, > > > > Do we have some visibility about the usage? > > Think jpa/tx feature tend to disappear in new applications because JTA > got > > it (we like or not the design is another thing but feature is there > > built-in now comared to when DS was created). > > So for a new major we can aim at dropping it - keeping in 1.x. > > About data module I guess the adoption is not that high even if module is > > really "cool" - guess we miss the jaxrs bridge but we never got any > request > > about it - so not sure its future. > > It can likely be the same for almost all core module which is now almost > > standard in CDI or Microprofile/coming Jakarta (idea being to not bring > > things without added value in time for a new major). > > > > So overall I wouldnt aim at renaming but more pruning what is built in or > > will be soon and make DS lighter now resources are very low and the need > of > > the project really less important than years ago. > > > > Hope it makes sense. > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://rmannibucau.metawerx.net/> | Old Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > < > > > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > > > > > Le mar. 4 avr. 2023 à 09:57, Thomas Andraschko < > > andraschko.tho...@gmail.com> > > a écrit : > > > > > JPA is also about reading the JPA XML descriptors and resolving > > > EntityManagers, which is both heavily used in the Data module. > > > So its currently much more than TX. I would rename it to ds-persistence > > and > > > ds-faces. > > > > > > Am Mo., 3. Apr. 2023 um 19:20 Uhr schrieb Gerhard Petracek < > > > gpetra...@apache.org>: > > > > > > > hi thomas, > > > > > > > > we need to fix the rat-check (see [1]). > > > > > > > > @renaming the modules: > > > > the jpa-module was always mainly about the "entitymanager" + > > > > "transaction" (see the package-naming)... with the main focus on > > > > transactions (see @Transactional and @TransactionScoped as the main > > > > api). > > > > therefore we almost renamed it to ds-tx (in the beginning). we just > > > > kept 'jpa', because it wasn't clear what we might add later on. > > > > maybe we should just start a community-poll about it. > > > > > > > > regards, > > > > gerhard > > > > > > > > [1] > > > > > > https://ci-builds.apache.org/job/DeltaSpike/job/DeltaSpike%20RAT-Check/ > > > > > > > > > > > > > > > > Am Mo., 3. Apr. 2023 um 16:08 Uhr schrieb Thomas Andraschko > > > > <andraschko.tho...@gmail.com>: > > > > > > > > > > Hi, > > > > > > > > > > last week i had some time and migrated almost all still existing > > > modules > > > > to > > > > > Jakarta. Only scheduler is currently not migrated. > > > > > AFAICS servlet, bean-validation has been removed, also other small > > > pieces > > > > > of core. > > > > > > > > > > I would also like to rename jpa and jsf to their new jakarta name > > > > > (persistence and faces). > > > > > WDYT guys? > > > > > > > > > > After that rename and reintroduce the scheduler module, i would be > > > happy > > > > > enough to release a RC1. > > > > > > > > > > AFAICS a big missing part are the tests on real containers?! > > > > > Any other topics we need to address? > > > > > > > > > > Best regards, > > > > > Thomas > > > > > > > > > >
