►
From YouTube: Kong Execution Pipeline - XML SOAP Handling
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
A
On
this
execution
of
the
pipeline
of
the
xmloop
in
the
demonstration,
we
will
use
a
SOP
service
of
mathematical
calculation
of
addition
of
subtraction,
on
which
we
will
carry
out
in
one
of
the
transformation.
We
will
add
an
operator
who
forgot
in
two.
We
will
check
that
the
flow
that
was
from
the
question
that
was
generated
and
conforms
to
the
SSD
scheme
potentially
generate
errors
in
3.
We
can
change
an
addition,
subtraction
operation
in
4.
We
will
do
routing.
A
A
We
will
check
the
correct
syntax
compared
to
the
XSD
schema
and
we
will
carry
out
a
final
transformation
step
7,
which
will
consist
in
transforming
the
envelope
jump
on
impure
XML
flow,
all
the
documentation
which
created
at
this
palpine
of
execution
of
XML,
processing,
Saul
and
referencing
in
a
positive
rule,
which
is
public
that
I
will
communicate
later
accident
positoury.
We
will
find
the
block
diagram
and
the
different
actions
that
allow
to
configure
this
assembly
execution.
A
Papel
already
been
done,
like
deploying
the
Kong
solution,
which
was
deployed
locally
I
propose
to
directly
access
the
configuration
within
Kong
Gateway
of
a
service
of
mathematical
calculation
service,
of
course,
that
will
perform
additions.
Subtractions
things
like
that
here
there
is
the
URL
I
suggest
you
use
this
number
layer
or
at
service
to
do
this.
Let
's
use
the
local
gong
manager.
Let.
A
On
the
URL
in
question
that
will
be
accessible
from
a
route,
an
access
route,
we
will
name
it
the
same
way.
It
goes
observice
with
a
path
that
the
name
of
the
route
to
test
this
route.
As
a
consumer
of
support,
you
just
have
to
go
back
to
my
hipository
and
take
this
example
of
brand
call,
and
here
I
was
able
to
run
through
magateway,
which
is
locally
which
costs
on
the
product
1000.
A
To
do
this,
we
will
press
the
repeat,
which
offers
a
certain
number
of
captures
first
test
case:
implementation
of
an
XSLT
transformation
on
the
request,
which
will
consist
of
add
a
tag
to
the
XML
request.
The
XSLT
transformation
that
is
proposed
is
this
one.
We
are
going
to
try
to
find
I
remind
you
that
we
are
adding
A
and
B.
We
are
going
to
delete
B
and
we
are
going
to
ask
official
t
of
the
EN
add.
So
we
are
looking
for
the
operand
a
and
we
will
add
the
B.
A
A
The
XML
request
1
transforms
XLT
before
is
here.
There
are
other
plugins
that
will
be
presented
later,
relatively
simple.
You
just
have
to
put
the
transformation
that
we
have
just
copied
and
pasted
here.
It
is
in
place.
I
go
back
to
my
execution
and
voluntarily
I
will
delete
the
l,
'operand
D,
with
its
value,
7
and
I'm,
going
to
inject
through
the
CST
the
value
8.
A
A
A
Two-Part
validation,
plugin,
the
validation
that
will
be
done
on
the
XSD
schema
specific
to
the
API.
It
is
here
and
the
ISSD
schema
of
the
envelope
jump,
which
is
already
configured
in
advance,
which
is
based
on
the
W3C,
so
once
it
is
in
place,
it
is
very
easy
for
me
to
validate
that
it
already
works,
always
well
perfect.
The
XML
envelope
of
the
question
is
validated
with
its
schema:
xD
And.
If
I
deliberately
introduce
errors
body
put
your
body
Kong.
Of
course
it
does
not
exist
in
the
W3C.
A
There
will
be
an
error
notification.
It
is
a
soup
flow
error
500
ago,
a
code
fault,
and
there
we
say
whatever
that.
Finally,
the
xD
validation
failed,
the
body
Kong
element
it
is
not
tense,
so
it
is
true
for
the
jump
envelope
that
we
modified
and
that
we
are
going
to
put
back
in
conformity
with
the
norm,
and
it
is
also
true
for
the
how
to
say
the
envelope.
A
A
A
bit
3
so
there
the
idea
is
a
transformation
that
was
after
XSD,
which
consists
in
replacing
a
subtraction
tag.
The
subtract
by
the
addition
it
looks
like
there.
We
will
call
the
service
to
carry
out
a
subtraction,
but
to
steal
it.
We
will
transform
it
to
finally
make
an
addition,
use
the
step,
3
plugin,
which
this
processing
is
carried
out,
that
we
will
first
configure
well
passing
without
configuration
to
ensure
that
the
subtraction
is
well
carried
out.
A
A
A
I
call
back
my
service
and,
where
I
configure
as
input
in
the
request,
the
subtraction
this
third
floor
of
the
pancline,
transform
it
to
me
into
an
addition
and
again
we
end
up
with
the
result
of
an
addition.
The
famous
13,
let's
go
to
the
last
step
of
the
bipeline
concerning
the
processing
of
the
request
is
the
dynamic
routing.
The
idea
is
to
call
another
oslame
on
this
SOP
service.
A
A
A
The
stream
it
is
here,
simple,
logical
object,
I,
create
I,
will
associate
this
callback
target
its
capacity
to
do
with
load
partition
on
different
targets.
Here
there
is
only
one
the
same
one
we
can
put
different
high
names
or
different
IP
addresses
the
plugin
in
question.
I,
add
it
what
makes
the
dynamic
routing
route
by
xpass
the
4
parameters
to
configure?
What
is
the
path
of
this
new
service?
It
was
given
here.
A
The
hubstream
that
we
created
it
is
this
one
the
request
x
passes.
It
is
the
a
that
we
will
recover
the
operand,
a
on
which
conditions
the
list
is
simple:
it
is,
as
it
is
called.
There
is
a
small
action
to
do.
An
additional
action
is
to
adapt
the
XLT
transformation
plugin
a
little
bit,
because
the
way
it
called
the
Add
method
is
not
all
exactly
the
same
as
for
the
other
service,
so
a
notion
of
urn
layer
which
must
be
added
in
front
of
the
addition
layer.
A
So
that
is
what
we
want
to
have.
There
is
a
difference
we
are
not
necessarily
seeing,
but
we
have
capitalized
so
that
we
capitalize
it's
not
all
the
plugins
that
do
that.
It's
the
service,
the
new
service
that
is
called
it's
the
one
that
returns
a
stream
in
uppercase.
First,
first
thing:
second
thing:
previously:
we
had
ultraise
addresses
there
this
time
that
simply
results
well
well
very
well,
and
then
there
is
even
the
same
space
which
was
added
the
urine
layer.
A
This
is
what
required
that
we
carry
out
a
transformation
modification
to
transformation
X,
and
we
are
finished
for
the
treatment
of
the
question
with
the
pipeline.
We
find
all
the
plugins
that
are
presented
on
the
screen
here.
This
time
we
will
go
to
the
step
of
processing
the
response
in
my
pipeline.
Let's
go
to
example,
5,
which
therefore
illustrates
the
idea
it
will
be
before
the
XSD
validation
there.
What
are
we
going
to
do?
A
Let's
go,
we
will
put
the
three
response:
transformation
plugins
like
that
it
will
be
done.
They
are
here
the
xxlt
before
transformation
before
the
XSD
validation.
It
is
here
on
the
screen.
I
take
this
opportunity
to
put
back,
as
I
also
said,
the
XSD
validation
for
the
moment,
I
deploy
them
without
configuring
them
and
the
last
XML
actually
that
I
have
under
the
screen
here.
I
have
the
complete
step
of
execution,
the
one
that
we
are
going
to
configure.
A
It
is
the
transformation
since
we
said
that
we
have
transformed
them,
and
indeed
the
result
in
congress
results
and
as
well
as
the
ns
address
in
response,
so
that
it
is
done
with
this
transformation
which
is
prepared
for
us.
We
configure
it.
I
save
I,
call
back
my
service,
and
so
there,
what
are
the
differences
as
I
told
you,
we
change
the
ns
address
simply
by
address.
It
is
not
obvious
that
this
way
of
naming
this
tag
complies
with
W3
C
standards.
A
So,
let's
put
things
square,
that's
also
the
interest
of
governance,
the
solution
of
Kong
and
then
so
the
result
bah.
Well,
we
added
an
ultraise
congress
rather
than
simply
a
result.
So
what
is
just
changed
enough
is
along
the
beacon.
The
result
on
13
is
dynamically.
Retrieved.
Here
is
the
first
transformation
x
slt
of
the
response.
A
Let's
move
on
to
the
penultimate
step
of
the
processing
of
the
packet
concerning
the
response.
This
is
the
validation
we
can
put
a
validation
scheme.
This
is
gone.
You
know
that
we
had
already
configured
rather
install
the
XSD
validation
plugin
from
the
response
now
configure.
It
I
remind
you
that
it
is
always
configured
with
the
soup
envelope
of
the
double
3C
standard
by
default,
so
it's
always
done
and
there
we
simply
add
the
XSD
specific
to
the
pie.
So
that
means
that
this
time,
if
I
remember
no
error,
everything
is
fine.
A
It
is
in
accordance
with
the
perfect
diagram,
go
last
stage
of
the
demonstration.
It
will
consist
of
my
faith
in
transforming
the
saved
response
stream
into
a
pure
XML
stream,
so
it
will
be
done
on
the
last
plugin
of
the
pipeline.
It
is
the
transform
xclt
after
and
we
do
it
with
this
transformation,
which
was
prepared
in
advance
Ben,
who
goes
who
go?
Who
will
put
aside
all
the
soup
type
tags?