►
From YouTube: Jakarta Mail 2.1 / Angus Mial 1.0
Description
This live presentation will be covering the following topics:
1. What is Jakarta Mail
2. What is new in Jakarta Mail 2.1
3. What is Angus Mail
4. Demo
Jakarta EE
Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.
Learn more: https://bit.ly/3IPrxOq
Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/
A
A
Yes,
okay,
okay!
So,
let's
start
so
this
I'm
going
to
talk
about
jakarta,
2.1
and
language
1.0,
and
we
are
going
to
have
small
theory.
Small
theory
just
three
points
about.
I
think
something
that
is
relevant.
What
is
jakarta
made?
What
is
new
in
jakarta
2.1
and
what
is
angus
mail
and
we
will
have
a
short
demo
and
at
the
end
I
will
show
you
some
references
in
case
you
want.
You
have
questions
about
mail
or
angus,
or
you
want
to
discuss
something
about
the
demo
or
whatever
you
want
to
ask
okay.
A
So,
let's
what
is
jakarta
mail?
I
think
if
you
have
been
working
in
java
and
you
have
sent
an
email,
you
have
probably
used
this
library
already,
I'm
going
to
read
this.
That
comes
from
the
specification
to
be
accurate,
so
the
jakarta
mail
api
provides
a
set
of
abstract
classes,
defining
objects
that
come
from
that
comprise
a
mail
system.
The
api
defines
classes
like
message,
store
and
transport
and
the
the
api
can
be
extended
and
can
be
supplied
to
provide
new
protocols
and
to
add
new
functionality
when
necessary.
A
A
A
A
A
message
defines
a
set
of
attributes
and
a
content
for
email
messages.
For
what
I
said,
for
example,
xavier
recipients,
content
type
attachments,
the
transport,
it
models,
the
transport
agent,
that
routes
the
images
to
its
destination
addresses
and
the
store
is
where
we
are
going
to
to
store
the
messages
and
in
the
store,
usually
you
have
folders
and
folders
can
contain
other
folders
or
messages,
and
we
have
the
session
which
it
was
not
shown
in
this
picture.
But
it
is
session,
is
everywhere
in
in
in
jakarta
mail.
A
So,
basically
it
contains
the
configuration
and
it
can
create
instances
with
that
configuration.
For
example,
if
you
send
a
message-
and
you
use
the
transport
you
send
it
with
smtp
protocol,
for
example,
you
need
to
specify
the
host
and
the
port
where
you
want
to
at
least
where
you
want
to
send
the
message.
So
that's
all
the
properties
are
kept
in
the
session
and
with
the
session
you
can
use
it
as
a
factory
to
create
instances
of
transport
store
and
such
things.
A
Basically,
there
are
two
things
one
is
in
in
in
jakarta:
mail
we
have
in
the
past
the
implementation
and
the
api
mixed
together.
So
if
you
open
the
java
file
of
jakarta
mail
in
previous
versions,
you
will
see
that
you
have
two
kind
of
packages.
This
is
for
the
implementation
and
this
is
for
the
api.
A
A
That
it
contains
it's
kind
of
factory
that
provides
different,
encoders
and
decoders.
We
have
the
mail
ap,
jakarta
mail
requires
some
of
them
here.
We
have
some
examples,
so
the
implementation,
different
implementations,
will
have
to
provide
implementations
of
this
interface
and
the
way
we
do
it
is
as
usually
in
in
jakarta
projects
we
use
the
service
lookup,
which
I
can
show
you
how
it
is
in
case
you,
don't
you
don't
know
it,
I'm
going
to
show
it,
for
example,
the
implementation
of
the
default
implementation
of
the
stream
provider.
A
It's
angus
mail,
as
we
will
check
it
later,
and
we
can
see
that
this
inter
this
class,
is
implementing
this
interface
and
it
has
different
decoders
and
encoders
okay
and
the
service
lookup.
The
way
it
works
is
you
need
to
have
the
implementation
in
place
and
you
need
to
configure
in
the
meta
inf.
You
need
to
have
a
service
folder
with
the
net,
with
the
name
of
the
interface
or
class
you
want
to
extend
or
implement,
and
inside
of
it
you
just
need
to
write
the
class
that
is
going
to
to
implement
it.
A
A
A
Okay.
So,
let's
now
we
can
move
forward
to
the
demo,
and
I
this
is
the
link
of
the
demo.
I
already
have
it
open.
Yes,
okay,
so
in
this
demo
we
are
going
to
do
two
things
very
simple
things.
We
are
going
to
send
one
email
with
smtp
protocol
and
we
are
going
to
read
the
email
from
the
inbox
with
e-map
protocol.
A
A
So
you,
you
will
be
able
to
start
it
just
executing
one
script,
but
I
think
is
that
you
will
need
to
have
docker
well,
you
need
docker
to
have
the
mail
server
and
in
order
to
execute
the
demo,
you
will
need
to
have
java
11
or
more
and
maven
okay.
So,
let's
first
I'm
not
going
to
execute
it
right
now.
Let's
first
check
the
the
demo
code.
Let's
start
from
the
pawn
file,
so
the
pawn
file
is
pretty
straightforward.
It
only
has
the
male
angus
dependency.
A
A
A
So,
okay,
that's
the
dependency
we
have.
The
other
things
you
see
here
is
just
to
compile,
with
java
11,
to
use
utf-18
calling
and
some
clients
to
compile,
to
generate
a
jar
file
with
an
executable
class
and
to
put
some
dependencies
in
some
folder.
But
it's
not
really
required
to
understand
this.
Yes,
the
only
important
thing
is
that
we
have
the
angular
small
dependency
and
the
only
class
we
have
this
is
everything
is
the
class
that
is
going
to
send
an
email
and
it's
going
to
read
the
email
okay.
A
A
So
the
first
thing
we
have
is
we
create
some
properties
for
two
protocols
for
smtp
and
for
e-map
because,
as
I
said,
the
we
will
send
email
with
smtp
and
we
will
read
it
with
emap
and
these
magic
addresses
are
related
to
my
docker,
because
once
we
start
docker
the
docker
container,
it
will
forward
these
ip
addresses
to
the
docker
port.
That
is
actually
where
the
mail
server
is
running
and
it
is
listening
for
smtp
and
map
connections.
A
A
A
We
are
setting
a
standard
message
in
the
subject
and
the
text
that
is
coming
from
the
argument,
and
then
we
just
invoke
the
the
transport.send
and
how
does
it
know
where?
Which
protocol
does
it
need
to
use?
It's
because
we
are
passing
a
message.
The
message
has
the
session
and
the
session
has
the
properties.
A
We
are
going
to
read
the
image
of
this
user.
It
makes
sense
because
it's
the
user
that
is
receiving
the
email.
So
the
way
we
do
it
is
we
create
from
session.
We
create
a
store
for
the
e-map
protocol
and
we
connect
with
the
user
and
password
the
password
user
and
password
is
already
configured
in
the
docker
container.
A
A
A
A
A
So
that's
pretty
much
the
demo.
We
have
seen
how
to
add
a
language
mail
and
how
to
use
two
basic
things
and
the
email
and
reading
emails,
and
now
we
can
so
guess
the
last
thing
in
case
you
have
questions
you
can
check.
Well,
if
you
want
to
extend
your
knowledge,
you
can
read
the
mail
spec
everything
is
written
there.