On Jul 31, 2007, at 10:47 AM, Jarek Gawor wrote:
I'm +1 on the testing this out. I seem to remember that a while ago I've had some problems with CXF when the <hidden-classes/> was actually enabled for Spring classes in the Jetty config but maybe it will work better now. See: http://www.mail-archive.com/[email protected]/msg41202.html. Please also run the testsuite/webservices-testsuite/jaxws-tests/jaxws-*/ tests to verify that everything works ok after the change.
OK. So, there are testsuite failures. I'm not seeing problems with other testing, however... I see why you removed the hidden-classes filter... Looks like we're in a bit of a Catch-22...
I assume restructuring the spring-based configuration of cxf is pretty disruptive/potentially error-prone? Looks like some apps which include Spring and use jaxws could run into the same type of catch-22. Their only option would be to include the same version of spring that's used by our cxf module...
--kevan
