Critical Description
When the public class WSDL2Java is used two times from the same process and with the same path to the wsdl file, the generated files are the same both times even if the content of the file at the wsdl file path has changed so it should result in different output. It seems like CXF is caching the content of the WSDL somewhere and just reads from the cache the second time WSDL2Java is called. If the path is different from all paths that have previously been used with WSDL2Java the file is correctly read from disk. A maven project that can be used to reproduce the behavior will be attached to this bug.
This is critical for us since our application can call WSDL2Java many times during it's life time and we don't want files to be cached somewhere between the calls so that our application leaks memory and so we get unexpected results. If we just knew how to clear all caches between the calls then that would be a good enough workaround for us. This problem did not exist in CXF version 2.0.6.