►
From YouTube: Jakarta EE Community Acceptance (JCAT) Testing Initiative | Jakarta Tech Talks | July 28, 2021
Description
Jakarta EE Ambassadors are announcing the start of the Jakarta EE Community Acceptance (JCAT) Testing initiative. The purpose of this initiative is to test Jakarta EE 9/9.1 implementations testing using your code and/or applications. Although Jakarta EE is extensively tested by the TCK, container specific tests, and QA, the purpose of JCAT is for developers to test the implementations. This presentation will go over this initiative and how to test your apps and code on Jakarta EE 9/9.1.
A
Hello,
everyone
and
welcome
to
another
jakarta
tech
talk
joining
us
today.
We
have
brian
cuprick
to
discuss
the
jakarta
ee
community
acceptance
testing
initiative
ryan
is
a
cpg
and
retail
formulation,
r
d
development,
senior
manager
at
the
salt
systems,
co-author
of
ejv
in
action
second
edition
from
manning
and
the
netbeans
certification
guide
from
mcgrawling
hill.
If
you
guys
have
any
questions
for
ryan
as
we
move
through,
the
presentation
today
feel
free
to
ask
it
in
the
chat
or
using
the
ask
a
questions
tab
at
the
bottom
without
any
further
delay
ryan
over
to
you.
B
Thank
you
very
much
I'd
like
to
welcome
everyone
today
to
jacardi
e
community
accepting
testing
initiative.
This
is
a
new
initiative
that
we
are
starting
today
and
I'll.
Be
briefly
going
over
that
a
little
background
on
me.
I'm
also
the
president
of
the
jakarta
e
ambassadors,
the
jihadi
ambassadors
we
were
founded
back
in
2016
five
years
ago
now,
with
the
goal
of
helping
to
push
job,
ee
and
now
jacardi
forward.
B
B
So
we
organize
talks,
prepare
material
and
try
to
drive
a
gauge
and
help
developers
engage
in
the
process.
Jakarta
dee
is
an
enterprise
standard
that
is
that's
been
around
for
over
20
years
right
now
and
is
the
foundation
of
many
careers
in
the
java
ecosystem.
So,
there's
probably
not
a
java
developer
out
there.
That
does
not
use
a
jaccardi
ee
java
ee
api
in
some
form
to
get
their
job
done.
B
You
know
guide
them
for
where
they,
you
know
where
they
can
contribute,
show
them
how
they
can
participate
in
the
process,
because
it
is,
you
know,
unlike
other
stan,
unlike
other
technologies
out
there,
it
is
driven
as
it
has
a
driving,
diverse
and
community
behind
it,
driving
it
forward.
There's
the
link
at
the
bottom
of
the
page
for
who
we
are.
You
can
see
if
you're
interested
in
joining
our
mailing
list
and
possibly
being
listed
there,
please
feel
to
fill
out
the
form
and
join
us
today
join
our
mailing
list.
B
So
we
get
announcements
for
things
that
are
going
on
in
the
java
eh
space,
as
well
as
our
twitter
account
when
we
tweet
out
updated
jacardi
e
java
ee
news
that
developers
should
be
aware
about
so
this
went
live
last
night.
This
is
our
initiative
for
community
acceptance,
testing
which
we
are
doing
for
jakarta.
Ee,
9
9.1,
as
many
people
know
that
jakarta
e9
9.1
didn't
introduce
any
new
features.
B
It
is
the
big
bang
name,
space
change
to
the
platform
that
was
dictated
by
legal
as
a
result
of
the
the
donation
from
oracle
to
the
eclipse
foundation,
there's
a
link
to
the
blog,
so
you
can
read
more
about
it.
There
are
links
up
on
the
blog
which
I'll
have
in
the
presentation
today,
but
it'll
be
actually
easier
for
you
to
click
on,
go
to
the
blog
and
click
on
the
links
from
there
to
join
our
to
join
our
initiative
and
so
this
initiative.
B
The
objective
between
behind
this
initiative
is
to
test
test
the
specifications
standalone
test,
existing
applications
deploying
to
jakarta
ee
99.1,
go
through
the
process
of
converting
java
e,
jakarta
e
applications
to
the
name
space
and
also
testing
the
the
impact
of
burning
on
drivable
11..
So,
as
I
mentioned,
it's
a
big
bang,
so
you
know
your
code
will
be
affected
by
this
from
moving
to
ee9
9.1,
and
so
we
would
like
to
shake
things
up,
because
this
impacts
not
only
the
application
code
that
you've
written.
B
B
If
you're
you
know
using
like
a
hibernate
or
jpa
implementation
or
json
api
in
a
desktop
app
in
a
desktop
application
or
in
a
you
know,
for
example,
microprofile
application
as
well,
so
the
sign
up
you
can
sign
up
there
to.
Let
us
know
that
you're
participating,
we'll
communicate
to
people
that
sign
up
to
provide
help
and
to
solicit
feedback,
there's
also
a
google
link
for
providing
feedback.
What
have
you
discovered?
You
know
what
has
what
have
been
your
experience?
You
know
in
testing
out
jakarta
ee9.
B
So
if
you
click
on
that
link
right
there,
you
can
provide
feedback
and
we're
going
to
be
running
this
from
today
july,
28th
until
october
1st
of
this
year,
and
then
we're
going
to
summarize
the
data
and
do
some
blog
entries
and
throughout
the
process
when
you,
when
you
submit
feedback
we're
going
to.
If,
if
you
run
into
a
problem,
we're
going
to
try
to
help,
try
to
help
you
solve
that
problem
and
get
feedback
to
the
relevant
specification
or
implementation
that
you
ran
into
an
issue.
B
So
you
know
why
jk,
why
are
we
doing
this?
Well?
Tck
and
qa
can
only
cover
so
much
with
this
type
of
transition.
Libraries
much
must
be
upgraded
for
your
applications.
For
example,
if
you're
using
prime
faces
or
killian
there's
going
to
be
ramifications
to
those,
and
just
as
I
mentioned
test,
libraries
must
be
upgraded,
there's
also
no
substitute
for
real
world
applications,
so
you
know
testing
your
application
seeing
how
hard
you
know
how
hard
it
is
to
turn
to
transition
to
it
testing.
B
You
know
the
you
know
the
library
support
for
the
new
versions,
there's
always
unexpected.
With
software
there's
always
unexpected
surprises
and
that's
what
we're
trying
to
do
is
kick
the
tires
on
this.
This
initiative
is
similar
if
you're
familiar
with
the
netbeans
project.
Netbeans
has
a
netcat
project
where
they
do
acceptance
testing
of
a
new
release
of
netbeans
beforehand.
So
our
process
is
modeled
on
the
netbeans
netcat.
That's
where
we
initially
got
the
idea
from
the
test
to
do
basically
community
acceptance
testing
before
you
know
to
help
developers
move
forward.
B
B
B
Vendors
are
now
releasing.
I
have
several
slides
on
the
vendors
that
so
far
have
released,
implement
runtimes
for
it
there's
bit
different
betas
going
on
for
jakarta,
ee9
support,
so
it
is
getting
out
there.
This
is
a
major
change.
Many
of
the
containers
will
still
support
running
existing
applications
unchanged,
so
that
is,
that
is
an
option
for
them.
But
if
you
choose
to
use
any
of
the
new
features,
you
know
that
are
going
to
come
out
in
jakarta,
ee10
you're
going
to
need
to
switch
your
code
over
to
the
new
namespace.
B
B
Note
that
not
all
java
x
packages
get
changed
to
jakarta
ee,
depending
upon
what
you're
doing.
Also,
if
you're,
making
the
jump
to
9.1,
which
is
the
java
11
support,
I'm
finally
getting
off
of
java
8.,
you
might
run
into
some
additional
issues
having
to
drop.
You
know
libraries
or
some
api
there's
been
some
changes
to
java
since
eight
that
might
might
impact
your
code.
Might
not
I've
seen
more
of
an
impact
on
desktop
applications
than
ee
applications,
but
you
know
that'll
that
can
be
part
of
the
feedback.
B
There
are
two
utilities
out
there
for
doing
a
transformation,
so
there's
the
eclipse
transformer
there's.
Actually
a
previous
tech
talk
on
that
I
put
in
the
link
to
the
youtube
video,
so
you
can
find
out
more
information
on
that.
There's
also
a
good
blog
from
payer
on
it
as
well,
and
there's
also
the
tomcat
cardi
e
migration
tool,
which
is
a
shell
script,
that
you
aim
at
your
source
code
and
it
goes
through
and
changes
the
the
java
packages
over
to
the
newer
java
packages.
B
There's
for
these
utilities,
there's
maven
and
shell
integration
available.
I
haven't
checked
for
gradle
integration,
yet
I
haven't
come
across
a
greater
plugin
for
that,
but
that's
something
that
would
be
very
good
for
the
community
to
try
to
write
or
provide
so,
if
you're,
a
tool
vendor
a
developer
out
there.
That
has
the
free
time
that
would
be
a
good
good
area
to
get
involved,
so
the
ecosystem
is
large.
So
this
is
why
a
lot
of
testing
needs
to
be
done.
So
you
know
this
impacts.
B
The
name
space
change
will
impact
eclipse,
link
hibernate
if
you're
using
delta
spike.
So
it
will
have
you
know
an
impact
upon
the
libraries
that
you're
using
only
need,
and
that's
that's.
The
reason
behind
this
specification,
also
unknown
to
a
lot
of
people,
is
that
spring
applications
will
also
be
impacted
by
this
later
in
the
year
spring,
contributes
and
uses
several
java
e
technologies,
including
serverlet
jpa
and
batching,
to
a
lesser
extent
or
their
major
contributor
to
the
batching.
B
So
spring
applications
not
only
java
ee
applications
and
desktop
applications
using
ee
technologies
will
be
impacted
but
also
spring
applications.
So
this
is
going
to
have
a
large
impact
upon
the
job
that
you
could
on
the
java
ecosystem.
So
if
you
are
writing
an
application
in
tomcat,
you
need
to
take
that
into
account.
B
It
will
also
impact
micro
profile
applications
if
you're
using
micro
profile
micro
profile,
builds
upon
and
used
as
many
of
the
jakarta
ee
apis.
So
you
will.
It
will
depend
upon
that,
so
the
jakarta
e9
containers
that
are
available
today
for
testing
include
glass,
fish,
early
releases
of
pyra
as
well
as
open
liberty
and
wildfly.
B
B
9.1
containers
with
full
java
11
support
are
listed
here,
as
you
can
see,
that
includes
glass,
fish,
wildfly,
etc,
as
well
as
open
liberty
and
web
profile
as
well.
So
if
your
web
profile
you're
running
in
tomcat
or
something
that
is
also
impacted,
so
even
if
you're
just
running
your
application,
you
have
just
a
tomcat
application.
You
are
going
to
be
impacted
by
these
changes,
so
testing
ideas.
So,
if
you're
looking
at
where
to
get
started,
how
do
you
start
looking
at
jacardi
e9,
you
know.
B
Maybe
your
company
is
not
ready
yet
to
make
the
transition
or
doesn't
really
have
any
idea
what
the
impact
is
going
to
be.
We've
put
together
a
javi
I
previously
put
together
a
java,
ee
starter
example,
which
you
can
check
out
or
clone
from
github
and
run
the
conversion
utilities
on
that,
just
to
see
what
it's
going
to
be
like,
so
you'll
need
to
update
not
only
the
tooling.
B
Test
applications
convert
cargo
tracker,
so
this
is
an
excellent
example.
To
get
involved
is
to
convert
the
cargo
tracker
from
jakarta,
e9
to
nine
point
or
eight
from
from
the
current
java
eights
ee-8,
either
nine
or
nine
point
one
and
contribute
back
to
that
on
the
cargo
tracker,
but
that's
a
larger
application
that
you
can
see
the
impact
on
the
real
world
application.
B
If
your
application
that
you
work
on
a
daily
basis
is
too
large
test
applications
standalone,
you
know,
testing
out,
you
know
the
impact
of
the
apis
on
java
se,
you
know
if
you're
using
json
applications
spring
applications.
All
of
these
are
great
ways
to
get
involved.
The
first
two,
the
java
e
starter
and
the
cargo
tracker,
are
an
easy
way
to
get
your
feet
wet
with
ee9
and
test
to
see
how
you're
gonna,
you
know
to
you
know.
A
B
Some
code,
through
the
the
put
some
effort
into
actually
doing
the
transition
and
see
what's
involved,
although
it's
a
big
bang,
it's
not
you
know
it's
not
major.
There's
not
you
know
just
a
package
renaming.
It's
not
new
features
being
added
you're,
not
dealing
with
chain.
You
know
changes
as
much
as
you
are
just
you
know,
going
through
an
existing
large
code
base
and
changing
every
package
imports
for
each
file.
B
So
another
excellent
example
is
the
boilerplate
project
which
I
put
in
the
link
below.
He
has
many
good
links
for
transitioning
to
jakarta
ee,
so
I
recommend
also
checking
out
this
project.
If
you
are,
you
know
definitely
following
this
project
here
for
doing
the
transition,
and
so
you
know
why
does
why?
Are
we
doing
this?
Well?
Eighty
percent
of
java
applications
use
jakarta
e
apis
and
it
underpins
many
frameworks.
Businesses
depend
upon
heavily
upon
jakarta
ee.
B
Many
developers
have
built
the
careers
around
this,
so
you
know
making
sure
that
this
is
successful
is
really
important
for
everybody's
career
and
everybody's
job.
So
that's
why
we're
doing
that's?
Why
we're
pushing
forward
with
the
community
acceptance
testing
to
to
put
it
through
its
paces
and
get
some
real
real
world
feedback?
Obviously
this
is
a
big
bang
changes,
so
business
is
going
to
be.
You
know
not
immediately
jumping
on
it.
You
know,
so
you
know
the
next.
B
So
this
is
just
a
generic
list
of
ways
of
contributing
to
jakarta
ee,
a
mailing
list,
et
cetera
for
doing
that,
the
chicag
ambassadors.
So
if
you
follow
us
on
twitter,
we'll
be
tweeting
about
this,
you
can
check
out
our
blog
our
website.
You
can
get
more
information
on
this
initiative
and
to
join
in
in
doing.
A
B
So
this
is
really
you
know:
we're
going
to
try
to
collect
the
feedback,
we're
going
to
use
this
as
the
basis
for
presentations
going
forward
to
tell
people.
You
know
where
the
paid
points
are,
and
you
know
to
you
know.
I
think
what
we'll
discover
in
the
end
is
that
the
transition,
although
it
is
a
big
bang
and
requires
changing
source
code
files,
it's
not
a
not
a
major
breaking
change
for
many
applications
and
that's
what
we're
hoping
to
hoping
to
prove
and
make
sure
that
that
is
the
case
for
for
the
community.
B
B
B
B
So
if
we
discover
that
there's
a
real
pain
point,
we
hope
to
jump
in
there
and
you
know,
drive
development
on
either
the
specs
or
on
the
tooling
to
make
it
easy
for
developers,
and
so
you
know
really
it's
really
important
that
people
start
playing
with
tools
right
now,
so
that
when
your
company
decides
to
make
the
jump
to
jakarta
e,
that
the
tools
are
there
and
that
they
worked
correctly.
So
that's
what
we're
trying
to
do
right
now
is
get
that
stuff
straight
straight
away.
A
All
right,
so
it
looks
like
that's
it
for
questions,
so
I
just
want
to
thank
you
for
that
excellent
presentation
today.
This
is
just
a
reminder
to
everyone
in
the
audience.
If
you
have
any
final
questions,
you
can
pop
them
in
the
chat
or
using
the
ask
a
questions.
Tab
I'll,
give
you
a
few
moments
to
do
so.
A
A
So
if
you
have
something
you're
interested
in
presenting,
you
can
fill
out
the
following
link:
there
you
go
and
finally,
if
you
have
any
feedback
on
this
presentation
or
on
our
jakarta
tech
talks
in
general,
you
can
fill
out
the
following
survey
at
the
bottom.
There
will
be
a
green
button
that
pops
up,
so
you
can
just
fill
that
out
and
I
don't
see
any
other
questions.
So
I
just
like
to
thank
ryan
again
for
today
in
this
excellent
presentation
and
thank
you
to
everyone
who
attended.