2009/7/8 James Strachan <james.strac...@gmail.com>: > 2009/7/8 Claus Ibsen <claus.ib...@gmail.com>: >> On Wed, Jul 8, 2009 at 2:44 PM, Claus Ibsen<claus.ib...@gmail.com> wrote: >>> On Tue, Jul 7, 2009 at 4:45 AM, ewhauser<ewhau...@gmail.com> wrote: >>>> >>>> I'm trying to figure out the best way to package the functionality in the >>>> camel web console in my apps. Is the web console designed to be embedded >>>> in >>>> a Camel application? Or should the camel-web project be used as a template >>>> for a Camel WAR app? >>> Hi >>> >>> At present time you gotta copy all the camel-web/src/main/web files >>> into your own web application to be able to use >>> the web console to browse your own camel application. >>> >>> It does not have any remote management functionallity - eg it must be >>> collocated with your web app. >> >> Ah I was told if you use maven then just depend on camel-web in your pom.xml >> >> Then maven does all the hard parts of merging all the src/main/web files. > > > There's an example in the sandbox > https://svn.apache.org/repos/asf/camel/sandbox/components/camel-activemq-web/ > > which creates an extension of camel-web, adding new dependencies and > changing the spring configuration. > > if you look at the pom > https://svn.apache.org/repos/asf/camel/sandbox/components/camel-activemq-web/pom.xml > > the trick is just depending on the camel-web war in your war's pom.xml. > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-web</artifactId> > <version>2.0</version> > <type>war</type> > <scope>runtime</scope> > </dependency> > > You can then override any file locally; whether its parts of the > default views or the spring XML or adding new views or your own > servlets and whatnot. > > We're using Jersey as a filter; so you should be able to mix camel-web > with any servlet/framework to do other things (see the web.xml for how > we exclude bits of the URI space from Jersey to work with regular > static resources & JSPs etc). > > But if you just basically want the camel-web console/REST API with > your own routes/components it should just work out of the box.
BTW there's the camel-archetype-war which you can use to create a sample project which reuses the camel-web console & REST API to deploy your routes. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
