nent.java:189)
at
org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:134)
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:508)
... 43 more
--
View this message in context:
http://camel.465427.n5.nabble.com/add
Thanks for the feedback Raul! More inline...
On 21 October 2012 11:58, Raul Kripalani wrote:
> Hi James,
>
> The idea looks nice. I'm just a bit concerned about whether the concept
> steps on the toes of the interceptSendToEndpoint DSL to some extent?
>
> The interceptSTE DSL only triggers at the
Hi James,
The idea looks nice. I'm just a bit concerned about whether the concept
steps on the toes of the interceptSendToEndpoint DSL to some extent?
The interceptSTE DSL only triggers at the dispatch stage, not at the
response, so it doesn't _fully wrap_ it. Perhaps we could extend the
intercep
I should have added a link to some test cases to give you an idea of
how to use them...
Here's an example of using the "binding:nameOfBinding:endpointURI" approach:
http://svn.apache.org/viewvc/camel/trunk/components/camel-jackson/src/test/java/org/apache/camel/component/jackson/JacksonNameBinding
Inspired by the SwitchYard project and how it uses contracts in SCA, I
thought I'd take a stab at adding something vaguely similar to Camel;
to allow us to add bindings to an endpoint (e.g. ensuring a particular
Data Format is used in or out of the endpoint, to add a validation
step , add transacti
