►
From YouTube: Jakarta EE Roadmap | JakartaOne Livestream 2021
Description
2021 was an exciting year for Jakarta EE! Major Platform releases as well as individual Component releases through out the year. And, more feature content planned for 2022! Jump on the Jakarta EE bandwagon and learn about the pent-up demand for this cloud-native Java programming model.
____
Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.
Learn more: https://jakarta.ee/
Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/
A
So
let
me
just
welcome
first
of
all,
kevin
sutter.
It
is
a
very
special
day
today
for
us
here,
not
just
because
we
have
a
live
stream
here,
but
because
we
have
a
opportunity
to
share
a
special
day
that
is
special
for
cabinet
as
well.
So
I
want
to
congratulate
kevin
on
his
retirement
and
I
also
wanna
say
that
it
is
an
honor
for
jakarta
and
microprofile
community
to
be
part
of
of
the
retirement
today.
A
For
for
for
kevin,
it
is
privileged
to
work
with
kevin
and
I'm
sure
that
everyone
will
agree
that
his
knowledge,
wisdom,
kindness
and
guidance
made
a
huge
difference
to
both
jakarta
and
microprofile
communities.
I'm
sure
there
are
other
communities,
but
those
are
the
closest
to
our
hearts
and
those
are
the
ones
that
we're
highlighting
today.
A
B
B
Okay,
well,
thank
you
very
much
for
the
very
nice
introduction
you
can
see
on
this
first
page
I
am
still
with
ibm.
I
don't
officially
retire
until
the
end
of
the
year,
but
this
is
my
last
official
activity
for
ibm.
It
was
the
ducati
or
jakarta
one,
so
I
think
it's
kind
of
fitting
with
all
of
the
activity
with
with
jakarta,
jakarta,
ee
and
even
microprofile,
and
to
finish
it
up
with
this
conference.
B
So
tiny,
already
kind
of
covered
a
lot
of
this
stuff,
I'd
like
to
include
a
quick
bio
just
for
the
people
on
the
call
that
I
haven't
met.
Yet
I
have
been
driving
the
releases
for
jakarta,
e9
and
9.1,
and
I
led
the
creation
of
the
release
plan
for
jakarta
ee10.
But
now
that
was
handed
off
and
scott
stark
is
going
to
be
taking
the
reins
and
he's
going
to
be
driving
the
ducati
e10
release.
B
So
it's
in
good
hands,
like
tanya,
said
I've
been
involved
with
java,
ee
and
jakarta
ee
for
a
long
time
and
with
many
different
aspects
of
jakarta
ee,
both
from
the
technical
side
as
well
as
the
business
side,
and
I
am
one
of
the
original
members
of
the
micro
profile
project,
which
is
a
very
close
cousin
to
jakarta
ee.
So
just
involved
with
everything
related
to
the
cloud
native
java
in
the
eclipse
environment.
B
B
B
A
B
Ee9,
the
big
change
there
was
to
move
to
the
jakarta.
Namespace
and
people
have
used
the
term.
The
big
bang
release,
because
everything
that
was
using
java
x
had
to
be
changed
to
jakarta,
and
so
it
was
all
the
specifications
all
the
apis
and
the
tcks
and
and
the
compatible
implementations,
and
it
was
a
large
large
effort
across
the
industry.
It
not
only
affected
the
things
related
to
jakarta
ee.
You
know
from
an
application
server
perspective,
but
also
the
other
tools
that
we
all
use
to
develop
these
applications.
B
B
We
really
limited
what
went
into
ducati
e9
outside
of
the
name
space
change,
because
we
really
you
know
we
knew
this
was
going
to
be
big
and
we
didn't
want
to
clutter
it
with
additional
features
that
were
coming
in
very
early
on
on
jakarta
e9.
We
kind
of
figured
out
that
we
aren't
that
we
were
not
going
to
be
able
to
get
the
java
se11
support
in
the
same
time
frame.
B
We
are
up
to
java
sc
11
support
that
provides
a
very
oh
I'm
getting
ahead
a
little
bit.
One
of
the
things
I
want
to
point
out
are
the
number
of
compatible
implementations-
and
I
know
mike
mentioned
this
on
the
keynote
on
the
number
of
compatible
products
and
he
expanded
it
across
all
of
the
releases
for
jakarta
ee,
and
I
think
he
said
that
there
were
23
total.
B
It
was
somewhere
around
there
and
so
for
what
I
have
here
is
9.1,
and
so
we
have
nine
full
platform
compatible
products
for
9.1
that
just
completed
in
may.
So
you
know
keep
that
in
mind
so
six
months
ago
and
we
have
nine
products
that
are
fully
compatible
with
the
platform
and
four
with
the
web
profile
and
that
that
is
just
fantastic
for
the
industry
to
show
that
growth
and
that
dedication
to
this
platform.
B
You
know
providing
the
new
foundation
going
forward
and
we
even
use
that
as
part
of
our
mantra
for
nine
and
nine
point,
one
that's
providing
new
foundation
for
innovation,
and
so
now
what
that?
What
that
showed?
When
I
started
to
look
into
the
ducati
10
release
plan,
is
there
was
so
much
pent
up
demand
for
new
features?
I
and
you'll
notice
this
here,
12
component
specifications
are
going
to
be
coming
out
with
a
major
version
update
now
semantic
versioning.
If
you
think
about
this
major
version
update,
that
means
that
there
are
some
breaking
api
changes.
B
B
We
can
move
beyond
that
and
we
can
start
to
clean
out
some
of
that
dead
weight,
and
so
that's
what
some
of
these
component
specifications
are
doing
for
a
major
version
update
and
beyond
that
we've
got
12
more
component
specifications
that
are
doing
a
minor
version
update,
so
they
still
may
be
doing
new
features
and
bug
fixes,
but
they
are
not
breaking
their
apis
at
all.
So
you
can
look
at
that
and
there's
24
components
that
are
going
to
be
going
through
some
type
of
update
for
jakarta,
ee
10
and
that
that's
that's
major.
B
That
shows
that
pent
up
demand,
probably
the
biggest
item
that
is
on
our
list.
Is
this
new
core
profile?
You
know
for
a
long
time
we've
had
the
web
profile
and
the
core
profile
is
a
new.
It's
a
smaller
set
of
jaccardi
technologies,
and
these
technologies
are
targeting
the
microservice
and
and
cloud
native
development.
Runtimes.
B
One
other
thing
that
we're
doing
is
kind
of
redefining
the
platform
requirements,
so
jacardi
ee
platform
has
always
had
these
requirements
for
the
ejb
entity
beans
and
the
embeddable
ejb
container.
Now
those
features
are
not
going
to
be
removed
from
you
know
the
the
actual
ejb
specification
they
are
still
there.
We
can
still
test
them.
You
know
they're
they're
still
going
to
be
specked
out,
but
the
requirement
to
have
ejb
entity
beans
and
the
embeddable
ejb
container
for
the
platform
is
going
to
be
removed
from
the
specification.
B
So
I've
got
a
little
bit
more
detail
on
that.
Coming
up,
we
had
the
goal
of
delivering
in
first
quarter
and
I
noticed
that
mike's
chart
wasn't
updated
yet,
but
just
you
know
in
the
last
couple
of
weeks
we've
kind
of
figured
out
that
that
just
is
not
going
to
happen
so
we're
pushing
it
out
the
second
quarter
of
2022
and
we'll.
Hopefully
we
we
will
get
that
one
done.
B
These
charts,
they're
gonna
look
repetitive,
and
I
I
apologize
to
that,
but
I
was
trying
to
get
a
model
down
so
every
one
of
the
charts
that
follow
they're,
going
to
have
an
item
at
the
top
for
the
specification
record
and
for
the
release
record
for
the
components
that
I'm
talking
about
now.
The
reason
I'm
doing
doing
it
this
way
and
the
pdf
that
you
will
eventually
get
all
these
links
are
available
to
you.
B
So
I'm
gonna
just
show
this
on
the
platform
and
then
the
the
other
ones
I
won't
be
showing
the
individual
ones,
but
the
specification
record.
These
are
the
ones
that
are
from
the
specifications
that
are
out
under
jakarta.ee,
and
so
this
is
where
all
the
specifications
are
housed.
When
we
go
through
the
you
know,
the
schedule,
the
compatible
implementations,
the
different
ballots
that
are
done
for
the
plan
review
and
release
review-
that's
where
all
of
this
is
held.
Okay.
B
Now,
if
I
come
back
here,
the
release
record
now
we're
getting
to
the
eclipse
metadata
associated
with
each
project.
So
this
is
the
release
record
for
jakarta,
ee10
and,
and
you
can
see
it
has
a
link
to
the
release
plan.
But
what
I
really
want
to
point
out
is,
if
you
back
up
one
level
here
to
the
platform
project,
every
one
of
these
projects,
you
can
take
a
look
at
and
see.
Okay,
here's
all
the
different
releases.
B
If
I
click
on
who's
involved,
you
can
see
all
the
different
people
and
companies
that
are
involved
with
developing
the
platform
project.
You
can
look
at
the
developer
resources.
These
are
all
of
the
repositories
that
are
associated
with
this
project
and
if
you
need
to
contact
anybody
on
this
project,
then
there's
a
mailing
list
that
you
can
subscribe
to
and
participate
on.
So
getting
back
to
this.
B
B
I
believe
all
of
them
are
moving
to
java
se11
there's
a
handful
of
specifications
that
are
not
looking
to
make
any
updates
for
jakarta
e10,
so
we're
not
forcing
them
to
move
to
java
se11
they
they
are
still
strongly
recommended
to
do
so,
but
it's
not
a
requirement,
but
at
the
same
time
we
do
want
to
look
forward
to
javasc,
11
and
java
se
17
run
times.
So
we
want
we're
going
to
enforce
that.
The
tck
can
be
executed
using
both
of
those
runtimes.
B
B
Most
of
the
components
already
have
one
of
these,
but
in
case
some
of
the
components
don't
have
one
we
we
are
now
going
to
require
it
in
jakarta,
ee10,
jakarta
concurrency
is
going
to
be
moved
from
the
platform
definition
to
the
web
profile
and
that
that's
just
it's
a
it's
a
move.
That's
been
talked
about
for
quite
some
time,
and
you
know
we
took
a
vote
and
a
ballot
and
decided
that
was
the
way
to
go,
and
then
I
mentioned
this
already
that
we're
removing
two
items
from
the
platform
requirements.
B
B
C
B
I
think
it
was
in
java
ee
when
the
web
profile
was
first
introduced.
There
has
been
no
other
profiles
defined
it.
The
platform
spec
talks
about
profiles,
but
there's
only
been
the
one
web
profile.
Now
we
are
coming
out
with
a
core
profile
and
the
idea
of
this
core
profile
is
to
target
the
small
microservice
cloud-based
runtimes.
B
So
if
any
of
you
are
familiar
with
microprofile
there's
been
a
subset
of
jakarta
specifications
and
java
ee
specifications
that
we
have
targeted
as
just
kind
of
like
being
the
base
so
from
jakarta,
ee
there's
certain
ones
that
were
required
as
a
base
for
biker
profile.
Well,
that's
kind
of
grown
into
this
core
profile
idea.
B
So
now
this
core
profile
would
include
annotations
cdi,
lite,
not
the
full
cdi
and
I'll
talk
a
little
bit
about
what
the
difference
is
there
on
a
later
chart,
dependency,
injection
expression,
language,
interceptors,
json,
b
and
p
restful
web
services
or
jax
rs
is
more
familiar,
and
originally
we
were
talking
about
having
config
1.0,
but
that's
not
moving
as
fast
as
what
we
had
hoped.
So
I
don't
think
that's
going
to
make
the
core
profile
10,
but
I
know
that
they're
still
working
on
it.
B
So
for
the
next
set
of
charts,
these
are
all
of
the
core
or
the
the
component
specifications
that
are
going
through
a
major
version
update,
and
so
what
I've
tried
to
do
is
to
highlight
the
items
that
are
causing
that
major
version
update.
You
know
what
what
is
changing
in
the
api,
that's
going
to
say:
oh
yeah,
okay,
I
have
to
be
aware
of
this
because
now
2.1
is
not
going
to
be
compatible
with
3.0
from
a
api
perspective,
so
I
tried
to
highlight
all
of
those
type
of
changes.
B
Now
I
had
to
abbreviate
because
you
know
we
only
have
so
much
time
so
for
any
of
these.
If
you're
interested
in
more
detail,
then
I
would
reference
the
specification
record
and
the
release
records
for
more
detail
and
then,
if
you
really
want
to
get
involved
contact
the
development
teams
that
are
developing
these
specifications,
so
the
big
thing
with
the
jakarta
authentication
is
that
we
are
defining
a
couple
of
new
profiles
for
servlets
and
restful
web
services.
Now
just
a
quick
explanation.
B
B
B
If
any
of
you
are
familiar
with
those
the
mica
profile
context,
propagation
from
day
one,
it
was
highlighted
as
being
an
extension
to
jakarta,
concurrency
and
eventually
it
would
merge
in
but
because
jakarta
was
so
busy
just
trying
to
get
set
up
and
incorporated.
You
know
moving
from
java
x
to
jakarta,
we
went
ahead
with
a
profile
to
come
up
with
context
propagation
and
now
it's
time
to
move
that
back
into
jakarta
concurrency.
So
that's
the
big
change,
that's
happening
for
the
3.0
release.
B
Okay,
I've
mentioned
this
already.
The
config
1.0
you'll
notice.
Here
the
two
records
the
specification
record,
release
record.
They
aren't
completed
yet
they
aren't
even
created.
So
that's
part
of
the
reason
you
know:
there's
no
links
it
just
isn't
far
enough
along
to
really
make
sure
that
it's
going
to
make
jicardi
e10.
So
if
I'm
a
betting
man,
what
I
would
say
is
it's
not
going
to
be
part
of
jakarta
e10,
but
I
know
that
they're
going
to
continue
to
push
on
this.
B
To
try
and
get
config
1.0
available
as
soon
as
they
can
here
again.
This
is
another
specification
that
started
in
microprofile,
so
we've
had
mica
profile
config
for
several
releases.
I
think
emily
said
we're
on
our
fifth
year.
I
think
with
microprofile
config
and
so
part
of
this
discussion
is
trying
to
figure
out
okay.
B
Okay,
cdi
4.0:
this
is
going
through
quite
a
major
change
for
jakarta
e10.
I
don't
know
why
the
specification
record
hasn't
been
created,
yet
it's
not
out
there.
That's
just
a
bug.
I
I've
mentioned
it
to
people,
and
so
eventually
that'll
get
that'll
get
fixed,
but
the
release
record
is
available
and
you
can
go
out
there
to
see
the
details
as
to
what's
coming.
B
The
big
thing
is
cdi
has
to
be.
You
know,
kind
of
split
up
into
separate
specifications.
It's
just
been
getting
too
big
that
component
model
and
all
of
the
things
associated
with
it.
It
was
just
getting
too
cumbersome,
and
so
they
really
need
to
break
it.
Apart
into
separate
specifications,
the
big
well
shouldn't
say
big
because
we're
trying
to
go
light
but
we're
trying
to
come
up
with
a
new
cdi
light
specification
and
the
idea
is
this
would
be
targeted
for
that
core
profile.
B
The
tck
has
to
follow
suit,
so
then
the
tck,
the
application
server
environment,
is
not
going
to
be
required
for
every
one
of
the
specifications
you
know
cdi.
Lite
will
probably
just
be
a
java
se
environment,
and
so
then
the
application
server
isn't
required.
So
there's
a
lot
of
work
that
needs
to
be
done
with
cdi
4.0
for
jakarta,
ee10.
B
Okay,
expression,
language
5.0,
you
know
normally
I
you
know
people
just
kind
of
use,
the
expression
language
and
they
don't
really
think
about
it,
going
through
a
lot
of
changes-
and
you
know
this
major
update
they're
wondering
what
what
the
heck
is
happening
here
with
the
expression
language,
because
that
shouldn't
be
changing
well.
The
big
thing
is:
there's
a
lot
of
deprecated
apis
and
methods
that
just
need
to
be
removed.
B
They
have
been
there
since
day,
one
nobody's
using
them,
let's
get
them
out
of
the
way
so
that
we
can
have
a
more
skinny
version
of
the
expression
language
related
to
that.
For
some
reason
there
was
a
jpms
module
dependency
on
java.desktop
and
we
need
to
remove
that
to
clean
that
up.
So
that's
that's
some
of
the
work
that
needs
to
be
done
for
the
expression
language
for
the
major
version.
B
So
this
this
chart
here
reminds
me
every
one
of
the
charts
I
was
trying
to
find
some
image
or
icon
that
would
indicate
you
know,
demonstrate
the
technology
well
expression.
Language
just
does
not
have
a
whole
lot.
You
know
as
far
as
finding
images
or
an
icon-
or
you
know,
logo
or
whatever,
but
I
did
find
this
spanish
book
on
expression,
language
with
faceless
and
I
know
facelifts
are
you
know
little
old
technology,
but
at
least
I
found
something
related
to
expression,
language,
you'll
notice
on
a
future
chart.
B
B
So
json,
b
3.0,
the
big
thing
here-
is
defining
optional
parameters
for
the
json
b.
Creator
annotation
and
that's
going
to
you
know,
throw
a
little
wrench
into
that
annotation
and
so
that
that
kind
of
breaks
that
the
the
api.
From
that
perspective,
I'm
pointing
one
thing
out
here
with
the
footnote:
the
jakarta,
the
official
ducati
e10
release
plan
still
states
json
b.
2.1
recently,
dimitri
took
us
all
through
a
new
release
plan
for
3.0,
so
3.0
is
approved.
B
B
They
are
also
looking
at
adding
a
couple
of
new
features
with
some
additional
authentication
mechanisms,
and
I
know
that
they're
talking
about
open
id
connect
and
oauth
2.
there's
a
couple,
others
that
are
being
discussed,
but
I
don't
know
if
they're
going
to
make
it,
but
I
think
these
two
will
make
it
for
sure.
B
Okay,
jakarta
server
faces.
You
know
it
seems
like
every
java
ee
release
every
jakarta
ee
release.
People
are
always
talking
about.
Okay,
jsf,
it's
dead,
you
know,
let's
move
forward,
but
every
release.
There
is
more
and
more
interest
with
jsf
and
they
get
you
know
not
only
the
team
itself,
but
they
get
assistance
from
people.
They
get
feedback,
they
get
input,
so
jsf
is
alive
and
well.
B
So
if
you
ever
hear
that
you
know
it's
dead,
just
don't
believe
it,
because
it
is
one
of
the
most
active
teams
that
I
have
experienced
with
on
both
java
ee
and
jakarta
ee,
but
they
need
to
move
that
api
forward.
So
the
same
thing
I've
mentioned
on
a
couple,
others
there's
some
deprecated
apis
that
just
need
to
be
removed
and
they
want
to
identify
some
additional
deprecations
for
future
removal.
B
So
it's
going
to
be
okay,
get
rid
of
the
old
mention
some
others
that
are
getting
old
and
then
advance
the
current
api
and
the
big
advance
is
by
utilizing
cdi.
So,
let's
get
on
to
the
current
component
model
and
utilize
cdi
now
my
image
here
you
can
see.
I
kind
of
you
know
plagiarized
this
a
little
bit.
B
B
B
B
So
we've
got
the
the
3.0
release
and
the
big
thing
here
is
dropping
the
deprecated
dom
api
extension.
So
that's
a
very
old
object,
model
type
extension
and
it's
just
no
longer
required,
and
so
they're
going
to
be
dropping
that
and
there's
a
few
other
additional
features
and
bug
fixes.
But
that's
the
big
item:
that's
forcing
the
major
version
update.
B
B
B
Those
uris
will
be
changed
to
jakarta.tags,
or
maybe
it's
jakarta.something
else,
but
moving
them
to
the
jakarta
namespace
so
that
that's
the
big
breaking
change
for
that
api
here
was
the
other
icon
or
the
image
that
I
came
up
with.
I
found
one
that
said
fun
with
jstl
and
el.
Now
I
don't
know
it
seems
kind
of
weird
to
say
that
you're
gonna
have
fun
with
these
type
of
technologies,
but
this
was
the
other
reference
to
the
expression
language
that
I
did
find.
So
there
were
two
of
them.
B
Okay,
jakarta
xml
binding
here
again,
moving
up
in
a
major
version
released
because
one
thing:
removing
the
java
beans
dependency
and
the
bigger
thing
is
removal
of
the
jax
b1
api
from
the
specification
that
is
just
not
being
utilized
at
all,
and
it
was
time
to
get
rid
of
it
and
again
modernize
the
api.
Let's
move
up
to
the
you
know
new
stuff,
so
this
update
to
a
major
version
for
jax
b
that
has
a
little
bit
of
a
ripple
effect,
because
this
here
the
xml
web
services.
B
This
is
also
going
up
by
a
major
version
update
and
the
main
thing
is
because
of
the
dependency
on
xml
binding.
Now
here
again
the
xml
web
services.
It's
an
optional
feature,
so
products
that
are
trying
to
be
compliant
don't
have
to
implement
it.
But
we
still
have
several
application
servers
that
support
soap
and
web
services,
and
so
we
will
continue
to
to
provide
updates
to
them,
and
so,
besides
xml
binding
update
to
4.0.
B
The
other
thing
that
lucas
is
looking
to
do
is
trying
to
combine
all
of
these
specifications.
The
specifications
for
xml
web
services,
web
services
metadata
and
the
soap
with
attachments,
they're
all
very
small
specifications
and
they're
all
very
tightly
coupled
and
interrelated.
So
lucas
is
looking
at
this
and
saying
you
know
why?
Don't
we
just
combine
all
of
them
into
a
single
specification
and
take
that
forward,
and
so
that's
what
he's
looking
to
do
with
web
services?
4.0.
B
Okay,
so
let's
see
where
okay
I'm
doing
okay,
so
those
were
all
of
the
major
version
updates.
This
page
here
highlights
all
of
the
specifications
that
will
be
going
through
a
minor
version
update.
Now,
I'm
not
going
to
go
into
all
the
detail
like
what
I
just
did
with
the
major
version
updates,
because
I
wanted
to
highlight
those
breaking
api
changes,
but
for
this
case
for
the
minor
version
I
kind
of
summarized
them-
and
I
read
through
them
and
tried
to
say:
okay,
what's
common
well,
the
big
thing
is
updates.
B
I
also
mentioned
the
module
info
class.
That's
a
requirement!
There
will
be
several
minor
feature
updates
and
bug
fixes,
but
the
key
thing
here
with
these
is
no
breaking
api
changes.
Now
I
did
make
a
couple
of
footnotes
here
so,
for
example,
activation
the
release
plan
had
indicated
that
activation
was
not
going
to
be
making
an
update,
but
through
the
investigation-
and
you
know
looking
at
what
was
required-
there
was
a
small
change
that
needed
to
be
done.
B
So
there
will
be
a
2.1
for
jakarta
authorization
that
one
originally
had
been
identified
as
being
a
major
version
update
of
3.0.
So
that's
what
we
thought
we
were
doing
for
the
release
plan
as
that
team
dove
into
it.
They
figured
out
that
no,
we
really
don't
need
to
do
that.
Let's
cut
it
back,
let's
do
the
2.1
and
we'll
just
do
a
service
update.
I
mean
a
minor
version
update
and
then
for
jax
rs.
B
B
This
is
the
set
of
specifications
that
are
not
requiring
any
changes.
Now
I
have
three
of
them
marked
with
a
footnote
that
there
may
be
some
changes
here
that
might
require
a
minor
version
update
because
of
the
reorganization
of
cdi,
4.0,
they're,
re-evaluating
or
looking
at
all
the
dependencies
with
cdi,
and
how
does
that
affect
injection,
interceptors
and
transactions
and
whether
or
not
a
minor
version
might
be
required
for
that
it
hasn't
been
determined.
B
Yet
if
it
is
they'll,
take
it
through
the
process
of
getting
a
release
plan
and
getting
that
all
approved,
and
then
we'll
have
to
update
the
jakarta
e10
release
plan
again,
but
right
now.
This
is
the
plan
of
record,
so
these
specifications
may
go
through
a
service
release.
That
would
be
the
third
digit.
B
B
C
B
Had
several
releases,
I
think
it
went
from
1
to
2.0
and
now
2.1
in
order
to
support
jakarta
e9.
It
just
hasn't
made
it
into
the
platform
spec
yet,
and
whether
it's
platform
or
web
profile
that's
still
being
discussed.
It
came
close
for
jakarta
ee10,
but
at
the
end,
they,
you
know
through
the
discussions
and
voting
and
ballots,
it
was
just
decided,
just
wasn't
quite
ready
to
be
included
in
the
platform
yet,
but
I
could
see
it
happening
down
the
road
there's.
B
Also
a
jakarta
nosql,
that's
a
new
project,
that's
still
being
developed,
it's
at
the
1.0
phase,
don't
know
if
that
will
ever
become
part
of
the
platform
or
not,
but
it's
out
there
being
worked
and
the
newest
one
is
a
proposal
that
just
came
out
like
within
the
last
two
three
weeks,
and
this
is
for
jakarta
rpc
now
the
name
I
mentioned
here.
It
needs
a
new
name.
B
That's
already
been
highlighted
because
we
don't
want
it
to
be
confused
with
jax
our
pc,
because
this
thing
is
going
to
be
more
than
what
that
project
had
provided
in
the
past.
So
we
have
to
come
up
with
a
new
name,
but
the
idea
there.
You
know
that
the
proposal,
the
link
is
there,
so
you
can
go
and
take
a
look
to
see
what's
coming
and
then
I
did
dot
dot
dot
because
there
is
constantly
new
discussions
and
ideas
for
additional
function,
whether
it's
in
jakarta
or
even
like
your
profile.
B
B
Okay,
so
for
the
summary
I
put
in
links
here,
the
release
plan,
which
was
approved
in
august,
the
project
board.
Okay.
So
when
I
drove
jakarta,
e9
and
9.1,
I
used
the
project
boards
quite
a
bit
because
they
gave
a
nice
visual
representation
of
where
we
were
at
so
far.
They
aren't
being
used
a
whole
lot
for
ducati
10.
Maybe
they
will
at
a
later
time,
but
right
now,
they're,
pretty
empty
scott
stark
had
created
this
cardi
e10
wiki.
So
that's
a
good
place
to
go.
B
So
because
of
all
that
work,
I've
mentioned
already
we're
moving
to
second
quarter
2022
and
we
have
a
lot
of
work
left
to
do.
You
know
the
component
specifications
apis,
tcks,
compatible
implementations
and
especially
with
the
major
version
updates.
We
can't
just
go
from
you
know:
boom
we're
going
to
vote
on
a
major
version
update.
We
need
early
rc
versions
of
these
apis
of
the
tcks
of
the
compatible
implementations
to
show
progress,
to
show
that
we're
getting
there,
and
then
we
can
do
the
final
ballot.
B
Once
those
are
done,
then
those
components
feed
into
the
platform
web
profile
core
profile,
and
so
then
we
need
to
be
ready
with
our
specs
apis
tcks
and
compatible
implementations,
and
I
would
guess
we
go
through
the
same
thing
with
early
release.
Candidates,
and
the
thing
I
want
to
highlight
on
this
page
is
we're
always
looking
for
additional
volunteers
and
that's
how
I
came
up
with
the
logo
on
this
one.
B
For
the
jakarta
ee
ambassadors,
this
link
here
is
a
very
nice
article
that
was
put
together
by
the
ambassadors
that
talks
about
all
the
different
ways
that
you
can
help
out
with
jakarta
ee10
and
whether
you're
contributing
code
contributing
words
to
a
spec
reviewing
a
spec.
I
had
one
person
help
with
the
platform
spec
for
redoing
all
of
our
images
into
svg
format.
C
B
Evar
or
tanya
can
speak
up
well,
while
we're
waiting.
I
did
have
one
final
thing.
I
really.
I
had
no
idea
that
the
eclipse
foundation
and
the
ducati
community
was
going
to
do
that
nice
video
beforehand.
So
what
I
did
here
is
just
to
announce
my
retirement.
What
I
was
going
to
do
at
this
point
is
move
to
the
next
chart.
That
shows
that
ibm
is
no
longer
there
and
I'm
dropping
the
mic
to
say
that
I'm
done
presenting.
So
that's
how
I
was
going
to
end
my
presentation.