GlassFish JMS Resource Types
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 15
### What happened
I am using NetBeans 15 with Eclipse GlassFish 6.2.5 and Jakarta EE 9. When I create a web application and add a GlassFish JMS Resource, the only available Resource Types are javax.jms and jakarta.jms is not available. Thus the deployment fails because the Glassish server is looking for the jakarta.jms types.
### How to reproduce
1. In NetBeans 15 create a new web application project by selecting **Java Web** under **Categories** and **Web Application** under **Projects**. Click **Next**.
2. Name the project and click **Next**.
3. Select a GlassFish 6.2.1 server and **Jakarta EE 9.1 Web** for the **Java EE Version**.
4. Click Finish.
5. Right-click the new project and select **New** -> **Other**.
6. Select **GlassFish** under **Categories** and **JMS Resource** under **File Types**. Click **Next**.
7. Under **Choose Resource Type** the only available types are javax.jms and jakarta.jms is not available. GlassFish 6.2.1 expects **jakarta.jms** types and generates an error when trying to deploy **javax.jms** types.

### Did this work correctly in an earlier version?
No / Don't know
### Operating System
Windows 10 21H2
### JDK
JDK 17 by default, Jakarta 9 for the Web Application
### Apache NetBeans packaging
Apache NetBeans provided installer
### Anything else
The issue occurs every time.
Issue was present in NetBeans 14 as well.
### Are you willing to submit a pull request?
Yes
### Code of Conduct
Yes
Contributor guide
Research direction
Reproduce the issue in NetBeans 15 with GlassFish 6.2.1 and a Jakarta EE 9.1 Web application, following the listed JMS Resource wizard steps. Inspect the implementation behind the Choose Resource Type page and verify that jakarta.jms is available for Jakarta EE projects while javax.jms remains supported where appropriate. Done when deployment no longer generates the reported type mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100