I just saw that the example is also present in the CXF examples. As Dan
pointed me to it I thought he had done it for the Talend Service Factory
specifically.
So no need to download the Talend stuff. You can find the example in the
cxf distribution.
Christian
Am 14.01.2011 08:55, schrieb Christian Schneider:
Hi Maatari,
I do not know of any way to specify intermediaries in the wsdl (that
does not mean there is no way ;-).
If I understood you correctly then you want your intermediary to kick
in for any service call. So what I would do is add the
intermediary as an interceptor into the cxf bus. That means it is
called for any service call.
In the interceptors documentation on the wiki there is a paragraph
"adding interceptors through configuration".
http://cxf.apache.org/docs/interceptors.html
If you use spring to configure cxf then this should help you. In any
case writing such an interceptor is not easy if you are not familiar
with the
framework internals.
Dan pointed me to an example inside the Talend Service Factory (Apache
Licensed).
http://www.talend.com/download.php
You need the Talend-SF-2.3.1 download.
There is an example configuration_interceptor that shows how to plug
an interceptor into all service calls. The interceptor does gzip
compression / decompression. So this
interceptor code is probably not so interesting for you. I guess you
rather would like to write your interceptor in a way to work on the
dom document like Dan described in one of the other messages.
Best regards
Christian
Am 12.01.2011 17:19, schrieb Maatari:
To be further specific here is one of the specific intent use.
My intermediary is like a platform that verify message and
transmit/forward
them to the original receiver.
If an end point is registered, it can send and receive message via the
platform. The intermediary is like a certification intermediary. As an
endpoint, you will only accept message that are somehow certify by this
intermediary.
Hence, endpoint A, want to send a message to endpoint B, that is
certify by
intermediary 0. Hence intermediary 0, receive it and shall know that
it is
intended for endpoint B, but only do the job of verification and
forwarding
if endpoint B, is registered to it and if the content is appropriate.
Many thanks,
-M-
--
----
http://www.liquid-reality.de
