►
From YouTube: Jakarta Tech Talk - Migrating from Java EE to Jakarta EE: challenges and opportunities
Description
"As many enterprise applications have been built using Java EE, migrating these applications to Jakarta EE is a key concern for developers. Jakarta EE 10 is the latest version of the enterprise Java standard, and it provides a platform for building portable, cloud-native applications.
In this talk, we will explore the challenges and opportunities of migrating from Java EE to Jakarta EE. We will begin by discussing the differences between Java EE and Jakarta EE, and how the migration process differs from previous upgrades. We will then explore the steps involved in migrating an application, such as identifying the modules that need to be updated, testing the application, and deploying it to a Jakarta EE 10 runtime.
One of the key challenges in migrating from Java EE to Jakarta EE is dealing with the removal of some of the legacy technologies that were present in earlier versions of Java EE. We will discuss strategies for dealing with this, such as using alternative technologies or refactoring the code to remove dependencies on these legacy technologies.
Throughout the talk, we will provide practical tips and best practices for migrating from Java EE to Jakarta EE, based on our own experiences and those of the broader community. By the end of the talk, developers will have a better understanding of the challenges and opportunities of migrating to Jakarta EE, and will be equipped with the knowledge and tools they need to make a successful transition."
A
Hello,
everyone
and
welcome
to
another
Jakarta
Tech
talk.
My
name
is
Serena
joining
us
today
is
buhaki
who
will
be
presenting
on
the
topic
of
migrating
from
java
ee
to
Jakarta
ee
challenges
and
opportunities.
If
you
have
any
questions
from
buhaki
as
we
move
through,
today's
presentation
feel
free
to
ask
them
in
the
chat
or
use
the
ask
a
questions
tab
without
any
further
delay.
We'll
hockey
it's
over
to
you.
B
A
B
To
those
who
are
in
the
U.S
or
around
10
a.m,
Eastern
Standard,
Time,
For
Us,
who
are
Africa
and
in
Europe
or
in
Asia,
is
either
a
good
afternoon
or
good
evening.
As
a
presenter
already
said,
my
name
is
bohake
and
I'm.
Speaking
from
the
sunny
and
warm
side
of
South,
Africa
right
now
be
sentenced
so
that
apparently,
the
economic
Hub
of
of
Africa
and
yeah,
so
without
further
Ado
I
would
like
to
talk
about
and
what
I've
learned
and
the
challenges
and
opportunities
Okay.
So.
B
Yeah,
so
basically
that's
my
topic
so
briefly,
who
I
am
I'm
a
full
stack
engineer
and
developer,
so
I've
basically
done
John,
Carter,
ee
or
Java
ee
application.
Full
stack
development
for
over
17
years
initially
started
an
IBM
and
then
now
apply
with
open
Liberty.
So
and
then,
over
the
years,
I
became
a
Jakarta.
B
B
Migration,
what
was
it
there
is
time
in
in
a
developer's
life
or
in
a
business
where
your
application
needs
to
be
migrated.
So
we
would
like
to
find
out
whether
you
are
ready
to
migrate
your
application.
So
the
reason
you
want
to
upgrade
your
application
most
corporates
are
run
on
the
license
based
approach,
so
they
have
a
license
agreement
with
or
service
level,
at
Greenleaf
with
their
suppliers
and
then
to
reach
those
agreement
service
level
agreement.
B
Certain
things
have
to
be
put
in
checks
and
balances,
especially
when
you
do
audited
every
year
by
like,
for
example,
us
with
the
Securities
Exchange.
If
you
are
public
listed
company,
the
certain
reason
might
be
needed
to
update
your
applications
so
like
authentic
technology,
also
security
vulnerabilities,
like
the
zero
day
that
we
had
the
log4j
zero
day.
I.
Remember
where
I
used
to
work
for
for
an
automated
company
in
South,
Africa
yeah
the
weekend
to
we've,
got
an
email
and
say:
listen.
B
We
have
to
all
upgrade
our
applications
upgrade
to
the
latest
log4j
or
if
you
don't
have
lost
your
JS
move
it
out
and
statistics
has
to
be
moved
and
we
literally
had
less
than
a
week
to
get
it
all
fixed,
because
the
Auditors
were
coming
to
make
sure
that
we
were
not
vulnerable
to
attacks
cost
efficiency.
Sometimes
vendors
will
probably
expire
your
previous
version,
so
you
need
to
upgrade
to
latest
version.
B
There
are
various
approaches
to
migration:
either
you
you
are
reactive,
so
so
you
so
there's
other
Proactive
or
reactive
either
you
you
know
that
you
know
what
we
need
to
it's
time
for
migration
and
update
is
around
around
the
corner,
so
there's
other
tackle
it
and
they
see
what
challenges
are
ahead
and
then
resolve
it
or
something
happened
or
like
you
got
attacked
or
whatever.
And
then
you
decide.
Okay,
fine,
there's
a
there's,
a
reason
to
migrate
and
then
you
migrate.
B
So
there
are
very
reason
also
why
circumstances
what
you
need
to
migrate
as
well
and
certain
strategies,
common
ones,
for
example,
you
need
to
rehearse
now
there's
a
big
push
to
go
to
the
cloud
so
there's
also
there's
good
challenges
and
opportunities
to
move
to
the
cloud.
So
I
know
like,
for
example,
pushing
payada
Cloud
very
extensively,
even
the
ibms,
and
so
with
Azure
and
and
AWS
as
well.
B
So
there's
a
lot
of
opportunities
to
move
to
the
class
and
to
and
Jakarta
EE
and
Eclipse
micro
profile
are
all
focusing
on
on,
for
example,
on
cloud
strategies
as
well
and
so,
which
will
also
be
due
to
life3
platforming.
So
if
you
want
to
be
Cloud
compliant,
you
might
you
and
you
have
a
Jakarta
application.
What
other
Technologies
we
can
read!
You
can
use
from
Jakarta
ee
to
make
sure
that
it's
also
Cloud
compliant,
for
example,
and
share
this
one
as
well.
B
Sometimes
you
might
need
to
decommission
your
applications
and
they'll
reboot,
newer
ones
with
the
newest
technology
or
your
application
is
good,
is
as
good
as
is,
and
you
just
need
to
move
it
to
to
the
newest
platform
without
needing
to
change
anything,
so
you
can
just
retain
it
and
just
push
it.
Okay,.
B
So
right
now
we're
on
Jakarta
E10,
there's
a
big
push
now
lately,
if
you've
been
active
on
social
media
about
future
talks
about
Jakarta
11,
which
is
coming
I,
think
in
a
few
weeks
time.
So
there's
a
big
push
of
Jakarta,
ee10
and
yeah.
So
Jakarta
is
basically
ee,
which
has
been
donated
to
the
eclipse
platform.
So
the
underlying
Technologies
are
still
the
same,
but
there
are
few
possible
changes.
Now
we
can't
use
the
Java
or
Java
X
namespace,
because
it's
still
copyrighted
by
Oracle,
so
we
use
Jakarta
for
example.
B
But
if
you,
if
you
come
from
a
Java
ee
background,
you
will
be
very
comfortable
using
kitchen,
Carter,
EE
and
Jakarta
today.
So
it's
very
visible.
The
release
cycle
is
very
accessible,
they're
very
open.
So
so
they
do
advertise
when
they're
going
to
what
we
about
the
next
few
days
and
and
which
technology
has
been
approved
or
which
technology
are
probably
going
to
be
re-looked
and
reworked
at,
but
it
is
very
visible
and
they're
quick,
also
to
adopt
to
latest
Technologies
like
Cloud
adoption,
like
you
know,
SQL,
for
example.
B
B
It's
very
open
source,
so
you
are,
if
you
want
to
contribute,
you've
got
you.
It
is
easy
for
them
to
join
the
community
and
then
also
give
contribution
as
well
and
then
also
they
quickly
also
to
adopt
to
the
latest
Java
technology
like
Java
records
and
also
with
virtual
threat
coming
in
Java
21,
there's
also
a
look
into
possibility
of
adopting
to
virtual
Trading
and
then
the
John
Carter
ee.
A
B
Java
21
is
coming
in
19th
of
September,
so
a
couple
of
weeks,
time
and
and
in
the
first
quarter
of
2024,
the
basic
is
Jakarta
11.
So
it
gives
time
for
them
to
do
both
testing
and
you
know
and
have
a
nice
General
AG
release
for
everybody
to
play
with,
and
then
I
always
get
asked
this
question,
especially
in
South
Africa
like
because
majority
of
spring
developers
and
maybe
are
using
spring
framework
and
then
they
were
like.
Why
do
you?
Why
do
you
look
at
your
Qatar?
B
Are
not
enemies
basically,
but
they
are
friends
actually.
So
if
you
look
at
this
every
day
and
you'll
see
that
certain
technology
that
is
being
used,
the
Java
Java
ee,
basically
so
in
November,
when
6.1
for
spring
comes
in
it
will
use
Jakarta,
10
certain
libraries
or
certain
Frameworks
from
Jakarta
anyway.
So
we
are
not
enemies.
We
are
actually
quite
friends
and
we
adopt
some
some
technologies
we
adopt
from
Spring
to
job
to
Jakarta
ee,
for
example,
batching.
B
So
the
batching
framework
came
from
basically
looks
identical
to
Spring
batching,
but
if
the
technology
came
from
Spring
framework
actually,
so
we
are
friends,
actually
that's
what
I'm
trying
to
say
and
to
the
Technologies
from
servlets
to
jpa,
to
JMS
even
CDI
and
annotations.
Come
Sprint
uses
it.
So
you
if
you
write,
for
example,
many
of
our
institutions
based,
for
example,
rights,
Enterprise,
free
application
with
JSF
as
a
front
end,
so
JSF
is
basically
just
Qatar
ee
web
framework
component-based
framework
for
presentation.
Basically,
so.
B
72
still
run
application
on
Java
17,
so
people
are
quickly
adopting
to
the
latest.
Jdk
very
few
are
still
on
Java
3D.
Well,
usually
it's
it's
very
difficult,
especially
here
with
a
lot
of
policies
in
place
to
to
get
quick
adoption
by
businesses,
because
what
you
do
not
fix,
what's
not
broken,
basically
close
to
50
uses
Java
ee,
which
is
which
is
quite
amazing,
the
biggest
among
Java
ee
schools,
Java
ee8.
B
The
applications
and
majority
still
run
Babel.
But
yeah
and
the
third,
the
second
biggest,
is
wildfly,
which
are
also
being
proponent
as
of
for
the
few
years
before
we
come
to
open
Liberty
and
for
cloud.
70
percent
is
still
doing
good,
but
ultimately
this
this
now
I
see
this
push
for
headed
on
focus
and
Micronaut.
B
Why
my
proponent
is
always
if
your
application
runs
on
if
you
deployed
your
application,
whether
it's
a
spring
boot
application
or
a
full-on
Jakarta
ee,
only
your
old
Java
ee
application
on
an
application
server.
You
are
basically
running
a
Jakarta
ee,
basically
because
most
of
your
Enterprise
application
server,
whether
it's
licensed
to
open
source
ee
compliant
so
yeah,
and
so
now
that
we
looked
at
it.
B
Version
of
which
is
basically
Jakarta
on
Jakarta
a
lot
of
things,
change
not
that
much,
but
I
think
I
saw
a
lot
of
things
that
were
juniorified,
that
my
code
was
that
in
JSF,
2.3
was
not
did
not
use
a
lot
of
engineering
so,
for
example,
your
renderers
and
your
and
your
converters.
Now
it's
just
a
lot
of
generics
and
a
lot
of
code
changes
have
to
be
done
over
there
as
well,
and
then
once
you
and
then
you
choose
your
your
cutout
Jakarta
ee
train
compatible
products.
B
B
B
B
So,
for
example,
the
last
one
of
my
code
was
Java,
ee6
and
I
migrated
to
the
Jakarta
platform,
Jakarta
API
to
version
10.
and
let's
keep
the
scope
provided,
because,
if
you
deploy
it
into
a
container,
the
container
has
the
full-on
implementation
of
Jakarta
Frameworks
and
specs.
So
you
don't
have
to
worry
about
how
the
theme
is
going
to
operate.
All
you
have
to
do
is
just
write
your
code
and
Bob's
your
uncle,
the
next
one,
which
usually
that's
when
you
need
a
good
ide,
a
you
rename
your
Java
X
import.
B
So
everything
that
starts
with
Java
X
that
you
imported
on
your
code
will
be
renamed
to
your
content,
dot
whatever
so,
basically
the
prefix
namespace
that
start
with
Java
X.
We
just
need
to
be
rename
to
Jakarta
and
then
the
rest
of
the
namespace
does
not
change,
which
is
which
is
very
beautiful,
because
if
you
have
your
Ides
it
like
your
IntelliJ
and
your
eclipse
and
visual
studio
code,
it
will
tell
you
I,
do
not
know.
I
could
not
find
your
Java
X
package,
but
I
see
there's
a
Jakarta
package
of
the
same
name.
B
Do
you
want
to
replace
it
and
then
you
just
replace
and
then
your
code
is
clean
as
ever
so
and
then
your
job
Java
you
it's
supposed
to
be
Jakarta
E10
forget
Java
ee.
Thank
you.
Ethan
application
containers
is
no
longer
compatible
with
Java
ee
application.
So
you
can't
take
your
Java
ee
code
so
anything
that
still
runs
with
a
Java
x,
dot
whatever
package
and
deploy
to
Jakarta
E10.
It
will
not
it
will.
It
will
not
see
it
it
will.
B
Your
deployment
will
fail
and
then,
for
those
who
still
runs
some
still
runs
your
XML
files
and
then
so
your
XML
namespaces
would
have
to
change.
So,
where
you
had
your
XML
name
phase
your
JCP,
you
need
to
change
it
to
jakarta.ee,
so
your
pre,
your
your
name,
spaces
that
was
prefixed
with
the
jcp.org,
just
change
it
to
jakarta.ee
and
they
use
namespaces
and
then
the
suffix
later
is
exactly
the
same
and
also
change
your
version
number,
for
example,
to
Joseph
I've.
B
If
you
granted
from
JSF
2.3
to
json4,
and
if
you
just
change
your
name
space
it
will,
it
will
still
not
work.
We'll
just
have
to
change
the
version
as
well.
So
as
you
change
your
yo,
so
you,
the
Xmas,
that
you
have
to
be
aware
of.
Are
your
siblings,
your
jpa,
your
CDI,
your
validations!
Your
badge
is
usually,
if
you're
writing
your
own
tag,
lips
and
Joseph
as
well.
So
those
are
the
prominent
ones
that
are
that
I'm
familiar
with.
They
still
have
XML
declarations.
A
B
If
you
still
have
your
your
Java
X
property,
the
stock
or
the
Java
s
prefix,
you
just
have
to
rename
it
to
Jakarta,
and
then
your
suffixes
are
still
the
same.
For
example,
your
CDI
service
extension,
you
had
a
Java
X,
Enterprise
inject
SPI
extension.
You
just
change
through
your
content.
You
see
that
the
suffixes
are
exactly
the
same.
It's
just
a
Java
extension
culture
has
been
changed.
B
B
You
usually
have
to
specify
your
name
spaces
for
yours,
for
in
order
to
use
the
SF
like,
for
example,
your
your
call,
your
dstl
core,
your
Facebook
score,
your
pass
through
attributes
and
whatever
so
before,
Joseph
so
JSF
2.2
before
JSF
2.2,
we
had
sun
java.sun.com
and
then
what
then
you're
naming
for
your
namespace
and
then
up
then
from
2.2.
We
went
to
xmln.jcp.org.
B
As
I
previously
said,
and
then
from
jsf2
onwards,
we
we
wait
on
js
on
jcp.org,
but
from
there
to
now
we
move
from
jcp.org
to
jsf4,
where
we
do
not
have
like
a
URL
based
namespace.
We
have
short
time
names,
for
example,
so
we
have
like
Jakarta.
So
your
first
score
is
your
carton
of
faces.com.
Your
HTML
is
to
carter.facebook.html
your
face
latencies,
so
basically
it's
got
jakarta.faces
and
then
whatever
it
is.
So
if
it's
a
composite,
it's
a
composite.
If
it's
a
function,
it's
a
function
positively
positive.
B
The
only
thing
that
hasn't
changed
is
jstl.destrco.
It
doesn't
have
a
shortened
name
yet,
but
on
jsf4
we
basically
gave
a
shorter
name
for
for
your
name
spaces,
and
basically
your
xstmr
looks
like
this
now,
so
your
your
name,
spaces
now
has
now
Dakota
faces
the
whatever,
but
all
the
tech,
libraries,
all
the
libraries.
B
B
B
Prime
faces
front
faces
from
preface
system
you
can
use,
you
can
use
to
contact
in
land
Space
by
default.
It
defaults
to
java.x,
so
you
have
to
specify
a
classifier
to
say
Jakarta,
so
that
you
can
see
that
you
know
what
you
are
trying
to
use
to
cut
your
branding
on
a
joke
after
ee
container
and
it's
going
to
use
the
Jakarta
namespace.
B
B
A
B
B
You
will
just
have
to
do
this,
which
change
the
version
to
J
to
version
3,
which
is
the
latest
version
of
jpa
on
on
Jakarta
ee10,
and
then
you'll
see
your
properties
where
it
says
now.
It's
changed
to
jakarta.persistence
Dot,
whatever
that
you
want
to
call
it,
but
it
is,
everything
is
exactly
the
same.
The
only
thing
that's
changed
is
the
version.
The
schema
location
now
says
jakarta.ee,
as
our
previously
mentioned,
and
then
all
the
properties
that
was
Java
x,
dot
has
been
replaced
to
Jakarta
dot.
B
B
B
B
Ide
to
look
for
anything
that
says,
Java,
X
and
and
and
replace
it
to
Jakarta.
You
might
have
an
issue
where
you
you
think
of
loading
of,
do
Dynamic,
loading
of
a
specific
class
or
or
was
doing
it
a
dynamic
ejection,
and
then
suddenly
you
suddenly.
You
come
into
an
error
because
you
still
have
a
Java,
X
and
package
name
on
there.
So
a
good
idea
that
can
Spot
the
Difference,
especially
like
IntelliJ
and
most
modern
Ides
right
now
support
Jakarta.
So
it
is
very
efficiently
spotting
differences.
B
You
know
like
oh,
this
I
can
replace
with
that.
Your
Imports
are
easy
to
do,
but
then
there
are
those
one
way:
some
people
really
hard
code
like
package
names
and
class
names,
especially
in
XML
in
a
in
a
configuration
file
or
a
properties
file
where
it's
not
easily
picked
up.
So
a
good
idea
where
you
literally
have
to
find
all
of
that
and
just
manually
fix
that
is,
is
very
it.
It
can
be
very.
It
can
be
something
to
do
dependency
management,
especially
for
third-party
libraries.
B
B
But
sometimes
there
are
some
things
that
are
out
of
your
control,
but
there
is
a
solution
to
it,
which
I'll
explain
later,
like
with
like
Eclipse
Transformer,
which
can
actually
go
into
your
your
your
your
your
dependencies
and
then
dynamically,
and
then
change
your
your
Imports
or
your
packages
into
Azure
cutter,
easy
compliant
and
then
certain
apis,
for
example,
get
duplicated,
for
example,
in
the
future.
I
think
each
of
these
will
be
phased
out,
so
you
just
have
to
be.
B
It
does
have
to
be
aware
which
packages
which
Frameworks
are
getting
deprecated
and
and
find
all
alternate
solutions
to
it,
and
that's
where
I
always
say
read
the
manual,
because
the
manual
always
tells
you
like
all
re
or
the
release
icon
of
each
of
the
of
the
release
of
the
of
UF
Frameworks
or
the
newer
version
of
Jakarta.
It
will
tell
you
what.
B
Isn't
difficult
at
all?
This
is
probably
changed.
The
version
of
your
of
of
your
threat
of
your
technology
that
you're,
using
like
your
jpa
or
your
JSF,
for
example,
but
it
still
has
backward
compatibility
with
previous
releases
of
Jakarta.
For
those
that
don't
know
the
name.
Spaces
from
Java
X
to
Jakarta
has
changed,
I
think
from
Jakarta
ee9,
because
Jakarta
still
adopted
the
Java
X
namespace,
but
it
was
bought
now
of
the
Eclipse
foundation,
so
from
Jakarta
ee9
we've
removed
to
Jakarta
namespaces,
and
so
it
will.
B
B
Open
rewrite
so
this
I
heard
when
I
was
overseas,
the
with
the
complexity,
for
example,
as
I
spoke
earlier,
you
know
to
do.
Refactory
companies
like
open
rewrite
actually
created
tools
to
refactor
your
your
code
to
the
latest,
for
example,
if
usage
of
Qatar
E10
it
can
help
you
with
automatically
refactoring
your
code
and
your
import.
B
B
Renaming
that
your
import
on
on
bytecode
level
or
already
pre-compiled
libraries
already
so,
but
this
this
is
also
a
very
good
tool.
For
example,
if
you
have
your
existing
code
base
that
you
wanna
do,
do
you
want
to
make
it
quickly
compliant
to
related
release
of
Jakarta
E10
open
rewrite?
Is
there
I
spoke
about
Eclipse
Transformer,
it's
it's!
It
provides
a
tool
to
actually
transform
your
libraries
to
the
latest
release
from
your
class
files
to
your
book
to
your
waffles
and
Java,
so
even
third
parties,
and
also
changes
to
properties,
files
and
resources.
B
So
this
is
actually
quite
advanced
form
of
openly
write,
so
I
haven't
used
it
yet
because
most
of
my
for
me
personally
or
my
code,
Java
EE
written,
is
basically
using
Java
e
framework.
So
for
me,
I've
never
had
issues
migrating
to
your
contact.
Ee,
so
I
haven't
used
Eclipse
format
to
actually
change
my
code
of
three
parties
because
I
have
moved.
We
don't
really
use
third-party
libraries
unless
we
really
necessarily
need
it
and
the
third
party
libraries
that
we
mostly
use
are
prime
faces
and
that's
already
they've
already
sorted-
that
portion
up
and.
B
Performance
so,
but
my
gratitude
is
Jakarta
is
you
can
take
advantage
of
performances
to
every
every
suppliers,
for
example,
or
or
companies
that
that
are
part
of
the
the
Java
Qatar
ecosystem
releases,
the
application
server
that
provide
also
enhanced
security
and
all
these
good
features.
So
by
writing.
A
B
B
Cloud
native
ready,
the
deployment
to
the
cloud
is
very
easy.
For
example,
your
your
containers,
most
of
the
your
containers,
are
already
you
can
find
them
already
on
Docker,
so
you
can
actually
dockerize
your
application
from
the
get-go
and
then
create
a
CD
SCI
CDs
workflow,
to
deploy
to
your
yours,
your
cloud
provider
of
choice,
whether
it's
it's
AWS
or
or
Microsoft,
azure,
for
example,
what
we
did
as
well.
We
took
application
that
we
moved
to
that.
What
that
is
running
on
prior.
A
B
We've
basically
dockerized
all
of
that
we've
moved
it
into.
We
created
our
a
workflow
pipeline
on
Jenkins
that
actually
takes
a
call,
builds
it
dockerizes
it
and
then
deploys
it
into
to
to
our
Azure
instances
and
then,
when
the
customer
actually
browse,
the
application
is
actually
from
an
application.
That's
running
on
as
your
cloud,
but
all
the
application
is
actually
dockerized.
So
when
we
get
new
teams
involved,
they
basically.
B
B
B
A
B
B
B
A
B
In
the
medical
field,
so
that
basically
this
is
a
for
those
in
a
I
was
going
to
say
Hospitality,
but
it's
not
hospital.
It's
not
Hospitality
in
a
medical
sector.
So
this
application-
and
it
says
I've-
got
a
code,
that's
broken,
so
something
broke
and
I,
don't
know
what
it
is
and
I
haven't
touched
any
code.
Yet
so.
B
B
B
B
B
Also
I'm
trying
to
play
with
Jakarta
data
which
which
I'm
gonna
go
into
in
the
near
future,
but
for
now
I
know
Jakarta
Jakarta,
11
11
is
going
to
come
with
your
data,
so
I'm
trying
to
anticipate
for
that
already
and
it's
got
postgres
and
all
of
that
good
features
on
there
and
I'm
using
open
Liberty.
As
my
container,
which
is
version
23.
B
B
B
B
B
B
Only
thing
is
jdbc:
your
jdbc
does
not
have
jakarta.c4
Dot
Dot
data
source
or
XA
data
source;
it
still
uses
Javas,
that's
the
only
thing
that
doesn't
change
is
your
jdbc,
because
I
tried
changing
that
to
Jakarta,
and
it
was
not
happy
and
other
than
that.
Everything
else
is
exactly
the
same,
and
these
are
your
configuration,
but
the
one
thing
I
wanted
to
show
you.
B
This
was
one
of
the
modules
I
wrote
to
to
move
everything
to
to
I
was
trying
to
do
the
whole
HTML5
components
basically,
and
is
it
this
thing
and
your
first
little
tag
library
is
still
Jakarta
ee.
Nothing
has
changed,
but
everything
else
is
exactly
the
same.
What
is
the
faces?
Config
your
faces
can't
fit
here.
If
I'm
not
mistaken.
B
Previously
it
was
called
manage
being
so
many
spin
has
changed
to
reference
V.
So
there's
one
thing
that
you
need
to
look
at
if
you're
gonna
create
your
own
taglib
Library
your
custom,
Library
purchases,
so
change
that
to
reference
B
and
then
everything
else
and
then
so
get
used
to
be
many
speed,
name
and
management
class.
B
B
B
B
B
B
B
Security
I'm
I'm
using
the
late
I'm
using
the
latest
security,
so
I
can
write.
I
can
do
write
my
custom
identity
store
and
here
I'm,
so
basically
implementing
the
authentication.
But
the
whole
point
is
the
latest.
Security
framework
allows
us
to
create
custom
identities,
so
so
I'm
trying
to
use
custom
identity
store
to
do
login
and
and
from
there
you
can
use
the
security
context
to
post
your
your
username
password
credential
to
to
here,
and
your
security
cortex
has
existed
from
java
ee
already.
B
So
two,
your
knowledge
in
using
your
Java
ee
application
hasn't
really
changed.
The
only
thing
that
that
has
changed
is
basically
your
Imports
and
and
all
of
that
stuff,
so
there's
no
Java
X
or
whatever.
This
is
my
custom
faces
useful,
but
everything
else
is
Jakarta
the
geographic
Imports.
What
used
to
be
Java
x,
dot,
Enterprise,
dot,
request
code,
which
is
CDI
request,
COPD,
it's
exactly
the
same,
there's
nothing
else
that
has
changed.
This
should
not
be.
B
This
one,
this
one
yay
so
there's
there's
a
there's
a
JC
Frontier
page.
This
is
brand
new.
So
it's
not.
It's
still
brand
new
development.
So
we
took
existing
stuff
that
we're
taking
is
this
stuff
that
worked
on
previous
code
and
we
just
decided
to
do
a
whole
rewrite
with
Jakarta
E10.
So
this
is
the
registration
for
your
login
form,
so
using
Json
for
any
trans
and
if
I
make
code
changes
here.
Open
Liberty
is
running
on
development
mode
and
you
can
just
if
it's
on
development
board,
so
any
changes
here.
B
It
will
automatically
redeploy
it
and
then
you
just
have
to
refresh
your
browser
and
then
and
see
your
changes.
So
basically
what
it
does.
It
does
a
watch
on
on
your
on
your
on
your
project.
So
it
does
a
watch
and
then
whatever
changes,
whether
it's
code,
whether
it's
resources,
whether
it's
your
JSF
HTML
Pages,
it
watches
all
of
that
and
then
and
then
it
has
a
auto,
auto
redeployment
for
you.
So
you
don't
have
to
shut
down
the
container.