Re: [starter-dev] [EXTERNAL] Re: [jakarta.ee-community] [jakartaee-ambas

[Ondro Mihályi <mihalyi@xxxxxxxxxxx>]

Sure, no problem on my side. It's OK that the GlassFish Docker option is enabled only for the full Platform because it's more correct. The Docker image contains only the full GlassFish distribution and it's not possible to run in a "profile" that allows only Web Profile functionality. The UI bug is acceptable too, I know there are sometimes issues like that in JSF. I thought it's a mistake in the validation rules, that's why I reported it.

I have just one more note as a feedback. I think that the decision to select Jakarta EE 11 is misleading at the current time, as it only supports Core Profile now. Most of the people care only about Platform or Web Profile, Core profile is really meant mostly for certifications of small runtimes, mainly MicroProfile-only runtimes. Most people, who want to use the Starter to generate a project, would immediately select Jakarta EE 10 or older, and then would also need to select Platform, because the Core profile is pre-selected.

Do you think it would make sense to switch to Full Profile if people select Jakarta EE 10 or older right after the page loads? I mean, if they didn't select Core or Web Profile themself but Core Profile was pre-selected because of the default Jakarta EE 11 option? Can I create a PR to do something like that?

Ondro

On Sun, Mar 23, 2025 at 3:03 AM 'Reza Rahman' via Jakarta EE Ambassadors <jakartaee-ambassadors@xxxxxxxxxxxxxxxx> wrote:

I'll look at the UI validation tomorrow.

For the Archetype, I simply accepted your PR. If you want to change something about that, please simply make another PR.

Obviously, please ensure whatever is supposed to be supported aligns with what the GlassFish project wants to do with Docker and profiles for users. That is what we try to ensure with other vendors like IBM for Liberty. Liberty does not have different images for different profiles as that is handled by the server.xml instead. Other vendors like Payara have different images for different profiles. I have no way to know what GlassFish wants to do with its Docker images but would want to ensure nothing is potentially misleading or inappropriate. I do know GlassFish has different binary distributions for the platform and web profile. I think that avoids the situation of users wanting the web profile but accidentally using features that are not actually in the web profile.

---

From: jakarta.ee-community <jakarta.ee-community-bounces@xxxxxxxxxxx> on behalf of Ondro Mihályi via jakarta.ee-community <jakarta.ee-community@xxxxxxxxxxx>
Sent: Saturday, March 22, 2025 9:41 PM
To: Reza Rahman <reza_rahman@xxxxxxxx>
Cc: Ondro Mihályi <mihalyi@xxxxxxxxxxx>; starter developer discussions <starter-dev@xxxxxxxxxxx>; Jakarta EE community discussions <jakarta.ee-community@xxxxxxxxxxx>; Jakarta EE Ambassadors <jakartaee-ambassadors@xxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakarta.ee-community] [jakartaee-ambassadors] GlassFish Docker Support in Jakarta Starter

 

Great news, Reza!

Now that I look at it, I see that some runtimes, e.g. OpenLiberty, use the same Docker image for Platform and both profiles. GlassFish Docker support is restricted only to Platform. I think we can change this in the archetype and UI to also support profiles with the GlassFish Full Docker image, right?

And I think I found a glitch in the UI - if I select GlassFish Docker, then change Java version to some other than 17 (GlassFish only supports Java 17 with the stock Docker image), then Docker support is unselected but the No option is not selected. What's worse, when I select Java 17 again, it should be possible to select the Docker option but it's not clickable. I attach a video recording.

Ondro

On Sat, Mar 22, 2025 at 4:53 AM 'Reza Rahman' via Jakarta EE Ambassadors <jakartaee-ambassadors@xxxxxxxxxxxxxxxx> wrote:

Hi folks,

We've now added GlassFish Docker support in the Jakarta Starter:
https://start.jakarta.ee. Please check it out. As part of the release,
we've also tried to solve the typical view expired problems that usually
happen with JSF and PrimeFaces. If you run into issues, we would
appreciate it if you could let us know. Of course we will keep an eye
out in the logs anyway for signs of trouble.

Next up hopefully is support for the EE 11 Web Profile or initial
support for Helidon.

Cheers,

Reza

--
You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambassadors+unsubscribe@xxxxxxxxxxxxxxxx.
To view this discussion visit https://groups.google.com/d/msgid/jakartaee-ambassadors/41666bc6-b4b5-47a7-ba08-690ff0fa3fd0%40mail.com.

--
You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambassadors+unsubscribe@xxxxxxxxxxxxxxxx.
To view this discussion visit https://groups.google.com/d/msgid/jakartaee-ambassadors/A014242D-55AA-E048-B770-A4D37BDA7F6A%40hxcore.ol.