Maybe its not to bad at all :-) If i got you right, i could do it like this:
<eip:content-enricher service="test:contentEnricher" endpoint="endpoint">
<eip:enricherTarget>
<eip:exchange-target service="test:TokenService" />
</eip:enricherTarget>
<eip:target>
<eip:exchange-target service="test:xslt" />
</eip:target>
</eip:content-enricher>
<eip:static-routing-slip service="test:routingSlip" endpoint="endpoint">
<eip:targets>
<eip:exchange-target service="test:contentEnricher" />
<eip:exchange-target service="test:theActualService" />
</eip:targets>
</eip:static-routing-slip>
Right?
cheers, Johannes
> So why don't you use this concatenation offered by CE and do XSLT after that
> to insert what you want to the original message?
> Other question, wha is the relation between original request and the request
> to token service?
> Where are both of this request created?
>
>
> JMan_JE wrote:
>
>> Ok,
>> in the case i write my own bean, i have to invoke the token service
>> inside from my bean? I wouldn't really like that idea. Maybe bpel is
>> just the better option in this case?
>>
>>
>>
>
>