On Jul 23, 2008, at 6:48 AM, Oliver Wulff wrote:
One follow on question:
Let's assume a complexType called WageData is defined. We have a
client
which calls an intermediary which then calls the target wage data
service.
Some data must be encrypted with the public key of the intermediary
but the
WageData type must be encrypted with the public key of the target
wage data
service.
Let's assume that a soap request with two security headers (different
actors for intermediary and target service) is received in the
intermediary. The interesting part now is how the language binding
(JAX-WS)
looks like for the WageData type. The intermediary can't decrypt it
but the
JAX-WS service implementation must access this element to pass it on
to the
target service. Is this usecase covered in JAX-WS
Yes, indeed, that is a problem for any middleware stack that needs to
unmarshal DOM into some kind of type system, be it JAX-B, or Mom's Own
Cooking types.
In that case, the best the intermediate can do is re-marshal the DOM,
and pass the request on to the next tier.
I'd think that an EIP engine, like Apache Camel, would be the right
tool for the job, not a service creation engine, like Axis or CXF.
-Fred
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
