[
https://issues.apache.org/jira/browse/CAMEL-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider moved CXF-3343 to CAMEL-3684:
-------------------------------------------------
Key: CAMEL-3684 (was: CXF-3343)
Project: Camel (was: CXF)
> Make servlet component compatible with a application context initialized with
> the contextloaderlistener
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3684
> URL: https://issues.apache.org/jira/browse/CAMEL-3684
> Project: Camel
> Issue Type: Improvement
> Reporter: Christian Schneider
>
> When using the servlet component we currently require that the
> applicationcontext is defined in the CamelHttpServlet like shown in:
> https://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/test/resources/org/apache/camel/component/servlet/web-spring.xml
> We should find a way to make the servlet component work with an
> applicationcontext that is loaded using the spring ContextLoaderListener.
> When working in OSGi with the servlet component I had the idea to not use a
> single CamelHttpServlet but to register a servlet just when the endpoint
> starts and exactly with the uri specified in the endpoint. This would solve
> the problem of finding the CamelHttpServlet and would also allow us to
> reserve paths in the webserver more fine grained.
> E.g. at the moment it is not easily possible to have a servlet on /test1 and
> one on /test2 while some other non camel servlet on the server uses /test3.
> With the aproach described it would be no problem.
> The main problem with the aproach that I see is that it would be slightly
> incompatible with the current aproach as a servlet endpoint servlet:///test
> with a url of test1 for the servlet at the moment results in /test1/test.
> With the new aproach it would always be at /test. We could make this more
> compatible if the servlet component can be initialized with a prefix (test1
> in that case).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
