Are you using a Java with Maven project? Assuming so, the process for
what you are asking is a two step one:
1) Ensure the files you wish to access are located under the
src/main/resources folder as shown here:
https://i0.wp.com/www.dineshonjava.com/wp-content/uploads/2016/10/Maven-dirctory-struc
After a lot of swearing and adding of the correct libraries to
Tools->Libraries, I was able to persuade NB19 to create JPA 3.1 Entity
classes, based on the jakarta.persistence package space, from a database
in an SE project, although it identifies the libraries as EclipseLink
(JPA 3.0), not JPA
From my experience, minimize your direct Maven dependencies. Try to use
services as much as possible. For example. eclipselink should be a
runtime, not a compile time dependency and should be injected as service:
module-info.java:
requires jakarta.persistence;
uses jakarta.persistence
We have experienced this problem also. Which version of JPA are you
targeting?
On 20/01/2024 01:09, Greenberg, Gary wrote:
I am still using NB 18, because installing new versions require a lot
of paperwork here at Visa.
Nevertheless, I am now facing a problem that I haven’t had with
version
