Could you look in system test NoSpringServletClientTest.testStartAndStopServer() and analyse what is different in your case? Any chance to reproduce it on simple example?
Cheers, Andrei. -----Original Message----- From: Filipe Amaral [mailto:[email protected]] Sent: Donnerstag, 15. November 2012 15:12 To: [email protected] Subject: After upgrading CXF from 2.6.1 to 2.7.0 due to CXF-4407 bug a new problem arises Hi there My first post on the list so bare with me :) I'll just create a succinct description of the environment and problem. We, at our project, are at the moment providing two different web-services through servlets in an OSGi environment deployed in JBoss. One is based on contract-first through WSDL and the other on code-first through a Java interface. Both of them are published using JaxWsServerFactoryBean and all goes well. We recently had to develop a feature to enable a GUI user to stop and start, individually or not, these web-services, as well as to start them again, but we were using CXF 2.6.1. which suffered from CXF-4407 bug. After upgrading to 2.7.0 the bug depicted behavior disappeared and the service is shown in soap services page again after a start(), but if a request is made or if we try to access the published wsdl we get the following warning on our app console: 10:43:07,383 WARN [ServletController] Can't find the the request for [hidden url]'s Observer I've replaced the web-service url for [hidden url] due to company restrictions. In the ?wsdl page simply says "No service was found." I've run a few debugs inside CXF sources and I can see that when ServerLifeCycleManagerImpl.startServer() is executed the cycled ServerLifeCycleListener listeners list includes a MEXServerListener, a CacheCleanupListener and a ManagedEndpoint. This last, for my surprise, has a JaxWsImplementorInfo that points to the other web-service and not for the one i'm starting (is this normal?)... After some stops and starts this listener list starts to be filled only with a MEXServerListener and CacheCleanupListener. I'm getting an incoherent behavior on this and I can't figure out what the problem is. Can anyone help? If more info is needed on this, please ask. I'll try to fulfill the feature request by destroying the web-service and creating him again instead of just using stop() and start(), meanwhile I figure out if this is a CXF bug or something I'm doing wrong when creating the services with JaxWsServerFactoryBean. Best Regards -- View this message in context: http://cxf.547215.n5.nabble.com/After-upgrading-CXF-from-2-6-1-to-2-7-0-due-to-CXF-4407-bug-a-new-problem-arises-tp5718507.html Sent from the cxf-user mailing list archive at Nabble.com.
