►
Description
Watch the Industry Keynote with David Blevins from Tomitribe, Ian Robinson from IBM, Will Lyons from Oracle and Steve Millidge from Payara
///GET SOCIAL!
Subscribe: https://www.youtube.com/user/EclipseFdn
Follow us on Twitter: https://twitter.com/JakartaEE
Follow the conference: https://twitter.com/JakartaOneConf
Like us on Facebook: https://www.facebook.com/JakartaEE/
Become a member of our Jakarta Tech Talks Meetup: https://www.meetup.com/jakartatechtal...
Join us on LinkedIn: https://www.linkedin.com/groups/13597...
Tag us: #JakartaEE #JakartaOneLivestream
A
B
So
hi
I'm,
David,
Blevins,
CEO
of
Tommy,
tribe
and
just
longtime
contributor
to
all
things.
Apache
did
my
first
open
source
project
that
implemented
EJB
in
1999.
So,
needless
to
say,
this
day
has
been
pretty
amazing
to
see
Jakarta
ee8
released.
So
you
know
today
is
a
very
very
big
day,
but
I
kind
of
wanted
to
take
us
back
and
just
kind
of
remind
us
of
how
far
we've
come
and
and
just
to
compare
where,
where
that
means
we
can
go.
So
if
we
look
back
at
2004
that
was
the
day.
B
This
is
a
big
day
urine
Apache
Software
Foundation.
We
got
a
10-year
license
to
the
Java
EE
TCK,
so
this
hadn't
happened
before
it
was
actually
three
of
us
who
got
the
ability
to
be
licensees
as
open-source
projects
it
was
Apache.
It
was
the
and
objects
web
and
also
JBoss
got
a
TCK
elbow.
They
had
to
pay
for
it,
but
that
was
kind
of
an
the
first
beginning
of
you
know
really
truly
certified
open-source
and
in
that
10
years
it
seemed
to
have.
You
know
be
that
the
calling
had
just
brought
all
the.
B
I,
don't
know
what
the
deal
is,
but
I
seem
to
get
like
two
minutes
and
then
it's
and
then
it
cuts
me
so
I
will
attempt
to
continue
where
it's
going.
I,
don't
know
what
the
last
thing
like
you
heard,
but
basically
you
know,
as
of
2004,
with
Apache
having
the
license
to
the
Java
EE
TCK.
B
It
just
brought
a
ton
of
projects
into
Apache
and
we
kind
of
had
a
little
Renaissance,
so
open
JPA
was
frat
prep,
for
example,
donated
by
be
a
derby
IBM,
and
we
just
had
lots
and
lots
of
different
things
that
were
started.
Geronimo
was
a
project
that
I
was
a
you
know,
co-founder
of
and
of
course,
Tommy
towards
the
end
of
that
time,
and
in
the
ten
years
that
Apache
was
a
Java
EE
licensee,
which
is
2004
2013.
We
shipped
three
versions
of
Java
EE
from
one
four
to
five
to
six,
both
Geronimo
and
Tommy.
B
We
across
the
patch
he
implemented
more
than
30
specifications.
We
released
in
that
timeframe
about
a
hundred
and
eighty
to
spec
jars.
This
is
across
twelve
projects
and
an
aggregate
we
did
about
five
hundred
and
forty-one
releases.
That
implemented
Java
EE
technology,
and
it
was
a
fifteen
thousand
hours
of
testing
now
that
actually,
that
last
bullet
is
completely
garbage
because
I
don't
really
know
what
it
was.
That's
just
the
time
that
we
spent
certifying
Tommy
in
the
year
before
it
was
released.
B
So
that
was
just
on
my
personal
credit
card,
they're
too
easy
to
so,
unfortunately,
in
2013,
our
10-year
license
expired
and
Apache
was
unwilling
to
re-sign.
Oracle
would
have
absolutely
given
Apache
another
license
to
the
TCK,
but
Apache
had
some
some
reservations
because
of
some
bad
history
and
decided
not
to
renew,
and
so
the
net
result
was,
is
that
we
ended
up
spending
the
last
six
years
without
a
TCK.
B
So
none
of
these
projects
that
I
mentioned
that
Apache
had
a
TCK
ting
the
ability
to
go
forward,
and
it
wasn't
through
lack
of
trying
so
I
know.
Oracle
tried
very
very
hard
for
two
years
to
come
to
some
sort
of
terms
that
Apache
would
accept,
and
eventually,
after
two
years
of
us
trying,
we,
you
know
we
just
sort
of
gave
up,
and
then
that
brings
us
to
today,
which
is
basically
this
big
long
gap
where
Apache
has
been
without
coverage
of
the
TCK
is
over
officially
as
of
this
very
day.
B
So
today,
with
all
of
the
Jakarta
te8
releases
and
truly
open
sores
tcks
Apache
can
basically
pick
up
where
it
left
off
in
2013,
and
this
is
amazing
news,
and
so
you
know
this
open
source,
TCK
stuff.
It
is
a
big
deal.
People
talk
about
it
and
I
know
you
may
not
see
it
and
feel
it
as
consumers,
but
it
is
the
thing
that
drives
the
ecosystem
and
truly
for
the
first
time
in
this
entire
time.
B
You
know
Apaches,
Java,
EE
and
Jakarta
efforts
are
whole
again,
and
so
you
know
just
a
very
big
thank
you
to
Oracle
for
bringing
us
this
far.
A
very
big
THANK
YOU
to
the
working
group
for
getting
us
into
this
shape,
we're
actually
in
a
better
shape
than
we
were
in
the
previous
several
years.
So
in
the
past,
when
we
were
doing
all
this
testing
and
releasing
all
these
541
projects,
the
saw
the
hardware
and
the
continuous
integration
system
that
we
had
used
was
completely
private.
We
couldn't
share
the
TCK
with
anybody.
B
Now
we
can
do
that
all
openly
and
I.
Ask
you
what
kind
of
open
source
project
does
all
their
building
and
private?
Are
they
truly
open?
The
answer
is
kind
of
not
really.
We
had
to
have
private
issue
trackers.
If
there
was
a
problem
where
a
TCK
test
failed
and
we'd
learned
to
file
an
issue
about
it,
we
couldn't
put
those
those
details
out
in
public,
and
now
we
can
actually
do
all
of
that
work
out
in
public
in
front
of
everybody,
and
also
the
roadmap
was
completely
a
secret.
You
know
people
said
hey.
B
B
Imagine
what
can
be
accomplished
when
everything
is
completely
open.
We
can
finally
implement
these
things
in
front
of
everybody,
with
everybody
openly
as
a
community.
In
fact,
what
we
were
doing
before
was
largely
proprietary
software
development,
even
though
we
were
shipping
under
an
open-source
license,
and
so
we're
gonna
make
a
little
announcement
today
is
that
you
know
for
the
first
time
ever
possible
we're
basically
going
on
the
Tommy
tribe
side,
we're
gonna,
donate
TCK
testing
resources
to
the
Apache
projects
that
implement
jacquard,
EEE
so
running.
The
TCK
takes
a
very
long
time.
B
A
Okay,
so
I
think
it's
just
not
the
great
day
for
David
and
his
connections.
I
can
see
his
slide
out,
though
so
I
would
actually
suggest
we
move
on,
because
we
have
a
few
more
key
notes
to
go
to
so
at
this
point,
I
will
invite
Ian
on
the
screen
and
shared
to
share
his
screen.
Then
I
apologize
to
David
too
for
cutting
him
off,
but
we
have
to
move
on
and
we'll
make
sure
that
we
either
share
the
slide
deck
or
actually
do
a
proper
recording
and
provide
that
for
you
guys
so
Ian.
C
Well,
thank
you
very
much
and
I.
Think
David
was
having
quite
a
good
day.
Actually
I
thought
I
thought
his
message
came
through
loud
and
clear
until
we
lost
him
and
it's
one
of
the
great
things
about
working
in
the
Jakarta
steering
committee
is
all
the
great
people
working
together
to
do
things
like
David
was
just
talking
about
I'm,
Ian,
Robinson
and
I
worked
for
IBM
I'm,
an
IBM
distinguished
engineer,
I'm,
the
chief
architect
of
WebSphere
and
the
WebSphere
technologies.
C
So
Java
EE
has
historically
been
very,
very
important
to
to
me
in
to
us
and
for
myself
personally,
my
history
with
Java
EE
goes
back
pretty
much
to
the
beginning.
I
was
a
spec
lead
of
a
jsr
that
only
had
to
did
in
it.
So
that
gives
you
an
idea
of
how
long
ago
that
was
Java
EE
as
a
basis
for
Jakarta
EE
is
so
important
to
IBM
as
a
business
websphere
as
a
software
business
makes
us
a
billion
dollars
of
revenue.
C
C
We
have
tens
of
thousands
running
over
a
million
applications
for
WebSphere
related
technology,
whether
that's
traditional
WebSphere
or
I,
used
to
talk
about
Liberty
as
being
our
newer
WebSphere
around
time,
but
web
spear
has
been
around
for
twenty
one
years,
Liberty's
been
around
for
four
seven
years
now,
so
it's
not
a
new
runtime
anymore,
but
it
is
a
lightweight
runtime,
a
lightweight
Java,
EE
runtime,
and
it
it
it's.
One
of
the
things
that
has
made
me
terribly
frustrated
about
Java
EE
over
the
years
is
the
historical
suggestion
that
Java
EE
is
a
monolithic
architecture.
C
It
arguably
at
some
point
in
its
history.
It
could
have
been
accused
of
being
a
monolithic
architecture,
but
for
about
the
last
10
years,
probably
since
Java
EE
6
Java
EE
has
served
the
industry
pretty
well
my
opinion
as
a
technology,
that
the
applications
platforms
that
implement
it
have
been
able
to
move
with
the
times
until
a
few
years
ago
pretty
rapidly,
and
it
provides
a
foundational
set
of
technologies
that
are
alive
and
well
and
a
heart
of
of
our
cloud
and
our
customers
clouds
today.
C
What
I
think
is
what
I
think
has
become
challenging
or
Java.
Ee
is
not
the
fact
that
it's
perceived
to
be
a
monolithic
architecture.
It's
only
as
monolithic
is
the
implementation
of
the
technology.
The
thing
that
I
found
challenging
an
IBM
customers
found
challenging
with
Java
EE
in
recent
years
was
the
rate
and
pace
at
which
it
was
able
to
keep
up
with
the
demands
of
the
applications
that
had
historically
been
running
on
it.
C
So
you
know:
we've
been
moving
for
the
last
few
years
into
a
cloud-based
world,
putting
stuff
into
containers
running
them
in
cloud
platforms
like
kubernetes
and
Java.
Ee
wasn't
really
speaking
to
that
community
anymore.
It
wasn't
that
the
technology
wasn't
a
good
basis
for
running
applications
in
that
environment.
It's
just
that
the
platform
started
to
grind
to
a
halt.
C
He
implementers
and
that's
in
terms
of
the
sorts
of
things
that
David
and
Mike
was
speaking
about
earlier
on
how
the
specifications
are
hosted
and
made
available
how
the
tcks
are
hosted
and
made
available
how
implementers
of
the
platform
can
get
hold
of
the
technology
much
more
easily.
Like
me,
Apache
Software
Foundation
enables
us
to
have
a
far
broader
engagement
that
can
push
the
technology
further
forward
a
rate
and
pace
at
which
we
want
to
actually
consume
it.
C
Use
it,
and
so
I'm
particularly
excited
about
the
fact
that
in
IBM,
our
Liberty
technology
is
something
that
we've
been
trying
to
keep
up
to
pace
with
micro
profile.
So
every
time
there
has
been
a
micro
profile
release
Liberty
the
Open
Liberty
community
has
been
one
of
the
first
implementations
of
that
micro
profile
release.
Well,
Jakarta
ee8
was
released
today
and
we've
been
working
very
hard
behind
the
scenes,
along
with
our
colleagues
on
on
the
GlassFish
team,
and
indeed
the
wildfly
team,
and
so
on.
A
C
I
am
I'm
really
excited
about
the
fact
that,
on
the
very
very
first
day,
Jakarta
EE
8
was
released.
We've
certified
open
Liberty
to
Jakarta
EE,
so
that
an
open,
Liberty
developer
now
can
get
the
benefits
of
both
Jakarta
EEA
and/or,
a
micro
profile.
I
think
these
two
things
together
show
are
going
to
show
that
the
way
forward
for
the
Java
platform
and
my
expectation
in
terms
of
what's
coming
next
in
future
releases
of
Jakarta
EE
will
be
heavily
influenced
by
the
work
that
we've
been
doing
together
at
micro
profile
on
the
way.
A
A
A
D
Okay,
it's
not
sharing
the
actual
presentation,
no
problem,
so
I'm,
just
gonna
really
talk
briefly
around
hi
Aaron,
who
we
are
so
in
our
relationship
with
Jakarta
EEE,
so
payara,
our
strategic
members
of
Jakarta
EE
working
group,
which
means
that
we've
been
working
since
beginning
on
getting
Jakarta
ee8
out
the
door.
For
today.
D
The
working
group
is
where
a
lot
of
the
business
side
of
the
work
I
was
on
or
the
specification
creation,
certification
and
we've
been
strategic
members
since
the
beginning
and
since
the
migration
of
Java
EE
over
to
Jakarta
EE,
so
we're
also
PMC
members
of
evj.
So
e4j
is
the
section
of
the
church
foundation
where
the
actual
technical
work
is
done.
That's
where
all
the
projects
it
and
we
are
also
PMT
members
of
that,
and
one
of
the
key
things
is
that
pi
are
actually
a
new
vendor
in
this
ecosystem.
D
So
it
may
not
seem
like
that
that
site
seemed
like
it
for
many
many
people,
but
we've
only
been
around
as
a
company
since
2016,
so
we're
only
just
into
our
third
year
they're
our
fourth
year
now,
and
what
Carter
Eid
enables
us
to
do
as
a
new
vendor.
Is
they
do
the
opening
up
of
all
the
tcks
the
source-code
specifications
and
the
projects
is
that
as
an
as
a
new
vendor,
we
can
get
access
to
those
open
source,
tcks
and
certify
our
products
against
those?
D
So
as
part
of
being
a
strategic
member,
we've
been
heavily
involved
and
flat
out
and
getting
the
binaries
out
and
tested
and
into
GlassFish,
so
our
project
team
as
being
moving
the
migrating
all
the
projects
over
working
in
the
number
of
projects,
including
JSF
and
concurrency,
to
actually
build
out
and
certify
those
and
now
that's
all
out.
Then
all
that
works
done.
What
we
need
to
do
now
is
move
forward
into
driving
Jakarta
ee.
D
D
D
Created
payara
was
to
take
the
concept
of
what
was
a
java
application
server
and
move
that
concept
and
to
take
developers
onto
new
platforms
like
cloud
like
container
platforms,
IOT
platforms.
So
when
we
created
payara,
our
vision
was
really
to
to
reshape
what
people's
concept
of
an
application
server
is
and
enable
us
to
leverage
a
managed
runtime,
provide
monitoring.
D
Monitoring
and
scalability
and
thread
management
and
all
the
things
that
our
managed
runtime
can
do
but
try
and
take
that
and
make
it
work
on
lots
of
different
architectures.
So
basically
we
take
the
architect
mate.
We
take
the
product
and
make
it
work
best
for
different
architectures
and
you,
as
developers,
can
concentrate
just
on
the
Jakarta
EE
api's.
D
So
we
have
two
products
that
we
that
we
deliver.
One
is
PI
R
server,
which
is
a
standard
application
server
in
its
model.
It
has
a
domain,
it
has
managed
service,
and
now
that
was
that
was
derived
from
the
upstream
Eclipse
GlassFish,
and
our
intention
is
to
certify
payara
593,
which
is
one
that
was
just
released
in
August
as
a
compatible
implementation.
D
So
what
we're
trying
to
do
is
make
sure
that
is
repeatable,
because
we
release
our
product
every
month
to
customers
and
every
three
months
in
the
community.
So
we
want
to
make
sure
every
product
going
forward
is
fat?
Is
Jakarta
compatible,
so
we're
building
that
release
infrastructure
I
on
ec2
at
the
moment,
so
our
first
attention
is
to
release
pi
or
a
server
first
PI.
Our
micro
is
a
container
platform
and
we're
looking
to
release
that
after
PI
or
a
server
when
we
account
the
best
way
to
integrate
that
with
a
TCK.
D
The
TCK
has
quite
a
traditional
test
model
deploying
applications.
So
we
need
to
adapt
that
to
fire
micro.
So
we
see
that
following
from
PI
or
a
server
that
should
happen
very
soon
and
after
that
we
are
basically
gonna
release.
Every
version
has
been
a
compatible
implementation
and
then
team
will
be
working
heavily
within
the
chakashi
working
group
to
move
forward
to
Jakarta,
e9
and
Jakarta
e10
and
beyond,
so
that
that's
that's
all
I
have
to
say
today.
A
E
E
A
E
E
Some
of
this
has
already
been
discussed,
but
I'll
reiterate
that
Jakarta
e8
is
fully
compatible
with
Java
EE
8.
So
it's
using
the
same
API
is
using
the
Java
X
namespace.
The
tcks,
which
are
used
to
certify
compatible
implementations,
are
fully
compatible
with
the
Java
EE
ATC
case.
We've
got
a
new
granting
process
for.
E
Certifying
compatible
limitations,
and
all
of
this
is
a
result
of
a
cross-community
process.
That's
been
created
at
the
Eclipse
Foundation
Eclipse
GlassFish,
which
is
based
on
formal
oracle.
Glassfish
sources
which
have
been
donated
or
contributed
to
the
Eclipse
Foundation
is
one
of
the
compatible
implementations
and
Ian.
Has
artists
open
to
open
Liberty,
which
is
also
certified
as
compatible
and
all
the
vendors
listed
have
all
announced
their
intent
to
support
Jakarta
e8
with
compatible
implementations
going
forward.
So
we've
got
a
very
healthy
vendor
community
and
a
baseline
for
enterprise
Java
to
evolve
in
the
future.
E
I
I
just
want
to
say
a
big
thank
you
to
everybody.
It's
it's
been
a
long
road
and
I
think
that
needs
to
be
acknowledged.
We
we
Oracle
and
our
partners,
announced
our
intent
to
move
gobby
e
to
the
Eclipse
Foundation
two
years
ago.
Since
that
time
we've
created
the
IDI
forge
a
project
which
hosts
much
of
the
sources
that
Oracle
has
contributed.
E
E
Oracle
has
invested
a
lot
in
contributing
glassware
sources.
The
sources
of
the
TC
canes,
which
David
was
discussing
earlier
and
the
actual
specification
documents
themselves
were
so
the
Java
EE
8
specification
documents
which
are
now
being
reused
in
Jakarta
and
together
with
our
partners
and
in
this
undertaking,
we've
defined
a
specification
process
and
now,
finally,
we've
delivered
the
first
Jakarta
Yi
release.
E
It's
really
been
incredible
to
see
how,
once
we
got
all
the
foundation
created,
how
we've
been
able
to
deliver
this
place.
So
I
really
appreciate
the
work
that
everyone
is
contributing
to
this.
This
is
a
slide
that
I've
been
presenting
for
quite
some
time
now
that
it
has
been
our
intent
to
deliver
Java,
EE
technology
and
with
sponsorship
from
the
community
to
create
a
new
brand
and
a
new
process
which
is
flexible
and
is
open
and
it's
compatible
and
we've
done
all
of
us.
E
One
thing
I
want
to
emphasize
it's:
it's
been
a
long
road
delivering
this
release.
I
do
not
expect,
and
you
should
not
expect
that
this
will
be
a
two-year
process
going
forward.
Much
of
the
time
that's
been
invested
over
the
past
24
months
has
been
spent
in
technology
transfer,
both
contributing
technology
and
working
out,
the
licensing
terms,
etc.
Associated
with
that,
once
all
of
that
has
been
put
in
place,
it's
really
taken
the
community
only
a
few
months
to
actually
deliver
the
new
Jakarta
y8
specification.
E
So
I
think
there's
been
a
lot
of
upfront
investment
in
this
process
and
the
jacquard
e-version
crank.
That
should
be
much
easier
to
turn
going
forward.
So
I
hope
you
will
see
that
and
I
hope
you
will
continue
to
be
active
participants
and
we
look
forward
to
your
contributions
to
the
process.
Just
a
word
about
oracle
in
jakarta,
yay
and
we
are
in
our
quiet
period
now
so
forgive
the
standard,
Oracle's
safe
harbor
statement.
E
Oracle
remains
an
active
member
of
the
working
group
and
is
playing
the
lead
on
several
project
teams.
We
leverage
Jakarta
technology
today
and
Haledon,
which
provides
an
implementation
of
micro
profile
I'm,
expecting
a
new
release
of
Haledon
soon.
We
also
intend
to
support
the
car
DEA
in
a
new
version
of
WebLogic
server,
and
we
expect
to
have
more
news
on
that
very
soon.
E
We're
actively
investing
and
supporting
both
of
these
technologies
and
investing
in
the
underlying
container
and
kubernetes
technologies
themselves.
We're
seeing
a
tremendous
amount
of
interest
in
five
native
java
running
java
implementations
in
standard
cloud,
neutral
infrastructure-
and
this
is
something
we're
very
much
interested
in
if
we're
going
to
continue
to
investment
and
there's
a
lot
of
information
on
this
topic
coming
up
at
Oracle
code,
one
an
open
world
next
week
we're
going
to
be
talking
about
hello,
Don
about
WebLogic
server,
about
chukar
de
yi
and
containers
and
kubernetes.
E
So
this
is
a
significant
investment
for
us
going
forward.
So
what's
next
of
we
have
a
process
in
place
to
support
evolving
the
technology.
You've
got
the
technical
infrastructure,
we
have
people,
we
have
a
specification
process
and
you
can
participate
in
this
there's
some
key
issues
that
we
need
to
address
and
really
it's
you,
members
of
the
community.
E
So
example,
issues
that
we
need
to
look
at
are
we
need
to
move
for
new
functionality
that
gets
added
to
Jakarta?
We
need
to
move
from
the
Java
X
namespace
of
it's
part
of
namespace.
There's
active
discussion
within
the
community
about
whether
to
do
this,
all
at
once,
which
has
been
talked
about
as
the
big
bang
approach
versus
incremental
approaches.
E
So
that's
something
we
look
forward
to
hearing
your
input
on.
There's
been
a
great
deal
of
discussion
about
the
profiles,
whether
we
need
more
profiles,
in
addition
to
full
platform,
and
what
profile
do
we
need
profile,
which
doesn't
include
more
some
of
the
legacy,
technologies
or
technologies
which
do
them
well
not
evolve
in
the
future?
E
Do
we
need
a
profile
which
is
aligned
with
both
micro
profile
and
how
do
we
align
those
two
efforts
and
certainly
within
each
API,
we
need
to
determine
how
the
individual
API
is,
that
comprised
to
Carnegie
will
need
to
evolve
and
just
generally
there's
a
whole
host
of
issues
around
providing
cloud
native
Java
how
we
evolved
in
technology
from
microcircuit
aggression
with
proven
Eddie's
and
other
technologies
that
are
being
used
to
build
microservices
applications.
So
these
are
all
right
topics
or
debate.
E
There's
all
the
resources
provided
on
this
page
resources.
You
can
access
to
learn
more
to
become
committer,
become
a
member
of
the
tea
party
community,
so
I
believe
you're
going
to
be
sharing
these
slides
in
some
form,
Tonya
or
I
hope
you
will
be,
and
hopefully
these
links
will
be
useful
resources
to.
Thank
you
all
for
joining,
and
we
look
forward
to
your
participation.
E
A
A
And
we
will
give
it
here
a
few
minutes
to
Kenji
to
to
Dalian.
So
in
with
me
just
a
little
bit,
everyone
and
I'll
try
to
invite
Kenji
on
the
screen.
He
did
appear
at
some
brief
point,
but
it
seems
that
internet
connection
of
his
face
and
is
a
little
bit
problematic
and
we'll
work
on
that
for
particularly
for
the
later
or
the
the
steering
committee
panel
and
making
sure
that
we
get
a
little
bit
better
connection.
If
don't
have.
A
A
So
Kenji
I
will
connect
you
connect
with
you
offline
to
figure
out
the
connection
issues
with
the
regards
connection
issues,
so
we
can
have
a
better
connectivity
for
our
steering
committee
panel
session,
but
for
everyone
else,
thank
you
so
much
and
we
will
see
you
in
our
next
session.
I
want
the
broadcast
at
this
point.
Thank
you.
Bye.