[CXF-6787] not sufficient WadlGenerator presence detection

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.3, 3.1.4
• Fix Version/s: 3.1.6, 3.0.9, 3.2.0
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Romain Manni-Bucau
• Created: 18/Feb/16 13:46
• Updated: 14/Oct/16 14:13
• Resolved: 22/Feb/16 13:03

Description

org.apache.cxf.jaxrs.provider.ServerProviderFactory#createWadlGenerator do a loadClass to check WadlGenerator is there but if it is there in a upper classloader and cxf in a lower classloader then it will get instantiated but will not work (cause JAXRSUtil.currentmessage() will be loaded in both classloaders and will not be shared if the lower classloader is a webapp one).

Would be great to check once loaded the instance is actually usable before adding it.

This pattern is used in few other places - I suspect management part as well since I got the issue too - but this one broke archiva in tomee for instance.

Side note: reported the versions I tested with but I guess most of CXF versions are affected