►
From YouTube: Jakarta EE Update Call July 14, 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
There
we
go:
okay,
welcome
to
the
july
14,
jakarta
e
update,
call
and
I'll
walk
you
through
a
couple
of
things
that
are
happening
in
the
community
and
also
yeah
I'll,
show
the
agenda
here
and
feel
free
to
just
stop
me
and
ask
questions
if
you
have
any
on
the
way.
A
So
I'll,
just
briefly
go
through
the
upcoming
tech
talks
we
have
in
the
pipeline
and
the
jakarta
one
live
streams,
then
I'll
dive
into
some
possible
scenarios
for
the
new
jakarta
eco
profile
and
some
pointers
to
where
to
connect
with
us
and
that
kind
of
things.
A
So,
as
you
probably
know
on
meetup
we
have
the
ducati
tech
talks,
we
run
them
on
crowdcast
and
if
you
cannot
attend
them
live
you
can
watch
them
on
the
youtube
playlist
afterwards
and
all
these
links
will
be
published
afterwards.
So
so
you
can,
you
can
click
on
them
and
all
the
tech
talks
are
published
on
the
community
calendar.
A
So
that's
where
you
find
them
in
the
pipeline
right
now,
we
have
in
august
a
couple
of
talks,
one
by
steve,
millage
on
jakarta,
concurrency
and
also
one
on
jakarta
rest
by
santiago,
and
we
also
there
potentially
could
be
one
in
late
july
as
well,
so
just
keep
an
eye
on
the
community
calendar
and
see
what's
happening
there.
A
You
can
also,
of
course,
do
a
tech
talk
yourself.
It
doesn't
have
to
be
a
jakarta
content,
it's
good
that
it's
related
to
ducati,
but
it's
any
technical
topic
that
is
in
the
swear
of
business,
that
we
are
a
technology
that
we're
working
on.
So
you
can
use
this
signup
form
and
you
it's
also
accessible
from
the
jakarta
ee
webpage.
But
you
can
just
link
in
this
in
this
slide
as
well
and
just
sign
up
for
a
tech
talk
and
we
will
schedule
it
for
you.
A
We
also
have
the
jakarta.
One
live
stream
events
and
these
are
in
different
languages
and
upcoming.
In
august
we
have
a
turkish
one
on
august
21st
and
then,
following
that
in
september
october,
we
have
a
portuguese
edition
and
a
spanish
edition,
and
all
of
these
are
working
on
creating
the
schedule.
So
the
call
for
papers
are
up,
at
least
for
the
portuguese
and
spanish.
A
I
think
the
turkish
has
closed
now,
but
if
you
have
a
talk
or
want
to
talk
in
portuguese
or
spanish,
do
submit
their
call
for
papers
and
you
can
get
accepted
to
this
conference
and
it's
usually
pretty
well
attended
and-
and
you
can
get
it
in
in
your
local
language
and
of
course
we
have
the
main
event
in
december
on
december
7th
and
the
call
for
paper.
For
this
event,
this
will
be
in
english
and
the
culture
paper
for
this
event
will
start
tomorrow.
A
So
just
sharpen
your
pencils
or
keyboards
or
whatever
you
use
to
submit
your
abstracts
and
go
in
to
the
chicago
one.org
website,
find
the
cfp
and
submit
your
talk.
A
B
The
all
the
previous
jacquard
one
live
stream
hawks
are
recorded
and
you
can
play
them
back
at
any
time
in
you
know
in
and
they're
all
in
their
native
languages,.
A
A
The
next
topic
I
was
planning
on
going
through
is
ducati
core
profile
and
thanks
very
well.
I
think
it's
kevin
coming
in
here.
A
So
I'll
walk
you
through
some
thoughts.
We
have
working
on
the
jakarta
e
core,
crowbar
and
first.
Why
are
we
doing
this?
A
And
one
of
the
reasons
is
that
if
you
look
at
this
is
a
very
suggestive
proposed
how
the
jakarta
e10
platform
could
look
like
with
the
associated
versions
and
be
aware.
Everything
here
can
change
we're
currently
discussing
whether
mvc
should
be
a
part
of
the
platform
or
not,
and
the
others
are
also
all
of
them
are
up
for
discussion.
A
But
this
is
one
scenario
of
how
jaccardi
platform
could
look
like
and,
as
you
see
there
are
lots
of
specifications
here
and
and
all
these
specifications
are
implemented
by
various
vendors
and
I've
listed
the
ducati
9.1
platform
compatible,
and
you
can
see
that
it's
the
usual
suspects
of
application
servers
here
of
glass
station
managed
fish
and
open
liberty,
piara
and
wildfly,
and
there
are
more
to
come.
I'm
sure
that
this
list
will
be
bigger
every
day
as
we
go.
A
So
so,
if
we
take
these
specifications
and
and
look
at
some
of
them
here
that
have
grayed
out
that
are
more
of
the
the
let's
call
it
the
enterprise
things
like
the
mail
messaging
and
and
batch
specification,
for
example,
and
if
we
take
these
out,
the
the
set
of
specifications
are
a
little
smaller,
and
this
is
the
jakarta
e
web
profile
and
and,
as
I
said
with
the
previous
slide,
this
is
just
a
suggestion
of
how
the
10
web
profile
could
look
like,
but
you
can
see
it,
it's
a
smaller
set
of
specs
and
if
you
look
at
the
implementations
here,
it's
more
or
less,
this
is
the
901
version.
A
It's
more
or
less
the
same
application
servers
as
we
had
with
the
platform
you
can
see.
Apache
tommy
has
come
in
here
they
implement
the
web
profile,
so
they
are
kind
of
benefiting
from
having
a
smaller
set
of
specs
to
implement.
So
you
don't
have
to
do
everything.
A
B
A
Take
the
ones
I've
grayed
out
here
that
are
more
targeted
towards
creating
web
applications
and
web
uis
a
lot
like
the
faces
and
and
servlets
and
server
pages,
and
that
kind
of
things
and
and
grade
these
out
and
take
these
away.
A
We're
left
with
a
set
of
specifications
that
are
targeted
towards
creating
headless
services
or
microservices.
If
you
like-
and
this
is
a
very
suggestive
suggestion
for
how
ducati
e10
core
profile
could
look
like
and
and
and
since
this
is
a
a
significantly
smaller
set
of
specs-
and
you
can
also
see
that
there
is
a
new
specification
on
the
bottom
here.
Called
config
I'll,
go
into
a
little
bit
more
detail
about
that
later,
as
well
as
the
cdi
light,
which
is
a
new
flavor
of
cdi.
That'll,
also
go
into
a
little
bit
more
detail.
A
But
since
we
now
have
very
shrinked
from
the
the
large
platform
to
the
web
rover
and
then
even
further
down
to
the
core
profile,
we
open
up
the
possibility
for
having
smaller
products
potentially
being
ee
compatible.
And
I've
just
listed
a
couple
of
examples
here.
That
could
be
a
potential
core
profile
compatible
like
halodon,
corkus
or
even
micronaut.
A
So
so
the
the
core
thing
about
the
core
profile
fun
intended
actually
is
targeting
smaller
runtimes
and
and
let's
look
at
how
we're
doing
that
in
by
looking
at
a
couple
of
the
specs
and
let's
first
look
at
config
and
the
the
new
spec
for
jakarta
config,
which
will
be
very
much
influenced
from
a
microprofile
config.
It
may
possibly
end
up
being
microproc
config
that
becomes
chicago
config
or,
however,
that
project
team
decides
to
solve
it.
A
They
are
discussing
the
goals
and
non-goals
for
the
specification
now,
but
what
they,
the
the
the
thing
about,
the
the
config
is
to
create
portable
configuration
from
environment
of
our
sources,
and
you
can
find
details
on
this
on
the
ducati
specifications
config,
and
this
is
how
a
config
may
function
like
if
I
inject
a
config
property
called
place
here
and
I'm
using
a
in
the
down
right
corner
like
a
property
file
where
the
the
value
of
the
property
is
property
file
world,
then
the
value
of
place
would
be
getting
this.
A
A
I
can
also
override
this
one
by
having
a
system
property,
for
example,
given
to
me
by
a
container
management
system
like
kubernetes,
and
you
can
also
possibly
if
we
go
go
down
the
road
that
microprofile
config
are
doing,
you
will
be
able
to
create
your
own
sources
that
would
be
able
to
come
in
between
these
defaults
or
even
over
item.
It's
not
even
necessarily
these
three
levels
that
will
be
of
jakarta
config,
but
that's
pretty
likely.
A
A
Slash
cdi
and
some
of
the
things
that
are
being
discussed
in
the
cdi
projects
is
to
create
a
new
extensions
api
and
modify
the
beans
xml
behavior
a
little
bit
and
some
other
things
and
and
the
purpose
for
these
changes
is
to
enable
ahead
of
time
compilation
using
technologies
like
raw
vm
to
to
to
to
create
a
compiled
to
native
images.
A
If,
if
you
want
to
do
that,
so
so,
to
remove
some
of
the
dynamic
features
of
cdi,
take
it
out
of
the
the
the
cdi
light
and
and
see
that
light
is
expected
to
be
a
subset
of
cdi
core,
which
would
be
a
subset
of
the
cdf
or
whatever
they
end
up.
Calling
these
different
flavors
of
cdi.
A
If
we
look
at
jakarta
restful
web
services,
the
goal
for
the
four
dog
version
there
is
to
potentially
use
jakarta
config
if
that's
available,
when
the
specification
is
written,
so
you
can
configure
your
rest
application
using
jakarta,
config
and
also
align
it
with
cdi
light
and
also
align
it
with
cdi
traditionally,
and
you
can
find
information
about
this.
One
under
chicago
specifications,
slash
restful,
ws
and
one
of
the
things
they
want
to
do
in
in
jakarta.
A
Rest
for,
though,
is
to
get
rid
of
their
custom
injection
mechanisms
like
if
you're
used
to
writing
restful
endpoints,
and
you
want
to
have
access
to
the
uri
info
in
order
to
build
some
uris
for
example.
Today
you
have
to
use
the
add
context
to
inject
this
property,
but
by
enabling
and
being
it
making
it
cdi
friendly,
you
will
be
able
to
use
the
add
inject
from
cdi
or
a
jakarta
inject
and
inject
the
urine
flow
directly.
A
So
the
the
json
specifications
for
processing
and
binding
are
planning
on
doing
smaller,
updates
and
doing
community
wanted
features
to
to
make
life
easier
for
a
programmer.
A
So
there
are
not
very
big
changes
going
on
there
there.
As
you
can
see,
there
are
minor
releases,
so
they
will
just
adjust
and
yeah
make
life
easier,
more
or
less.
A
There
are
also
three
kind
of
pretty
stable
specifications
there
for
dependency
injections,
interceptors
and
intentions,
and
these
are,
as
far
as
I
know,
not
any
plans
for
doing
anything
for
chicago
attempts,
so
they
will
stay
as
they
are
for
chicago.
A
Potentially
the
this
is
also
me
just
guessing
the
if
we
end
up
creating
a
a
a
jar
for
the
core
api
probably
looks
something
like
this.
A
So
beside
the
core
profile,
we're
also
considering
other
things
for
chicago
and
one
of
the
things
we're
looking
at
is
the
java
sc
versions
and
we've
actually
made
some
decisions
here
and
that
the
the
apis.
A
A
Another
thing
we're
discussing
is:
how
are
we
going
to
have
a
release
cadence?
Will
it
be
a
time-based
release?
Cadence
like
once
a
year
once
three
year?
Should
we
tie
it
to
the
javascript
lts
versions,
or
how
are
we
going
to
do
this
and
that's
something
we
are
currently
discussing
pretty
vividly
in
the
platform
project,
so
please
do
join
our
calls
there.
A
If
you're
interested,
we've
also
started
work
of
decoupling,
the
dck,
so
each
project,
each
specification
project
can
take
responsibility
for
their
own
tck
and
the
tcga
team
will
pull
it
together,
and
so
we
will
still
be
able
to
run
the
platform
and
profile
this
case.
So
that
was
the
core
profile.
Any
questions
on
core
profiles
or
comments.
B
A
So
the
the
specifications
that
core
profile
will
consist
of
is
mapping
pretty
much
directly
to
these
specifications
from
jakarta
e.
That
microprofile
depend
on
so
so
it
will
be
a
baseline
to
to
to
have
microprofile
apis
built
on
top
of
so
so
that
is
one
of
the
ideas
behind
it.
Yes,
but
it's
not
any
competing
profile
or
any
anything
that
is
replacing
anything.
It
will
provide
the
core
jakarta
ee
apis.
A
That
microprofile
can
depend
on,
and
this
opens
up
for
having
a
a
test
suite
that
tests
the
core
profile,
then
the
microprofile
can
actually
adopt
this
test
suite
and
if
they
want
to,
they
can
say
that
in
order
to
be
microprofile
compatible
applications,
you
will
have
to
pass
this
test
to
it
if
they
want
to.
They
can
also
say
that
hey,
we
want
to
be
jakarta,
ee,
core
compatible
as
well
and
and
and
pass
the
core
test
rate
there.
So
that
is
it.
It's
kind
of.
A
It
aligns
very
well
with
the
the
the
how
the
world
looks
looks
to
today.
This
is.
B
I
have
a
question
because
if
I
develop
on
micro
profile,
I
can't
migrate
to
core
profile
or
if
I
develop
project
on
core
profile,
I
can
move
it
or
my
on
micro
profile.
Well,.
A
A
A
B
B
A
So
I'll
I
have
some
a
couple
of
closing,
slides
and
since
you're
all
here
you
all
know
this,
but
since
we've
been
recorded
I'll,
just
reiterate
it.
So
why
should
you
get
involved
in
open
source?
And
why
should
you
get
involved
in
jakarta
e
in
particular,
and,
first
of
all,
it's
to
gain
a
better
understanding
of
the
technology
if
you're
a
contractor
or
or
a
consultant
working
with
jakarta
technology?
What
better
way
of
selling
your
competence
to
a
potential
customer
is
to
say
that
hey,
I'm
actually
developing
the
technologies
you're
using.
A
So
it's
a
selling
point:
it's
you
can
work
with
and
learn
from
the
industry
leaders
the
people
that
are
creating
the
technologies.
You
can
work
with
them
and
learn
from
them
and
you
can
build
your
reputation
in
a
community.
You
can
build
a
name
for
yourself
by
by
being
a
committer
on
one
of
these
projects,
showing
that
hey,
I'm
here
so
and
also
of
course,
you
can
impact
the
course
of
the
technology.
So
if
you
want
something
moving
in
in
a
certain
direction,
put
your
efforts
in
there
and
you
can
make
it
move.
A
So
advance
your
career,
that's
why
you
should
getting
involved
in
open
source
and
it's
pretty
easy
to
contribute
to
jaccardi.
The
only
thing
you
need
to
do
is
to
sign
the
eclipse,
configura
agreement,
and
that's
all
you
need
to
do.
It
doesn't
cost
you
anything
and
that's
the
main
path
of
getting
involved.
A
The
chicago
developer
survey
closed
a
month
ago
or
so,
and
the
marketing
team
is
working
as
fast
as
they
can
to
provide
a
report
coming
out
of
this
survey.
So
this
will
be
coming
up
soon.
A
You
can
connect
with
us
in
multiple
ways
through
the
mailing
lists.
Look
at
the
upcoming
events
and
community
news
in
the
community
calendar.
I
do
communicate
through
github
issues
and
pull
requests,
and
also
we
have
a
slack
workspace.
You
can
join
we're
blogging
a
lot
here
and
there
and
also
we're
doing
jakarta,
tech
talks
and
the
jakarta
one
live
stream
and,
of
course,
we're
on
all
social
media
so
follow
us
on
twitter
or
facebook
or
what
your
favorite
social
media
platform.