Camel is light-weight so you should easily be able to deploy 50 WARs in Tomcat.
You can also consider grouping related routes into a single WAR and then lets say have 20 WARs instead. Putting JARs in the lib of tomcat is not recommended as you may have classloading issues. Instead keeping all JARs in the WAR is recommended as they are all within the same classloading scheme. On the other side having this kind of modularity and not the need to duplicate libraries as you would need to with a WAR file is what OSGi is capable of. That would allow all 50 routes to share Camel and other 3rd party frameworks and thus reduce memory footprint (less classes to be loaded in memory). However currently WAR is a wel proven and easy way of deploying apps. Thats a great choice. -- View this message in context: http://camel.465427.n5.nabble.com/Deploying-Routes-as-WAR-files-tp3350610p3350910.html Sent from the Camel - Users mailing list archive at Nabble.com.
