Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E608418E6F for ; Mon, 22 Feb 2016 13:30:04 +0000 (UTC) Received: (qmail 70807 invoked by uid 500); 22 Feb 2016 12:39:26 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 70341 invoked by uid 500); 22 Feb 2016 12:39:23 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 68445 invoked by uid 99); 22 Feb 2016 12:32:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2016 12:32:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 276652C1F58 for ; Mon, 22 Feb 2016 12:32:18 +0000 (UTC) Date: Mon, 22 Feb 2016 12:32:18 +0000 (UTC) From: "Romain Manni-Bucau (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-6787) not sufficient WadlGenerator presence detection MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156838#comment-15156838 ] Romain Manni-Bucau commented on CXF-6787: ----------------------------------------- [~sergey_beryozkin] checking null is ok for me. Thanks! > 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 > > 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 (v6.3.4#6332)