Hi, just to make sure you don't go after a red herring in your code. Did you check with the latest 3.0.2-SNAPSHOT? Can't pin-point it down to a probable cause but it might be an issue with a newer version of Pax Web.
regards, Achim 2014-09-17 13:34 GMT+02:00 F.Aubele <[email protected]>: > Yeah, i did it with and without arguments. With argument shows the > behaviour > i described in my initial post (adding new servlets and showing old servlet > as undeployed). > Without arguments changes nothing, servlets stay listed in deployed and in > undeployed state. > > The servlet deployment behaviour was just the same (not removing/updating > servlets), sorry if i did not express my self accurately enough. > > It is not really bad, just unnerving me, i will try to find out what is > wrong, obviously it must be something in my code, since it seems no one > else > ever had this problem. > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Karaf-3-0-1-Problem-with-Servlets-using-DS-tp4035323p4035344.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Software Architect / Project Manager / Scrum Master
