willem.jiang wrote:
>
>
> Oh, you want to the camel servlet component be managed by camel web
> console.
> After go through the SpringServlet code I think you set the CamelRoute
> configure location into the SpringServlet's init-param just like
> CamelHttpTransportServlet does, then you can add the
> ContextLoaderListener as usual.
>
> Willem
>
>
One of the major points of this thread was that you couldn't use the
ContextLoaderListener with the camel-servlet component due to bootstrapping
issues so this won't work at all.
However, I have come very close to getting this all to work. Turns out
there's a ContextLoaderServlet that does the same thing as the listener.
So, I can first load the camel-servlet, then load the context loader and
finally the jersey SpringServlet using the load-on-startup directive.
Everything starts cleanly and the endpoint and routes work fine. However,
the camel web console doesn't show up. When I navigate to the url, I just
get a blank page. Using the jersey SpringServlet as a servlet instead of a
listener seems to break the interface.
Can any web console experts chime in as to why this might be happening? Can
the console work using the SpringServlet as a servlet as opposed to a
filter?
--
View this message in context:
http://old.nabble.com/Deploying-as-web-app-with-jetty-endpoint-tp28171746p28256874.html
Sent from the Camel - Users mailing list archive at Nabble.com.
