Hi Claus,
I tend to disagree on that. I actually think that having a generic Attachment
API in Camel does make sense. Having Attachments only as part of MailMessage
and e.g. a (currently non-existing) CXFMessage would mean, that it is e.g.
impossible to receive an attachment via mail and then f
On Thu, Apr 7, 2016 at 2:42 PM, Siano, Stephan wrote:
> Hi,
>
> Is there anybody available in this list who knows why the attachment handling
> in Camel is as it is?
>
> I have had a look into this topic with the Camel-Mail and Camel-CXF
> components and would like to discuss my thoughts about t
Hi
Maybe the endpoint can be specified as both id an uri.
Then if you want to refer to an existing by id as it does today, you
just use ref:
runEndpoint=ref:foo
runEndpoint=direct:foo
This also allows to route to seda / jms etc.
runEndpoint=seda:bar
runEndpoint=jms:queue:numbers
Though if you
While implementing the hystrix component, I had to choose whether to
use endpoint Ids or direct component for run/faillback endpoints.
I've chosen endpoints, as it allows defining any kind of endpoints
with all the options and then refer to it by its id. The downside is
that you have to add the en
Github user binfalse closed the pull request at:
https://github.com/apache/camel/pull/938
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Hi chaps,
I'm also not very happy with the way endpointId are part of the
hystrix URL but that was the only non-intrusive way I manged to
implement it atm. Keep in mind that we want both Java and XML dsl
solution. So if you have any ideas to make it easier to use, feel free
to work on it. I won't
