|Re: [jakartaee-platform-dev] [glassfish-dev] Status of GlassFish 6.0.0-M1|
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.
On Behalf Of arjan tijms
Sent: 03 June 2020 19:21
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: 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:
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.
jakartaee-platform-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
Back to the top