apache / apache/netbeans

Add support for Jakarta Persistence

Open
#5,616 2 comments 0 reactions 0 assignees View on GitHub
Java EE/Jakarta EE kind:feature
Dominant language
Java
Stars
3.1k
Forks
935
Avg merge
2d 3h
Merged PRs (30d)
17

Description

### Description

Good day everyone,

Currently Netbeans only has support for Javax based Persistence versions (1.0, 2.0 and 2.1), not the [Jakarta](https://jakarta.ee/specifications/persistence/) versions (2.2, 3.0 and 3.1). That means that it does not recognise the persistence.xml files of those versions as good ones and does not identify Entity Classes declared with jakarta namespaces or the JPQL of the Named Queries as such.

That last one is specially bothersome as it does not detect errors in the queries and you only find them once the start-up of the persistence module at deployment fails. Then you have to search within all your queries manually using the information that the persistence provider logs. And let me tell you, when you have a silly kind of error like a moved coma, the logs are really unhelpful.

![image](https://user-images.githubusercontent.com/16305562/223118561-1838d464-9f05-4d8a-b73b-39e944fb6bc4.png)

Thanks for your help in this issue.

### Use case/motivation

Have the same support for Jakarta Persistence as we currently have for Javax Persistence.

### Related issues

I already notified this issue in the #3757 bug report. The part of the web services support was solved and that issue closed, but the part of the persistence was not.

### Are you willing to submit a pull request?

No

Contributor guide

Open the contributing guide

Research direction

Start by comparing NetBeans' existing Javax Persistence support with the requested Jakarta Persistence versions 2.2, 3.0, and 3.1. Check recognition of persistence.xml files, jakarta entity namespaces, and JPQL in named queries. Done means Jakarta Persistence receives the same support currently provided for Javax Persistence, including query error detection.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.