Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <16001963.post@talk.nabble.com>
Date: Wed, 12 Mar 2008 05:07:41 -0700 (PDT)
From: davsclaus <cib_rejse@yahoo.dk>
To: camel-user@activemq.apache.org
Subject: Re: Camel TCP receiver endpoint
In-Reply-To: <16001744.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <15430834.post@talk.nabble.com> <15827541.post@talk.nabble.com>
 <15867258.post@talk.nabble.com> <15870389.post@talk.nabble.com>
 <15925676.post@talk.nabble.com> <15950664.post@talk.nabble.com>
 <15950769.post@talk.nabble.com> <16001744.post@talk.nabble.com>


Hi George

The best way to supply patches etc is to create a new ticket in JIRA (issue
tracker)
http://activemq.apache.org/camel/support.html

Then its not lost in this forum where people tend to read only the new
posts.

As I am supplying quite a lot of patches to the MINA component lately I
could take a look at your patches and get it into the core Camel.

I hear you point about just using the standard camel-mina component you will
be able to send messages over the network and not lose your header and other
properties on the exchange itself. 

So please create a JIRA and supply your patches and other files and we can
go from there.

/Claus


georgiosgeorgiadis wrote:
> 
> Hi Claus,
> 
> Thanks again.
> 
> We would prefer to use all camel components in a simple and transparent
> way, of course.
> Thus we would prefer that a patch especially for mina-camel component is
> applied as a patch into Camel itself.
> 
> I have made the modifications myself in the local snapshot of Camel 1.2.0
> here, which is the way for me to apply it in Camel? I can send my changes
> in which specific classes in this forum or not?
> 
> Best regards
> 
> Georgios
> 
> 
> 
> davsclaus wrote:
>> 
>> Gerorge
>> 
>> Have you tried to use your own codec? There is a codec parameter to the
>> uri configuration of camel routes.
>> 
>> The codec is then your Mina codec class where you can do the
>> encode/decode where you can include the headers and properties from the
>> exchange.
>> 
>> I am however not sure if using this codec it gives you access to the
>> exchange in your subclass?
>> 
>> Another approach is to do your own data format, there is some examples in
>> Camel where you can create your data formatter and annotate them. Then
>> you can have your dataforma POJO class that holds the body, header and
>> properties.
>> 
>> You are ofcourse welcome to try to create a patch for camel that includes
>> the header and properties out-of-the-box. It is however not so easy as
>> the raw TCP protocol is not a protocol that supports metadata as headers
>> and properties = everything is one long binary stream. Unlike eg.
>> messaging such as JMS.
>> 
>> 
>> /Claus
>> 
>> 
>> georgiosgeorgiadis wrote:
>>> 
>>> Hi Claus,
>>> 
>>> Yes, the requirement is that we connect to a local or TCP repository
>>> with the ability to switch from the one or the other only with
>>> configuration changes. The thing is that we specify some of the stuff in
>>> the headers and the properties and they don't seem to be passed when I
>>> use mina tcp camel endpoint.
>>> 
>>> Regards
>>> 
>>> Georgios
>>> 
>>> 
>>> davsclaus wrote:
>>>> 
>>>> Hi George
>>>> 
>>>> camel-mina does only support marshalling the body content. (in.body)
>>>> What is you use-case for using camel-mina to send messages that
>>>> contains headers and properties as well?
>>>> 
>>>> /Claus
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Camel-TCP-receiver-endpoint-tp15430834s22882p16001963.html
Sent from the Camel - Users mailing list archive at Nabble.com.