►
From YouTube: INDUSTRY SESSION - IBM, ORACLE, PAYARA
Description
JakartaOne Livestream is a one-day virtual conference for developers and technical business leaders that brings insights into the current state and future of Jakarta EE and related technologies focused on developing cloud-native technologies for enterprise Java applications.
Featured Speakers: Claudia Beisiegel, Gunnar Hillert, Steve Millidge
09:00-09:45 GMT-04
A
A
A
A
A
B
D
D
E
C
B
E
E
E
E
Okay,
can
you
see
that
right?
So
first,
I'm
going
to
talk
about
jakarta,
10
changes,
so
takashi
10
is
due
out
in
july,
and
ducati
10
is
a
big
deal,
because
it's
the
first
release
that
will
have
changes
from
in
the
underlying
apis
of
jakarta
e,
so
cartridge
eight
was
the
first
release
of
the
eclipse
foundation.
E
Cartridge
eight
was
basically
a
identical
api
released
to
java
ee-8
and
was
to
there
to
provide
api
compatibility
and
to
show
that
karchery
and
java
eu
were
effectively
equivalent.
To
that
point
in
time.
Takashi
9,
which
came
out
you
know
about.
I
can't
remember
18
months
ago
or
so
or
two
years
ago,
was
all
about
a
namespace
change
which
I'll
talk
about
from
the
javex
namespace
to
the
jakarta
namespace.
E
So
that
has
no
real
functional
benefit
for
people
was
really
there's
a
tool
release
to
for
vendors
to
get
their
tooling
and
their
products
used
to
the
jakarta
namespace
change
and
do
that
on
a
stable
platform
where
there
weren't
other
changes.
So
jakarta
10
is
a
big
deal
because
it's
the
first
release
that
has
substantive
changes
in
the
apis.
E
So
obviously,
the
first
big
thing
that,
if
you're
a
jakarta,
ee
or
java
e8
developer,
is
that
you
have
to
contend
with
is
the
name
space
so
on
the
namespace
change.
Everything
that
has
javx
is
moving
to
jakarta
and
obviously
that's
a
big
breaking
change.
So
all
the
apis
that
people
use
in
jakarta
e
will
need
to
be
moved
to
from
javex
to
jakarta
things
like
ejb
annotation
mail.
I've
highlighted
a
number
in
yellow
on
the
slide,
which
are
very
common
apis
and
very
common
in
applications.
E
So
this
impacts
jakarta
e
in
quite
a
big
way
as
a
developer,
because
you
need
to
do
that
migration,
you
need
to
to
run
on
a
jakarta
return
platform.
You
will
need
to
migrate
your
applications
to
this
new
namespace,
but
jakarta
e10
also
has
a
bigger,
wider
impact
on
the
industry,
as
many
of
these
apis
are
widely
used
in
other
frameworks.
E
E
The
next
major
part
of
jakarta
e10
is
the
java
version
has
been
uplifted
so
in
chicago
eight
and
nine
api
jars
were
compiled
at
jk8
in
jakarta
310.
They
will
be
compiled
at
jdk
11..
Now
that
may
seem.
You
know
not
that
modern
in
that
we
all
want
jdk
17,
but
all
that
means
is
that
the
apis
can
be
used
in
a
jdk
11
runtime.
E
It
doesn't
prevent
people
certifying
and
building
products
like
payara,
which
already
runs
on
jdk
17
and
running
those
on
jdk
17,
and
it
doesn't
prevent
your
application
from
using
jdk
17
apis.
So
if
you
want
to
use
jdk
17
an
absolutely
carter,
e10
will
support
it
and
we
can
test
as
a
vendor
and
application
server
rolling,
jdk
17.,
but
the
baseline
apis
are
compiled
at
11..
E
The
reason
we
do
that
is
just
to
make
sure
that
at
the
pure
api
level
and
classpath
level
that
we're
being
as
inclusive
as
we
can
and
incorporating
and
enabling
any
many
developers
to
use
the
apis
so
jakarta
10
had
a
number
of
goals
at
the
very
top
level.
At
the
steering
committee
level,
there
was
three
key
goals
that
we
wanted
to
achieve
with
jakarta
10..
E
The
first
was
modernization
so
one
what
we
did
around
modernization
first.
Is
we
removed
or
made
option
a
lot
of
deprecated
old
capabilities
or
features
of
of
previous
versions,
so
things
like
old
style,
cmp
entity
beans
which
people
remember
from
or
may
not
remember
from
many
many
years
ago,
can
now
be
completely
removed,
they're
nominated
as
optional,
so
we
can
still
ship
it,
but
other
vendors
or
other
implementations
can
completely
remove
it.
E
E
Jakarta,
javari
hadn't
been
moved
for
a
few
years,
so
support
for
completable
futures
for
joint
pools,
modern
things
in
in
the
latest
versions
of
java
was
up
to
a
java.
Sc
11
was
brought
into
api,
so
apis
could
use
date
time
we're
also
introducing
jpms
metadata
for
every
api,
and
so
that's
that
was
the
key
goal
on
the
modernization.
E
It
was
also
simplification
as
well,
so
we
wanted
to
bring
in
broader
use
of
annotations
for
deployment
across
the
platform.
For
example,
you
know
in
previously
in
java,
8
many
people
still
don't
use
this,
but
it's
possible
to
define
data
sources
through
annotations.
You
don't
need
deployment
descriptors.
For
that,
you
don't
need
to
use
vendor
tools
to
create
data
sources.
E
Finally,
lightweight
was
a
key
theme
again.
Simplification
and
pruning
makes
the
platform
more
lightweight,
but,
however,
we
also
introduced
something
called
the
core
profile
and
the
core
profile
is
a
reduced
set
of
apis,
designed
for
more
to
support
more
light
for
weight
frameworks,
lightweight
applications.
E
One
of
the
key
benefits
that
I
see
around
chicago
10
is
it.
It
gives
life
for
other
vendors
and
other
frameworks
to
to
join
jakarta
ee
and
deliver
runtimes
for
developers.
That
may
not
been
able
to
do
so
before
because
of
the
lot
of
the
legacy
and
and
fat
that
was
in
from
many
years
ago
because
of
the
breaking
changes
in
the
name.
Space
there's
been
different,
been
the
ability
to
bring
in
other
breaking
changes
in
different
apis.
E
E
So
there's
a
lot
of
new
capability,
a
lot
of
new
features
in
jakarta
310.
I
have
a
couple
of
slides
where
I'll
go
through
some
of
them
very
briefly,
and
then
that's
just
a
flavor
really
so
there's
quite
a
lot
of
change
and
there's
quite
a
lot.
Some
of
it
is
breaking
and
some
of
it's
not
anything
with
the
dot.
Zero
was
allowed
to
do
breaking
changes.
E
E
E
E
So
that's
bringing
in
innovation
from
that
was
originally
a
microprofile
around
context,
propagation,
bringing
that
into
jakarta
ee
to
more
sub
support
context,
propagation
scenarios,
where
what
I
mean
by
that
is
that
so
the
context
to
run
in
asynchronously
in
jakarta
so
including
security
context,
transactional
context.
You
know
the
the
ability
to
inject
beans
or
those
things
which
is
tricky
and
if
you
just
use
raw
threads
and
that
was
upgraded
to
support
computable
futures
fork.
Joint
pools
has
managed
executive
services
and
things
like
that
faces
has
had
a
big
update.
E
A
lot
of
stuff's
been
removed,
so
jsp
support
and
managed
beans
is
gone
and
again
it's
again.
It's
been
more
unifying
on
top
of
cdi.
Jakarta
arrest
has
had
a
minor
update.
I
think
they're
waiting
for
the
next
release
for
their
big
major
update,
but
it
has
some
capabilities
around
multi-form
part
forms.
It
has
a
new
bootstrap
api
again,
which
helps
people
building
core
profile,
implementations.
E
So
that's
a
major
release.
A
breaking
change
securities
bring
up
brought
in
new
micro
services
and
and
web
oriented
authentication
that
open
id
you
know,
auth
and
json
b
has
brought
polymorphic
types
and
jpa
has
a
a
lot
of
sort
of
minor
updates
which
are
quality
of
life
updates,
which,
which
are
which
are
great
to
see.
E
So,
with
jakarta
in
10
being
a
breaking
change,
I
just
wanted
to
touch
on
payara
pira6
and
how
we're
supporting
jakarta,
310,
so
pyro
6,
alpha
2,
was
released
quite
a
while
ago.
Now,
sometime
at
the
beginning
of
the
year,
that
is
was
essentially
the
second
release
of
our
first
development
stream.
If
you
like
on
pyora,
so
we
did
designate
an
alpha
if
it's
not
functionally
complete.
E
That
was
certified
chicago
nine
compatible.
So
that
was
the
first
step
for
us
to
take
that
jakarta,
9,
tooling,
release
and
make
sure
that
we
could
port
the
whole
server.
So
it
runs
on
the
new
namespace
and
achieves
basically
the
equivalent
function,
a
functionality
of
jakarta
eight,
but
on
the
new
namespace.
E
E
E
So
the
way
we're
supporting
both
jakarta
and
jakarta,
eight
and
jakarta
10
is
on
this
slide.
So
at
the
minute
in
power
5
community
or
at
the
top
of
the
top
of
the
chart
you
can.
It
is
essentially
a
jakarta
8
runtime,
but
you
can
currently
deploy
jakarta,
39
applications
and
what
it
does
internally
is.
E
Then
we're
intending
to
embed
abilities
for
jakarta,
eight
apps
to
be
transformed
to
jakarta
10.,
and
that
means
going
the
other
way.
That
means
taking
the
javex
namespace
and
moving
it
to
the
jakarta
namespace,
and
we
do
that
as
far
as
we
can.
Obviously,
there
are
breaking
changes.
For
example,
if
faces
users
manage
beans,
then
you
you
may
have
to
do
some
code
changes
as
well,
so
to
put
that
on
a
on
a
another
slide.
E
There
will
be
a
bit
of
an
overlap
and
we'll
do
a
final
five
sometime
after
our
sixth
release,
just
to
roll
up
any
major
bugs
and
things
that
we
have
have
left
lying
around
and
then
currently
on
the
enterprise
stream.
We
still
support
java,
e7
applications
right
up
to
2025
and
that
again
it
still
supports
jdk
7
as
well.
E
E
E
E
We
also
have
a
whole
lot
of
assistance
and
accelerator,
which
is
our
consultancy
to
help
people
migrate
to
jakarta.
310
we're
also
providing
tooling
command
line
tooling
and
upgrade
advisors
that
will
basically
take
people's
raw
files,
transform
them
to
the
latest
name
space
and
also
advise
where
incompatibilities
may
arise
between
8
and
10
and
which
areas
where
application
features
may
have
disappeared
or
api
features
are
no
longer
available.