Hi there-
I have the following scenario:
external WS client -> http-consumer -> content-enricher -> http-provider ->
external WS provider

When I connect the http-consumer to forward to the content-enricher it does
enriching of the
SOAP message content, but then returns (provides back) to the NMR and the
http-consumer picks it up and return it back to the client
instead of forwarding to the http-provider and executing the remote web
service and then go back the same rout to the external client.

By mine understading
<eip:target>
      <eip:exchange-target service="ns:LoggerWebService" /> <!-- this is the
soap-provider ->
    </eip:target>

should designed the next service in the chain. Is that correct?
It seems that my EnricherBean is InOut and it provides back to the NMR where
my http-consumer
picks it up.

I have this settings for the EIP

<eip:content-enricher service="ns:contentEnricher"
endpoint="contentEnricherEP">
    <eip:enricherTarget>
      <eip:exchange-target service="ns:loggerEnricher" />
    </eip:enricherTarget>
    <eip:target>
      <eip:exchange-target service="ns:LoggerWebService" /> <!-- this is the
soap-provider ->
    </eip:target>
  </eip:content-enricher>

<bean:endpoint service="ns:loggerEnricher" endpoint="ns:LoggerEnricherEP"
bean="#enricherBean"/>

  <bean id="enricherBean"
class="com.gallup.webservices.logger.EnricherBean"/>

Any help will be appreciated.

Reply via email to