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 2009/08/13 10:26:36 UTC

[jira] Commented: (CAMEL-1910) CamelHttpTransportServlet need to support init the camel context itself

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

Claus Ibsen commented on CAMEL-1910:
------------------------------------

Hmm can this be avoid and init lazy as Spring should really be in control when CamelContext is initialized.

I kinda want Spring to be 100% in control when and how CamelContext is initialized. Had a bad experience with Mule where you had to use a special context listener in web.xml to init mule. That caused all sorts of trouble for us.

> CamelHttpTransportServlet need to support init the camel context itself
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-1910
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1910
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-servlet
>    Affects Versions: 2.0-M3
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.0.0
>
>
> Since current servlet component need to deploy the servlet first then it can create the servlet endpoint for using.
> Here is the mail thread which discusses about the servlet component creation issue.
> http://www.nabble.com/How-to-create-a-Servlet-component--td24909157.html
> So CamelHttpTransportServlet need to support init the camel context itself after the servlet is initialized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.