If your war has been correctly registered it will also show up in the
web:list command output as Deployed, with a Web-ContextPath; and the
individual servlets will show in in the http:list command output. If they
are not visible then something fundamental is missing: perhaps you need to
install the "war" feature in Karaf, for example? ("feature:install war")BTW it is very unhelpful to write "it's not working" when for a couple of picojoules more effort you could write "I get 404 Not found" or whatever it is you get. As regards splitting up a big war, I would suggest try first to draw a boundary between the "servlet" code and the "services" it uses; you can then move all the non-webby code into a separate bundle. Having done that you may be able to see clear fault-lines in one or other bundle, e.g. the servlets clearly fall into two or three functional area which don't interact very much or some services are only used by one servlet. How easy it will be will depend very much on how big a mess the current code is: in my experience if a large body of code has been developed without regard to modularity then it will be one big mess. That being said, IMHO OSGi is far and away the best tool around for creating and sustaining modularity. Courage! -- View this message in context: http://karaf.922171.n3.nabble.com/Transform-a-big-WAR-project-in-OSGI-tp4034260p4034316.html Sent from the Karaf - User mailing list archive at Nabble.com.
