Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 74.125.46.152 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=sJ1ksymQOOZZ8n8O+yk1eDfs1ijlpXxuIK4rp7InyPHUWDLgWpzazW8PktDuHpjxpp
         C2/TIQQlUQEcCvZCv858Z32WeGKLZxJXCnbeb+hqMUTXSAAfFqQYeDyOfw98BtBYmYTB
         sz67KYJp02wA3hd6rI5JGMeJwkPgdUsyzgfx0=
Message-ID: <5380c69c0812090350l311775f1mfde7db90d72b5d5f@mail.gmail.com>
Date: Tue, 9 Dec 2008 12:50:49 +0100
From: "Claus Ibsen" <claus.ibsen@gmail.com>
To: camel-dev@activemq.apache.org
Subject: Re: [CONF] Apache Camel: Event Message (page edited)
In-Reply-To: <2068256394.1228821480033.JavaMail.www-data@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2068256394.1228821480033.JavaMail.www-data@brutus>

Hi James

I am not on IRC anymore because of network blockings at current client.
But the exchange pattern URI options isn't it: exchangePattern and not pattern?

This
foo:bar?pattern=InOnly

Should be:
foo:bar?exchangePattern=InOnly

Or am I mistaking, or is there a special option on the jms component for this?


/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/


On Tue, Dec 9, 2008 at 12:18 PM,  <confluence@apache.org> wrote:
> Page Edited : CAMEL : Event Message
>
> Event Message has been edited by James Strachan (Dec 09, 2008).
>
> (View changes)
>
> Content:
>
> Event Message
>
> Camel supports the Event Message from the EIP patterns by supporting the
> Exchange Pattern on a Message which can be set to InOnly to indicate a
> oneway event message. Camel Components then implement this pattern using the
> underlying transport or protocols.
>
> The default behaviour of many Components is InOnly such as for JMS or SEDA
>
> Explicitly specifying InOnly
>
> If you are using a component which defaults to InOut you can override the
> Exchange Pattern for an endpoint using the pattern property.
>
> foo:bar?pattern=InOnly
>
> Using This Pattern
>
> If you would like to use this EIP Pattern then please read the Getting
> Started, you may also find the Architecture useful particularly the
> description of Endpoint and URIs. Then you could try out some of the
> Examples first before trying this pattern out.
>
> Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) -
> Bug/feature request
>
> Unsubscribe or edit your notifications preferences