camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Cifer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6232) Create a spring DSL, where we can introduce interceptors without explicit listing
Date Fri, 05 Apr 2013 15:43:18 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623726#comment-13623726
] 

David Cifer commented on CAMEL-6232:
------------------------------------

I found a shortcoming of the bean solution. If the route what I try to advice has property
placeholders. Than it is unable to create the interceptor. Probably because I'm receiving
the CamelContext reference before PropertyPlaceHolder initialized.
                
> Create a spring DSL, where we can introduce interceptors without explicit listing
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-6232
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6232
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-spring
>    Affects Versions: 2.10.4
>         Environment: Any
>            Reporter: David Cifer
>            Priority: Minor
>              Labels: spring
>
> We have a spring DSL based Camel system. I wanted to introduce an interceptor for one
of the routes, but I wanted to define it on a separate xml file. So when the xml is added
to the Spring Context Loader than the interceptor is active otherwise it isn't.
> Unfortunately camel support contextScan and packageScan for camel routes defined with
JAVA.
> My work around currently is having a bean, which have a route definition and start up
time camel context is injected. So it registers itself to the route.
> But a more fluent solution would be welcome.
> More details: http://camel.465427.n5.nabble.com/Refering-implicitly-to-routeContext-td5730047.html#a5730204

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message