camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jfaath <jfa...@apache.org>
Subject Re: Deploying as web app with jetty endpoint
Date Wed, 14 Apr 2010 14:19:47 GMT

That seems to finally work...providing I remove the "Jersey Filter" that is
used by the web console.  This effectively breaks the Camel web console, so
as of now it appears the two are incompatible.



willem.jiang wrote:
> 
> Oh, you should not use the ContextLoaderLister to load the camel route.
> There is a contextConfigLocation parameter that you can pass to the 
> CamelHttpTransportServlet to load the camel route.
> You can find the example here
> https://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/test/resources/org/apache/camel/component/servlet/web-spring.xml
> 
> Willem
> 
> jfaath wrote:
>> I played around with this by removing everything below the
>> ContextLoaderListener listener.  I still get the same error.  As a rule,
>> it
>> seems that Tomcat always loads listeners before servlets.
>> 
>> What exactly is the expected behavior of the bootstrap process in the
>> servlet container?  What is the contextConfigLocation parameter supposed
>> to
>> do?
>> 
>> Is there a sample of using this component in an actual servlet container?
>> 
>> 
>> willem.jiang wrote:
>>> Hi,
>>>
>>> Can you remove the web console part and try again?
>>> Maybe there are some side effect of the web console configure.
>>>
>>> Willem
>>>
>>> jfaath wrote:
>>>> So should I post a JIRA on this?  The servlet component doesn't seem to
>>>> work
>>>> in v2.2 when used in the web console.
>>>
>>>
>> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Deploying-as-web-app-with-jetty-endpoint-tp28171746p28243271.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Mime
View raw message