If that is the case, that means CXF is not the problem, it is some
deployment option of Weblogic (i.e., you would have the same problem
with *any* web application deployed on it, web services or graphical web
app.)
What I would do is skeletonize your web application (remove CXF and
everything
Everything I can think of really has nothing to do with CXF.
1) Timestamp on the war/ear is from a computer that has it's clock set
wrong. Basically, if the war is built in the future according to the
machine running weblogic, it might think the war has changed when it
really hasn't.
2)
I have not worked with this type of problem before. Possible guesses:
1.) Anything in our WebLogic docs[1] that may be relevant for your
problem?
2.) We have two types of configuration for web services--via a
cxf-servlet.xml file and directly through Spring configuration[2]. If
you try the
org.apache.cxf.transport.servlet.CXFServlet
loadAdditionalConfig
INFO: Build endpoints from config-location: /WEB-INF/cxf-servlet.xml
--
View this message in context:
http://www.nabble.com/CXF-Service-End-Points-reloaded-every-time-in-WebLogic-tp16516335p16516335.html
Sent from the cxf-user mailing list archive at Nabble.com.
