►
Description
Speaker: Ivar Grimstad
When JSR 371 was dropped from the scope of Java EE, Oracle made the decision to allow the Community to finalize the specification. It quickly became known as the "Community JSR" and the slogan "@Controller to the Community" grew out of it.
When all the Java EE 8 specifications where transferred to Eclipse Foundation and Jakarta EE, MVC was once again left behind. We managed to release MVC 1.0 through the JCP and has since moved over to Jakarta EE as well. And we are on our way to release Jakarta MVC 1.1 through the Jakarta EE Specification Process. Maybe it is time for a new slogan? "The Specification that Never Dies!"?
In this talk, I will take you through this journey and show all aspects of the MVC in code. You don't want to miss this!
--
Get Social!
Subscribe: https://www.youtube.com/user/EclipseFdn
Follow us on Twitter: https://twitter.com/JakartaEE
Like us on Facebook: https://www.facebook.com/JakartaEE/
Join us on LinkedIn: https://www.linkedin.com/groups/13597
Tag us: #JakartaEE
Want more great Eclipse Community webinars? Become a member of our Jakarta Tech Talks Meetup: https://www.meetup.com/jakartatechtalks
A
Hello,
everybody
and
welcome
to
another
jakarta
tech
talk.
My
name
is
hudson
kelly
I'll
be
the
host.
Today.
Today's
session
is
on
jakarta
mvc
the
specification
that
never
dies.
We
are
lucky
enough
to
be
joined
by
a
speaker
that
many
of
you,
I'm
sure,
are
quite
familiar
with
evar
grimstad,
jakarta,
ee
developer
advocate
at
eclipse
foundation
and
java
champion.
A
B
So
this
is
my
twitter
handle
and
some
of
the
stuff
I
am
I'm
doing
in
my
daily
work
and
my
samples
and
everything
is
on
my
github.
You
can
see
it
here
feel
free
to
follow
me
on
twitter
or
follow
me
on
on
linkedin
as
well.
So
if
you
have
any
questions
during
this
talk,
go
ahead
and
ask
them
in
the
chat
and
we'll
try
to
do
it
as
we
go
or
just
have
a
dialogue
afterwards
and
feel
free
to
contact
me.
B
It
has
many
names
it's
been
around
for
a
while,
and
I
like
to
call
it
the
community
specification
and
also
one
of
the
slogans
we
had
during
this
time.
We
add
the
ad
controller
to
the
community
and
I'll
show
you
why
at
control
is
something
we
talked
about
with
embassy,
so
to
look
at
some
of
the
the
history,
okay
or
something
else
yeah.
We
won
some
awards
so
a
couple
of
years
ago
we
we
won
the
outstanding
adopter
jsr
award
and
we
also.
A
B
The
outstanding
spec
lead
award
and,
to
be
honest,
I'm
not
the
only
speculator
on
this
specification.
We
have
christian
and
christian
is
here
in
the
audience
as
well.
I
think
so.
Please
say
hi
christian
and
and
if
you
have
any
hard
questions,
put
them
to
christian
and
I'll
I'll,
take
the
easy
ones
and-
and
if
my
demo
screws
up
I'll
just
invite
christian
on
stage
here
or
in
in
the
stream,
and
he
can
fix
it.
For
me.
B
B
We
started
this
specification
actually
back
in
2014,
so
it's
been
six
years
and
that
was
when
it
was
proposed
in
the
java
community
process
and
it
was
approved
that
year
and
the
expert
group
start
started
working
and
pretty
fast.
We
we
delivered
a
early
draft
release
or
edr
one,
and
I
need
there
are
two
and
so
we're
kind
of
getting
ready.
We
had
the
specification
was
pretty
much
done
and
and
the
apis
and
everything
was
up
and
working
pretty
good.
B
So
we
can
finish
it
off
and
they
were
and
we
had
a
good
dialogue
with
them
and
they
pretty
fast
signed
it
over
and
they
signed
it
over
to
me
as
a
as
a
person
because
they
they
needed
some
legal
entities
that
could
to
receive
it
so
that
that
was
in
january
2017
and
it
took
a
couple
of
months
to
get
this
transfer
done.
It's
it's
some
documents
here
and
there
and
it
has
to
be
signed
by
people
to
get
it
done.
B
We
set
up
the
all
the
infrastructure,
all
the
github
reports
and
the
website
and
everything
and
and
continued
working
and
then
the
jakarta
ee
thing
came
along.
So
all
the
other
java
aspects
were
transferred
to
a
class
foundation.
So
we
we
thought
that
we
can't
be
any
worse.
So,
let's
transfer
as
well.
So
we
we
emailed
out
that
we
have
an
intention
to
transfer
to
atlas
foundation
as
well,
and
that
was
in
2017.
B
So
all
of
this
happened
during
one
year
and
usually
when,
when
you
present
these
timelines,
you
have
like
one
slide.
I
have
four
so
so
it
has
been
a
while
and
you
can
see
it's
lost
a
lot's
been
happening,
but
when
we
came
to
to
january
2018
we
had
a
public
review
in
the
jcp,
and
that
was
successful.
B
We
thought
that
let's
get
ozark
the
reference
implementation
over
checklist
foundation,
so
so
so
we
can
have
it
there.
So
we
did
that
transfer
and,
of
course,
ozark
wasn't
approved
as
a
name,
so
we
had
to
change
it.
So
we
kind
of
reversed
the
letters
and
created
a
crossover,
and
so
it
looks.
Graso
was.
B
B
B
B
A
B
That
kind
of
sets
the
starting
point
for
our
next
step
and
our
next
step
would
be
to
do
the
name,
space
change
that
is
what's
happening
with
jakarta,
e9
right
now.
It's
that
take
all
the
specification
and
move
them
from
the
java
x,
namespace
to
the
jigara
namespace.
So
that
is
something
we
will
start
with
directly
after
the
101
release
is
released
and
sometime
after
ee9,
we
will
be
able
to
release
chicago
mvc2
row,
which
will
be
on
the
jicarilla
namespace
and
hopefully
that
will
be
early
next.
B
Year,
so
what
is
embassy
then?
Well,
it
is
an
implementation
of
the
model,
view,
control
pattern
and
the
a
common
way
of
describing
the
model
view
controller.
Is
this
way
you
have
the
a
request
coming
in
from
the
browser
or
some
application
to
a
controller
that
does
some
updates
to
the
model
selects
which
view
to
to
render,
and
this
view
accesses
the
model
and
presents
it,
and
you
have
two
flavors
of
mvc.
B
You
have
the
component
based,
which
is
a
jsf
for
example,
or
jakarta
faces,
as
it's
called
now,
where
the
framework
handles
the
controller
you
have
the
faces.
That
is
the
controller,
so
you
only
take
care
of
the
model
and
the
view,
and
then
you
have
the
the
action-based
version
which
mvc
comes
under,
where
you
have
more
control
over
the
controller.
B
B
So
so
I
have
the
jaccardia
dimension
and
then
I
add
the
the
release
candidate
for
jakarta
mvc,
which
is
available
on
maven
central
and
I'm
using
the
the
milestone
versions
of
eclipse
grazo
so
and
in
this
demo
I'll
be
running
on
glassfish.
So
then
I'll
choose
the
jersey
version
of
crossover.
Otherwise
I
would
just,
for
example,
rest
easy
for
running
on
wildflowers
other
things
in
this
application
there
are
no
java
code,
and
the
only
thing
I've
put
in
here
is
an
index
file.
So.
B
B
B
A
B
A
B
A
B
B
B
A
B
A
A
B
A
B
B
A
B
A
A
B
B
A
B
A
B
So
what
I
do
here
is
I
I
set
the
property
0
protection
to
explicit.
That
means
that
I
will
have
to
explicitly
set
this
annotation
on
the
on
the
method
I
want
to
have
protected.
It
is
not
not
doesn't
need
to
be
protected
for
forgets
because
you're
not
sending
anything
so
for
a
post
it
it
makes
sense.
B
B
B
A
B
A
B
A
B
A
B
A
B
B
B
A
A
A
A
A
B
A
A
A
B
A
This
is
also
from
jax
red
and
it's
not
called
name
and
it's
a
helloform
object
and
I'll
call
it
hello
form,
and
now,
where
I'm
using
the
name
back
here,
I
can't
use
that
directly.
So
I'm
using
the
hello
form,
get
name
and
also
to
activate
the
remodelation
I'll
just
say
that
this
one
has
to
be
valid
ivor.
We
have
a
couple
questions
if
you
don't
mind
yeah
sure,
so
one
is.
Is
it
similar
to
struts
that
just
came
in.
B
It's
sort
of
similar
to
stress
yes,
but
it's
building
entirely
on
on
the
java
java
ee
technologies.
So
it's
it's
it's
more
of
a
standard.
So
so
many
of
the
ideas
from
here
are
from
struts
and
many
of
the
ideas
are
from
spring
mvc,
which
is
very
similar,
so
so,
with
with
spring
mvc,
for
example,
they
they
had
spring
msc,
which
did
this
kind
of
thing,
and
then
they
created
the
the
support
for
for
restful
and
endpoints
using
spring
embassy
and
we've
done
it.
The
other
way
around.
B
We
had
the
technology
for
restful,
endpoints
injectors
and
we
added
the
and
the
support
for
embassy.
On
top
of
that,
so
so,
and
and
starts
to
say,
a
separate,
it's
not
a
standard
it.
It's
kind
of
more
an
open
source
project
that
apache
foundation,
so
lots
of
many
of
the
ideas
from
scratch
are
here
and-
and
I
guess
struts
probably
could
implement
this
standard.
If
I
wanted.
A
B
A
B
B
B
A
A
B
A
A
What
they
were
so
I'll
just
go
in
here
and
have
it
have
some
cheating
here
so
I'll
just
and
can
we
see
msg
gives
me
a
actually
deprecated
html.
That's
that's
how
good
I'm
at
at
web
development.
So
I'm
saying
I
want
it's
red,
and
this
is
how
I
did
it
in
all
day.
So
I'll
do
that
now
and
what
I'm
doing
is
just
get.
B
A
A
B
Concept
we
haven't
done,
and
that
is
how
about
form
submissions.
So
if
I
read
submission
so,
if
I
go
in
here
and
you
see,
the
url
doesn't
change
it,
it's
still
a
hello,
no
matter
if
the,
if
it's
the
form
or
the
hello
jsp.
So
if
I
refresh
this
page
you'll
see
I'll
I'm
getting
a
re
a
phone
summation,
and
that
is
something
that
is
not
very
good,
especially
if
you're
handling
money.
B
B
A
a
normal
pattern
for
handling
this,
and
this
is
kind
of
the
usual
case.
This
is
the
one
I'm
I've
implemented
so
far.
This
case
is
a
reservation,
so
you
can
say
if
a
browser
has
a
reservation
form
that
that
it
posts
to
the
reservation
controller.
The
reservation
controller
updates
the
model
and
sends
ok
back
to
the
browser
which
displays
a
confirmation
form.
If
you
hit
refresh
on
this
confirmation
form,
you
will
actually
on
confirmation
form.
B
And
that
is
why
I,
with
the
greeting,
I
already
added
the
redirect
scope
here.
So
that
is
a
a
scope
that
is
specially
defined
for
embassy
and
otherwise
you
would
have
the
request,
scoped
or
the
application
scopes
and
etc.
So
this
is
the
redirect
scope
that
will
handle
and
keep
this
being
alive
through
a
redirect.
A
request,
scope
will
live
for
one
request
and
an
application
scope
would
live
for
the
entire
application,
so
this
one
leaves
one
redirect
and-
and
that
is
very
useful
when
you
do
this
kind
of
applications.
B
B
B
A
A
B
B
A
A
A
B
A
A
B
A
B
B
B
Okay,
comparison
with
jsf,
why
use
jsf
and
why
I
use
mse
okay,
so
jsf
is
the.
If
you
remember
the
the
slide
I
showed
with
the
component
based
mvc
and
the
action-based
mnc
jsf
is
component-based
and,
and
they
have
the
controller
defined
for
you,
and
they
have
a
very
clearly
defined
lifecycle
for
the
application
with
mvc.
It's
action-based
and
it's
much
more
up
to
you
as
a
developer,
to
define
how
you
you
implement
the
controllers.
B
So
so
it
gives
you
more
finer.
Grain
control
with
mvc
and
but
jsf
will
give
you
a
bigger
library
of
components
and
make
more
maybe
more
sophisticated
uis.
But
if
you
want
to
make
something
that
it's
faster
and
simpler
and
just
use
the
post,
the
the
the
request
and
and
post
redirect
get
parent.
For
example,
the
embassy
is
a
better
technology.
B
So
I
hope
you
enjoyed
this
talk
and
please
feel
free
to
check
out
the
samples
come
with
the
feedback.
If
you
want
to
have
something
different,
this
specification
is
going
on
and
we
will
try
to
get
version
101
out
pretty
soon
and
then
we
can
start
get
version
2.0
out
and
after
that
we
will
start
adding
new
functionality.
So
join
the
analysts
check
out
the
github
issues,
issue
trackers
and
try
it
out.
B
B
B
A
Thank
you,
yvar
and
thank
you
everyone
for
tuning
in
today,
this
session
will
be
available
on
youtube
and
at
this
link
after
the
video
has
processed.
If
you're
interested
in
hosting
your
own
session
for
a
tech
talk,
I
will
post
a
link
in
the
chat,
and
we
have
some
openings
coming
up
later
in
october
into
december,
that
we
would
love
to
fill
so
the
link
is
here
and
please
feel
free
to
fill
that
out.
Thank
you.