camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Heinemann (JIRA)" <>
Subject [jira] Commented: (CAMEL-385) support attachments for better support of JBI and JAX-WS stuff
Date Mon, 17 Mar 2008 09:00:32 GMT


Lars Heinemann commented on CAMEL-385:


in my opinion a message is always made of the following three parts:

- some message header values / properties
- the base message content
- data attachments

This is the structure the JBI message is using. Now putting for example binary attachments
to a message 
header / property seems to be a "not so clean" workaround in my eyes. If doing so, every endpoint
would have to
implement some check logic if a header is an attachment or a property. Just compare the message
properties with
the property-files in some OS. It will always contain key = value pairs and no other things.
These values will always be
simple data types like String, Date etc.

Further I can not imagine that there is or will be another requirement than for these 3 parts.

Just my thoughts. 


> support attachments for better support of JBI and JAX-WS stuff
> --------------------------------------------------------------
>                 Key: CAMEL-385
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>            Reporter: James Strachan
>             Fix For: 1.3.0
>         Attachments: patch.diff

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message