[
https://issues.apache.org/jira/browse/CAMEL-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997682#comment-12997682
]
Christian Schneider commented on CAMEL-3549:
--------------------------------------------
Hmm, I worked on the OSGi ticket above. But this one is about non OSGi. I am
not yet sure how to do it exactly but the basic idea is to let the endpoint
start up without waiting for the servlet and let the servlet later pick up the
connections.
So we would not have the requirement anymore that the servlet must start first.
Do you think that could work?
> 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: Christian Schneider
> 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
