The first lines of the Content Enricher read as:

        if (!(exchange instanceof InOnly) && !(exchange instanceof
RobustInOnly)) {
            fail(exchange, new UnsupportedOperationException("Use an
InOnly or RobustInOnly MEP"));
        }

So I don't really understand how you could use it with in InOut MEP.

On Fri, Mar 7, 2008 at 5:05 AM, sachin2008 <[EMAIL PROTECTED]> wrote:
>
>  Hi gnodet,
>
>  My scenario is:
>
>  HTTP BC------>wiretap----> CBR--->static routing slip--->content
>  enricher------>static routing slip
>
>  I have used content enricher as InOut... but you are telling it is an inonly
>
>  So can u please help me in this ....
>
>
>
>
>  gnodet wrote:
>  >
>  > Have you checked:
>  >
>  > 
> http://servicemix.apache.org/servicemix-eip.html#servicemix-eip-ContentEnricher
>  >
>  > 
> http://servicemix.apache.org/servicemix-eip.html#servicemix-eip-StaticRoutingSlip
>  >
>  > Btw, the content enricher supports InOnly meps, whereas the
>  > StaticRoutingSlip expect InOut meps,
>  > so these are used in very different use cases.
>  >
>  > On Thu, Mar 6, 2008 at 1:57 PM, sachin2008 <[EMAIL PROTECTED]> wrote:
>  >>
>  >>  Can you please tell me the difference between content enricher and
>  >> static
>  >>  routing slip using some configurations.
>  >>
>  >>
>  >>
>  >>  gnodet wrote:
>  >>  >
>  >>  > The filter and content enricher works with InOnly mep, the content
>  >>  > based router should work with any mep.
>  >>  > Btw, when the InOnly is supported, RobustInOnly is too.
>  >>  >
>  >>  > On Wed, Mar 5, 2008 at 5:24 AM, sachin2008 <[EMAIL PROTECTED]>
>  >> wrote:
>  >>  >>
>  >>  >>  Hi,
>  >>  >>
>  >>  >>  I am giving a list of patterns :
>  >>  >>
>  >>  >>  wiretap: It can handle all the four MEPs and sends only inOnly
>  >> message
>  >>  >> to
>  >>  >>  the listener.
>  >>  >>  static recipient list: it will forward only inonly MEPs to multiple
>  >>  >>  recipients at a time.
>  >>  >>  static routing slip: it will forward an inout message in sequence
>  >>  >> fashion.
>  >>  >>  content based router: ?
>  >>  >>  content enricher: ?
>  >>  >>  pipeline:bridges gap between the inonly  and inout meps.
>  >>  >>  Message Filter : ?
>  >>  >>  xpath spltter:inonly
>  >>  >>  split aggregator:inonly
>  >>  >>
>  >>  >>
>  >>  >>  Can any one please modify if there is any mistake in handling MEPs
>  >> for
>  >>  >>  different patterns
>  >>  >>
>  >>  >>  -----
>  >>  >>  Cheers
>  >>  >>  Praveen Oruganti
>  >>  >>  "Think before you act and act on what you believe"
>  >>  >>  --
>  >>  >>  View this message in context:
>  >>  >>
>  >> http://www.nabble.com/reg%3A-handling-MEPs-tp15843000s12049p15843000.html
>  >>  >>  Sent from the ServiceMix - User mailing list archive at Nabble.com.
>  >>  >>
>  >>  >>
>  >>  >
>  >>  >
>  >>  >
>  >>  > --
>  >>  > Cheers,
>  >>  > Guillaume Nodet
>  >>  > ------------------------
>  >>  > Blog: http://gnodet.blogspot.com/
>  >>  >
>  >>  >
>  >>
>  >>
>  >>  -----
>  >>  Cheers
>  >>  Praveen Oruganti
>  >>  "Think before you act and act on what you believe"
>  >>  --
>  >>  View this message in context:
>  >> http://www.nabble.com/reg%3A-handling-MEPs-tp15843000s12049p15872580.html
>  >>
>  >>
>  >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>  >
>  > --
>  > Cheers,
>  > Guillaume Nodet
>  > ------------------------
>  > Blog: http://gnodet.blogspot.com/
>  >
>  >
>
>
>  -----
>  Cheers
>  Praveen Oruganti
>  "Think before you act and act on what you believe"
>  --
>  View this message in context: 
> http://www.nabble.com/reg%3A-handling-MEPs-tp15843000s12049p15889554.html
>
>
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to