You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/03/02 10:41:37 UTC

[jira] Assigned: (CAMEL-3549) It should be possible to configure the CamelHttpTransportServlet using the spring ContextLoaderListener

     [ https://issues.apache.org/jira/browse/CAMEL-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-3549:
----------------------------------

    Assignee: Claus Ibsen  (was: Christian Schneider)

> It should be possible to configure the CamelHttpTransportServlet using the spring ContextLoaderListener
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3549
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3549
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-servlet
>    Affects Versions: 2.5.0
>            Reporter: Christian Schneider
>            Assignee: Claus Ibsen
>             Fix For: 2.7.0
>
>
> The spring security example uses two different spring contexts.
> The first is pulled up using the spring ContextLoaderListener. It is used to hook spring security into a filter.
> The second is pulled up by the CamelHttpTransportServlet. There is the main configuration includeing the camel context.
> I think this is quite ugly and makes things more complicated than they need to be. Especially if you also need the camel context outside the camel servlet.
> So I propose to change the code of the Camel Servlet component to simply use the spring context from the ContextLoaderListener. I can try to do the change myself but would be happy for any comments why this was designed so and where I have to be careful.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira