Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [glassfish-dev] Status of GlassFish 6.0.0-M1

Ahh, yes.  That makes sense, Steve.  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)    

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

The Eclipse GlassFish Orb project has explicit references to javax.transaction apis so these need changing to Jakarta.transaction. As GlassFish is OSGI it wants to resolve these at ORB startup and fails.


From:glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of arjan tijms
03 June 2020 19:21
jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Re: [glassfish-dev] [jakartaee-platform-dev] Status of GlassFish 6.0.0-M1




On Wed, Jun 3, 2020 at 8:08 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:

Okay, this looks like a case of an implementation (ie. Glassfish) continuing to provide a feature (ie. CORBA) that has been removed from the Platform.  Similar to an app server wishing to continue to provide jax-rpc or xml registries (jax-r).

But, I still have question why this CORBA orb would have to be converted to the jakarta namespace?  Since CORBA is not being picked up for continued support, wouldn't this stay in the javax namespace?  What am I missing?


GlassFish doesn't have both namespaces available at the same time. If the ORB declares a dependency on javax.*, then Felix (OSGi) will in most cases try to resolve that package during startup. If it's not found the startup is aborted. In some cases resolving is more dynamic, and will be done after startup, preventing something to work.


Kind regards,

Arjan Tijms

jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top