The update only updates the bundle, leaving bundles connected to the "old" bundle still intact. So actually you should not only refresh 123, which only does the resolving of bundle 123, you should also do a refresh on the "importing" bundle, at this point the cxf-core bundle, cause this one didn't get the "news" about a bundle update.
Same applies to camel, in case you update bundles containing camel routes you need to refresh / re-wire the camel bundle to the newly available camel routes. regards, Achim 2014-05-28 1:43 GMT+02:00 Scott Carr <[email protected]>: > Try 'update 123' instead. I believe refresh just refreshes configuration, > I don't think it touches updated bundles. > > > On 05/27/2014 06:02 PM, asookazian2 wrote: > >> I have an existing WAR mega-bundle (WAB). I run the following cmds: >> >> update 123 >> refresh 123 >> >> I refresh the WSDL page in my browser but I notice that the change I'm >> expecting is not there. >> >> I halt then start karaf, then refresh the WSDL and the changes have been >> affected. >> >> When does CXF/karaf regenerate the WSDL? Must I bounce karaf? thx. >> >> >> >> -- >> View this message in context: http://karaf.922171.n3.nabble. >> com/CXF-regenerating-a-WSDL-tp4033295.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > -- 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
