Incorrect Imports for Session Bean in Generated Code
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 23
### What happened
When a Session Bean class is generated, the code incorrectly uses javax imports instead of jakarta imports, which causes compatibility issues. This problem is particularly evident in projects using Jakarta EE dependencies.
### Language / Project Type / NetBeans Component
java maven project web application
### How to reproduce
The generated code incorrectly uses javax.* imports, which are not compatible with Jakarta EE projects without additional manual configuration.
### Did this work correctly in an earlier version?
No / Don't know
### Operating System
Linux Mint 22 Cinnamon with kernel 6.8.0-49-generic
### JDK
OpenJDK Runtime Environment Zulu21.32+17-CA (build 21.0.2+13-LTS)
### Apache NetBeans packaging
Apache NetBeans binary zip
### Anything else
Whenever a session bean class is generated, the imported library is still of type javax. instead of being of the jakarta type
![Uploading netbeans bug1.png…]()
### Are you willing to submit a pull request?
Yes
Contributor guide
Research direction
No source file, test, or entry point is named. Reproduce generation of a Session Bean in the described Java Maven web application, then trace the generator responsible for its imports; done means generated Jakarta EE code uses jakarta imports instead of javax imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100