Re: [jakartaee-platform-dev] Status of GlassFish 6.0.0-M1

["Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>]

Corba has an impact in GlassFish as the protocol for remote EJBs is RMI/IIOP. The way GlassFish is architected in Full Profile is that when you deploy an EJB application the ORB is started up just in case. It is the start up of the ORB that is failing even if it’s not used. In Web Profile because the ORB isn’t present it is possible to deploy EJB applications.

 

Steve

 

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Kevin Sutter
Sent: 03 June 2020 17:56
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Status of GlassFish 6.0.0-M1

 

Sounds like great progress, Steve!  The Web Profile is looking very good for the Milestone release!  Thanks.

I'm curious on the CORBA requirement.  Since the CORBA piece was not picked up from the Java SE discard pile, and we are removing Distributed Interop from EJB 4.0, why is the Jakarta version of CORBA required?  This question actually feeds into the Platform spec updates that I have been working on.  We need a consistent story between the Spec and the CI.  Thanks!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To:        glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Cc:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        06/03/2020 04:27
Subject:        [EXTERNAL] [jakartaee-platform-dev] Status of GlassFish 6.0.0-M1
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx

---

 

Hi All,

 

Just a status update on where we are based on GlassFish master today.

 

Web Profile – starts up and can deploy applications using asadmin (deploying via web console doesn’t work). I have tested a smoke test application that uses Servlet, CDI, EJB, JPA , JTA all in the new namespace and it works correctly.

Full Profile – starts up and displays the administration console but won’t deploy applications containing EJBs due to issues with CORBA.

 

We need a version of CORBA in the Jakarta namespace and Gaurav has made a PR.

To release a new version of CORBA I’m waiting on a Jenkins CI issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=563774I raised in on the 31^st but there has been no activity so I will chase this.

 

We also need a new release of the JSON-B api and Yasson. There are a number of PRs and issues in JSON-B so if anybody is a committer on that project please merge Gaurav’s PRs and push out another RC.

 

We have a commitment for a June milestone release with everything having to be ready by June 12th.

My view is if we can fix the admin console deployment issues in Web Profile then we can just release Web Profile in the June milestone as that seems to work OK. Therefore please test Web Profile is working for you before making a PR. I don’t want it broken before June 12^th. Also hold off merging in any JDK 11 changes until after June 12^thas I think that will destabilise master. JDK 11 support can be the next push after the milestone build.

 

A stretch goal will be to get the Jakarta CORBA version out on staging and also have Full Profile but that is somewhat out of our hands.

 

Please try out Web Profile and if you have any PRs that make it more solid please get them in before 10^th June as I will code freeze then for the 12^th June release.

 

Thoughts?

 

Steve_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev