Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
From: deki <git@git.apache.org>
To: dev@cxf.apache.org
Reply-To: dev@cxf.apache.org
Message-ID: <git-pr-236-cxf@git.apache.org>
Subject: [GitHub] cxf pull request #236: CXF-7137: extended unittest to show non working secur...
Content-Type: text/plain
Date: Mon, 13 Feb 2017 12:00:18 +0000 (UTC)
archived-at: Mon, 13 Feb 2017 12:00:20 -0000

GitHub user deki opened a pull request:

    https://github.com/apache/cxf/pull/236

    CXF-7137: extended unittest to show non working security definitions

    I've extended the unittest to show that the implementation from CXF-7137 isn't working at the moment. While contact is part of the BeanConfig and correctly serialized, the SecurityDefinitions are not shown in the swagger.json as Swagger's BaseApiListingResource handles only the attributes from BeanConfig.
    
    I'm not sure if this can be fixed without changes in Swagger, please have a look.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/deki/cxf CXF-7137

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/236.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #236
    
----
commit 9f196443a50c45014ff08a8198cc7fb95532951d
Author: Dennis Kieselhorst <mail@dekies.de>
Date:   2017-02-13T11:49:57Z

    CXF-7137: extended unittest for contact info (working) and security definitions (not working)

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---