Colm O hEigeartaigh closed CXF-6787.

> not sufficient WadlGenerator presence detection
> -----------------------------------------------
>                 Key: CXF-6787
>                 URL: https://issues.apache.org/jira/browse/CXF-6787
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.0.3, 3.1.4
>            Reporter: Romain Manni-Bucau
>            Assignee: Sergey Beryozkin
>             Fix For: 3.1.6, 3.0.9, 3.2.0
> 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

This message was sent by Atlassian JIRA

Reply via email to