Just a side note. There should be a new option in Camel 2.0 - matchOnUriPrefix that can allow you to match wildcard URIs.
On Tue, Apr 7, 2009 at 9:28 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Hi, > > I think it depends on your requirement. > > If you have lots of static resource or you need to set the http server's > port and context path at the deployment time, packaging the Camel > application into a WAR is your best choice. > > If your Camel application is under developing, or you just want to run > it from a simple Java Main, you may using a stand-alone Camel > application as a web server. > > Willem > > huntc wrote: >> Hey there, >> >> Does anyone have thoughts on using a stand-alone Camel application as a web >> server, or do people generally prefer packaging the Camel application in a >> WAR file? >> >> My use-case is that I have a web service provided by Camel and using the >> jetty component. This works nicely. However I want to serve up some static >> resources associated with the web service. The only way I have found to do >> this is by creating a producer for every static resource to be provided >> e.g.: >> >> my web service: >> >> jetty:http://0.0.0.0:9080/GPSTrackerCollectionService/GPSTrackerCollection/gpsTrackers/GPSTracker/history >> >> one (of the many) associated resources: >> >> jetty:http://0.0.0.0:9080/GPSTrackerCollectionService/GPSTrackerCollection/gpsTrackers/GPSTracker/styles.kml >> >> Kind regards, >> Christopher > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
