►
Description
Arjan Tijms and Ivar Grimstad discuss all things cloud native java in this Studio Jakarta EE session at JakartaOne Livestream 2020
A
B
B
B
B
A
A
B
B
Than
we
thought
before,
when
the
spec
was
just
transferred,
some
people
are
already
talking
about.
Okay
and
now
we
can
do
all
those
great
new
things
and
we
can
design
the
world
and
then
we
still
have
to
do
this.
Karta
ee
8
release
with
the
changed
spec
process.
Then
we
had
to
do
the
namespace
change
and
update
all
the
components,
and
this
took
quite
a
bit
of
time
but
yeah,
I'm
happy
that
it's
finally
done.
A
Yeah
and
one
of
the
things
we
did,
that
was
actually
for
for
jakarta
eight,
and
we
just
talked
about
it
that
that
we
we
change,
how
we
call
things
like
jax,
rs,
isn't
jack
sores
anymore,
it's
jakarta,
restful,
web
services,
and
and
this
morning
we
saw
an
important
examples
of
why
it's
important
to
say
things
like
this,
because
on
the
mainland
somebody
mentioned
el3,
and
what
what
could
that
mean?
What
was
the
ambiguity
there.
B
Yeah,
so
I
immediately
thought
about
expression,
language,
since
that's
most
often
abbreviated
to
el
and
even
the
version
number
matched
el
3.0.
So
I
was
thinking
this
other
person
was
talking
about
that
and
then,
after
some
confused
emails,
it
appeared.
He
was
talking
about
eclipse,
link,
yeah
and
at
some
point
it
just
hits
me
like
a
for
eclipse.
Alpha
link.
Oh
my
gosh,
it's
eclipse
link!
B
I
think
it
was
a
java
land.
The
two
years
ago,
when
we
two
talked
about
this
yeah,
we
said
it
might
be
better
to
go
for
just
simple
names:
don't
have
all
those
filler
things
like
jakarta,
persistence,
architecture
or
java
messaging
surface
concurrency
details
like
all
those
extra
words
like
architecture,
api
service
details.
I
mean
what
does
it
really
add
to
the
specs,
the
video
api,
so
all
those
words.
B
What
you
do
it's,
it's
called
piranha,
piranha
clouds
and
it's
a
new
full,
jakarta
platform
runtime,
and
what
makes
it
different
to
the
existing
servers
is
that
for
piranha
we
try
to
to
not
focus
so
much
on
the
application
server
bits.
So,
in
the
past
java
ee
jakarta,
ee
now
has
been
quite
entangled
with
this
application
server
concept,
where
you
start
application
server,
you
deploy
your
applications
to
it.
B
B
This,
of
course,
has
its
own
value,
but
we
discovered
this
gap
in
the
market
where
there's
a
demand
for
essentially
just
a
runtime,
so
a
minimal
just
a
minimal
amount
of
server
bits
to
get
all
the
components
working
together
and
also
allows
you
to
build
up
this
surface
minimal
server,
quite
programmatically
and
without
necessarily
having
a
deployment
having
an
http
server.
Even
so,
you
can
just.
B
B
Some
remote
egb
things
are
still
there.
They're
mandatory
for
the
full
platform.
On
the
other
hand,
there's
a
lot
of
simplification
in
egb,
like
the
egb
2.x
group,
api
group
is
optional.
Now
the
the
cover
the
interoperability
there
is
optional,
so
we
might
even
give
the
full
profile
a
go,
but
the
first
aim
would
be
for
the
web
profile
still
so
that
we
can
just
have
a
simpler
version
of
pgb.
Egb
lite
have
the
minimal
amount
of
apis
that
are
easiest
to
pass
the
tck
for,
and
so.
A
B
A
A
little
short,
but
there
is
one
question
here
and
it's
it's
actually
not
about
piranha.
It's
about
your
former
employer,
payara
and
they're.
Asking
is
payara
going
to
push
changes
back
to
glassfish
or
or
who
will
support
glassfish,
and
I
guess
the
the
answer
to
the
last
question.
It's
the
community
because
las
vegas
is
now
open
source.
A
B
B
Yeah,
so
you
can't
just
do
a
big
pr
of
pr
directly
to
classface
and
be
done
with
it.
You
would
have
to
extract
all
those
tiny
changes
everywhere,
then
merge
them
into
glass,
fish
resolve
all
the
changes
that
have
occurred
in
two
places.
That's
that's
really
difficult
to
do
it's
more
easy
for
them
to
contribute
back
the
changes
they
make
to
the
components
that
make
up
classes
like
grizzly,
hk2
and
pr
is
indeed
doing
that
so,
of
course,
not
longer
working
for
them.
I
can't
speak
for
them.