►
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: Hendrik Ebbers, Falk Sippach, Jan Westerkamp
07:45-08:00 GMT-04
A
A
A
Now
we
went
to
the
Jakarta
EE
website
and
the
list
that
we
just
saw
of
the
specifications
that
are
there
like
said
you
can
simply
look
at
them
here
via
specifications
prospe
specifications,
and
then
you
will
find
the
specifications
for
yourself
Information,
for
example,
I
just
opened
something
at
the
end.
You
end
up
with
a
really
long
specification,,
for
example,
with
bee
validation,,
describing
how
the
whole
thing
is
useful.
A
The
other
was
bienenvalidation
to
look
at
where
all
the
things
are
and
how
all
the
things
are
separated.
I
think
you
can
tell
a
lot
about
that.
Let's
just
start
with
the
validation,
because
that's
the
way
it
is,,
we
have
three
repositories
and
Although.
We
have
the
three
things:
API
Spec
and
TCK
here
separately
in
three
repositories,.
B
Yes,,
maybe
it
should
be
mentioned
that
it
is
not
quite
as
easy
as
it
should
be.
Actually,
during
the
preparation,,
we
noticed
again
how
to
get
to
the
gitreportitoris
Grid
repositoris
are
spread
out
a
bit,
so
the
specs
use
different
ones,
Some
structures
of
the
repositories,,
sometimes
as
just
mentioned,,
the
three
repositories
for
the
different
parts,,
the
API,.
B
B
Is
stored
in
an
extra
repositor,
but
normally
it
should
also
be
from
the
namespace
and
from
the
self-understanding
that
the
implementation
tion
is
always
in
a
separate
namespace,
but
sometimes
one
finds
such
artifacts
that
the
structure
is
not
completely
adhered
to,.
For
example,
the
API
artifact
nor
unit
tests
should
actually
not
be
because
the
API
should
only
be
an
interface
without
implementation
details
and
therefore
it
does
not
need
any
tests,.
But
if
you
take
a
closer
look,,
you
will
find
quite
a
few
things
that
have
the
greatest
network-historical
reasons,.
A
About
it,,
we
will
also
see
when
Micro
Profile
is
a
bit
tidier,
yes,.
It
is
uniformly
there,.
You
just
have.
It
said:
okay,
we're
starting
again
now
we're
starting
from
the
clean
base
and
that's
the
way
it
is
here,.
That's
why
I
also
looked
out
for
bean
validation,
because
you
really
have
this
separation
into
three
repositories.
A
That's
historical,!
That's
why
the
bees
are
one
of
the
few
specs
under
Java
EE,
those
weren't
oracle
worked,
but
rather
redhead,,
which
has
led
to
the
fact
that
the
TC,
for
example,
has
always
been
open
with
the
Origin
things,,
the
things
were
only
closed
source
and
there
it
was
simply
always
the
case
that
redhead
made
three
cleanly
separate
repositories
for
the
things
and
with
other
things
where
the
whole
thing
was
approached
completely
differently,
very.
B
Exemplary,
by
the
way,,
so
it
was
really
a
model
for
the
whole
of
Jakarta,
ie,
then
later,,
which
they
also
did
very
early
on,
during
the
transition
to
Jakarta,,
to
write
the
complete
spect
document
in
aski
Dock,
with
the
appropriate
references
into
the
API
and
into
the
TC
to
ensure,,
so
to
speak,
that
for
each
and
every
sentence
in
the
bacon
and
the
technical
requirements
from
it
also
exist
in
the
test,
and
that
you
can
jump
back
and
forth.
There,.
A
Those
were
really
advantages,
and
so
I
was
in
bees,,
for
example,
with
Edition
at
the
time,
and
you
could
just
access
them,
everyone
could
there
s
see
that
was
quite
pleasant.
I
am
wondering
today
how
the
other
specs
actually
did
it
in
the
early
days
of
Java
EE,
when
other
companies
were
also
involved,
I
find
it
relatively
difficult.
So
the
answer
is.
B
Relatively
simple,
so
most
don't
have
it
That's
why
tests
were
created
in
the
API
artifact,
of
course,,
because
you
could
actually
do
it
as
a
normal
developer,
without
selling
your
soul
to
a
contract,
which
isn't
the
optimal
solution
and
wasn't
conducive
either,.
So
if
something
like
that
is
close
source,
then
then
there
is
also
a
tendency
to
mold
and
legacy
issues,
often
pile
up,.
So
it
was
also
a
realization
when
it
became
open
source,.
B
So
does
anyone
of
you
still
know
a
script
that
is
still
the
core
framework
for
the
TCS
platform,,
which
is
a
bit
shocking,
and
so,
if
you've
ever
had
anything
to
do
with
it
and
had
to
wait,,
that's
no
fun
either,,
that's
about
to
happen.
Actually,
cleaned
up,,
but
that's
still
there.
There
is
still
a
real
technical
debt
in
one
or
the
other
purpose
that
had
to
be
cleaned,
up.,
That's
much
better
in
terms
of
quality
from
the
outset,
with
bien
validation
and
with
the
open
source
idea,.
B
A
Maybe
we'll
just
take
a
quick
look:
We
don't
have
much
time
anymore,,
so
bee
validation,
as
I
said,
is
divided
into
3d
positoris.
Here.
We
see
the
validation
repository,,
then
the
spec
repository
and
then
the
TC
repository
and
the
validation
repository,,
that's
the
API,.
So
that's!
Actually
the
Vegetation
API
repository
where
we
really
find
the
notations
and
interfaces
that
are
used
for
Java
was
vegetation
here
when
we
go
in,
so
there.
That
is
also
what
is
built
from
it,
yes,,
the
artifact
of
which
you
are
dependent,.
A
So
you
pack
that,
as
provided
or
whatever
as
Maven
dependency,
for
example,
the
spec,
you
just
said:
that's
the
end
effect
ekt.
You
can
find
quite
a
lot
of
asky
dog
now
I
have
to
think
again
for
myself
how
it
was
here
they
are
in
there
exactly
and
from
this
aski
dock.
The
readable
specification
is
really
defined
at
the
end,
which
I
have
just
shown.
That
is
this
document.
A
This
morning
we
had
the
CDI
example
where
there
were
problems
in
the
quarkkus
area,
because
quarkkus
did
not
have
the
complete
TCK
from
CDI
could
go
through
because
stuff
only
with
refl
ection
and
went
through
the
CDI
Guide,,
which
is
now
possible,
because
now
we
also
have
a
CDI,,
which
a
quark
course
can
then
also
go
through
completely
without
you
perhaps
being
needed,.
For
example,
we
are
now
a
horny
one,
a
bit
over
the
time,
maybe
completely.
In
short,
we
wanted
to
have
a
look
at
the
specs
at
Micro
Profile.
B
There
you
can
find
them
and
then
the
grid
with
one
click
at
Jakarta
e.
You
only
get
to
Eclipse
time.
So
there
is
one
for
each
back.
There
is
actually
their
own
website,
but
from
there
you
don't
get
directly
to
the
grid
repository,.
Strangely
enough,
we
definitely
have
to
improve
that,,
but
you
get
to
the
Eclipse
project
page
and
from
the
gypsum
project
page
you
get
to
the
grid
exactly
and.
A
Here
you
can
see
the
eggs
and
where
you
put
them
it
looks
really
nice,
it's
just
a
small
thing,
but
you
can
actually
see
it
perfectly.
That's
the
micro-pro
fi
health,
because
here,,
in
contrast
to
what
we
just
saw,,
you
can
see
that
we
simply
have
API,
Spec
and
TCK
all
three
components
in
one
repository
and
in
the
end
we
just
clean
different
artefacts
out
of
the
API
clean
out
what
we
depend
on
a
PDF
or
an
HTML
page
tumbles
out
of
the
bacon,,
I.e.
A
the
specification
in
Wiesbacher
form,
and
he
does
n’t
actually
get
anything
out
of
the
pcape
cleaning,
but
a
test
result
whether
something
is
really
important
or
not
exactly
yes,
and
we’re
both
at
that
point
Jakarta,
as
well
as
with
micropor
fight
that
the
TCS
are
completely
open
with
other
things
with
Java.
We
are,
unfortunately,
not
that
far
there,
but
with
adoptium
and
aquavit.
There
are
also
first
approaches
that
go
in
the
direction.