Hello Paulo, sorry for being silent
On Fri, 18 Jul 2025 at 18:44, Paulo Araújo <cris...@vikeo.com.br.invalid> wrote: > > Hello! > > I've figure out the "2" question about loading specific lazy > properties/fields. About the first one, I'll try to find the request for > change in Jakarta JPA project to assess if I should load all fields. > > The branch will be soon pushed to apache with the impl of > PersistenceUnitUtil.load methods. Glad to see you sorted everything out :)) Unfortunately I don't know codebase well enough to help :( > > Thanks! > > Paulo > > > > > > > ---- Em qui, 17 jul 2025 15:38:30 -0300 Paulo Araújo > <cris...@vikeo.com.br.INVALID> escreveu --- > > > > Hi! > > > > I've been using a self-hosted and the ci-builds config to run tests on the > OPENJPA-2940 branch (JPA 3.2). > > Could you please help me on the implementation of PersistenceUnitUtil > load(Object), load(Object, attributeName) and load(E entity, Attribute)? > These are my points: > 1- Is PUU.load(Object) equivalent to EntityManager.refresh(Object)? (If it > is, my impl is already ok) > 2- How can I use StateManager or a custom fetchplan to force the "eager" > loading of a given attribute? > > > > I couldn't figure how to solve the first one using the API description and > I'm struggling with the second one to find how to do it in an abstract manner > due the separation between openjpa-persistence and openjpa-persistence-jdbc. > > > > If it is ok to you, I'll keep pushing the branch to my personal project until > it gets green, when I'll push it to apache github project. IMO it is better to work in a branch at ASF repo due to - other devs will get notifications and can follow your commits - there will be activity on dev@ list :)))) > > Best regards, > > Paulo > > > > > > > ---- Em qua, 09 jul 2025 03:56:38 -0300 Maxim Solodovnik < > mailto:solomax...@gmail.com > escreveu --- > > > > This job can be used to test custom branches with Java 17 > https://ci-builds.apache.org/job/OpenJPA/job/openjpa-pr-17/ :)) > > On Tue, 8 Jul 2025 at 20:24, Paulo Araújo < mailto: > mailto:cris...@vikeo.com.br.invalid > wrote: > > > > I've pushed the branch to github. Although the build is still broke in GH > > actions, it works locally on: > > > > - derby > > > > - h2 (2.3.x), both in-memory and tcp dbs > > > > - postgresql (latest) > > > > - mariadb (lts) > > > > - mysql (lts) > > > > > > > > The branch is still on JPA 3.1 because I wanted to have a working and green > > tested baseline after bumps on dependencies, but before starting actual > > work on impl. The duplicate branch push is due my rebase after the recently > > merging of pending PRs. > > > > > > > > Best regards, > > > > Paulo > > > > > > > > > > > > > > ---- Em qua, 02 jul 2025 22:15:42 -0300 Maxim Solodovnik < mailto: > > mailto:solomax...@gmail.com > escreveu --- > > > > > > > > +1 for move on :) > > > > from mobile (sorry for typos ;) > > > > > > On Thu, Jul 3, 2025, 03:02 Romain Manni-Bucau < mailto: mailto: > > mailto:rmannibu...@gmail.com > wrote: > > > > > sounds good to me > > > > > > Romain Manni-Bucau > > > @rmannibucau < https://x.com/rmannibucau > | .NET Blog > > > < https://dotnetbirdie.github.io/ > | Blog < > > > https://rmannibucau.github.io/ > > > > | Old > > > Blog < http://rmannibucau.wordpress.com > | Github > > > < https://github.com/rmannibucau > | LinkedIn > > > < https://www.linkedin.com/in/rmannibucau > | Book > > > < > > > https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064 > > > > > > > > > > > > > Le mer. 2 juil. 2025 à 21:36, Paulo Araújo < mailto: mailto: > > > mailto:cris...@vikeo.com.br.invalid > > > > a > > > écrit : > > > > > > > Hello! > > > > > > > > Could we start the work to evolve openjpa to JPA 3.2? > > > > > > > > I've made some changes in my branch to push minimum JDK version to 17. > > > > > > > > For now, it is just some bumps in dependencies versions of the project, > > > > some cleanups in violations of checkstyle and removal of deprecated > > > methods > > > > (mostly on the SecurityManager front). The build still works, but it > > > > touches a big chunk of files and the revision would be a nightmare, I > > > guess. > > > > > > > > > > > > > > > > I was planning to submit this startup work as a tentative 4.2.0-SNAPSHOT > > > > version and keep working on the features added in spec (a lot more than > > > > 3.0-to-3.1). > > > > > > > > What do you think about it? > > > > Best regards, > > > > > > > > Paulo > > > > > > > -- > Best regards, > Maxim -- Best regards, Maxim
