Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Sun, 2 Apr 2017 14:44:41 +0000 (UTC)
From: "Andrei Shakirin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12996933.1471003895000.186464.1491144281761@Atlassian.JIRA>
In-Reply-To: <JIRA.12996933.1471003895000@Atlassian.JIRA>
References: <JIRA.12996933.1471003895000@Atlassian.JIRA> <JIRA.12996933.1471003895763@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (CXF-7010) Swagger2Feature can not
 auto-link to SwaggerUi in OSGI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 02 Apr 2017 14:44:46 -0000


    [ https://issues.apache.org/jira/browse/CXF-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952709#comment-15952709 ] 

Andrei Shakirin edited comment on CXF-7010 at 4/2/17 2:44 PM:
--------------------------------------------------------------

Hi Sergey,

I have discovered one case in OSGi, where the default bus fix doesn't really solve the problem.
It happens, if jax-rs service initializes a jax-rs or jax-ws client proxy on startup and this client proxy is created not through the blueprint, but programmatically, for example using JAXRSClientFactory.
If such client is created before the registration of first blueprint jax-rs service or blueprint jax-rs client in OSGi, the BusFactory will be initialized with ExtensionManagerBus as default bus (instead BlueprintBus).
This ExtensionManagerBus wouldn't be used by WadlGeneratior and doesn't know about "wadl.service.description.available" property. 
As result the WADL links still wouldn't be shown in service list page.
Of course it is a bit "exotic" case, anyway the service page view will changed after migration on CXF 3.X.
I haven't a good idea how to fix it, perhaps introducing optional JVM property that always force WADL links. What do you think?

Regards,
Andrei.


was (Author: ashakirin):
Hi Sergey,

I have discovered one case in OSGi, where the default bus fix doesn't really solve the problem.
It happens, if jax-rs service initializes a jax-rs or jax-ws client proxy on startup and this client proxy is created not through the blueprint, but programmatically for example using JAXRSClientFactory.
If such client is created before the registration of first blueprint jax-rs service or blueprint jax-rs client in OSGi, the BusFactory will be initialized with ExtensionManagerBus as default bus (instead BlueprintBus).
This ExtensionManagerBus doesn't used by WadlGeneratior and doesn't know about "wadl.service.description.available" property. 
As result the WADL links still wouldn't be shown in service list page.
Of course it is a bit "exotic" case, anyway the service page view will changed after migration on CXF 3.X.
I haven't a good idea how to fix it, perhaps introducing optional JVM property that always force WADL links. What do you think?

Regards,
Andrei.


> Swagger2Feature can not auto-link to SwaggerUi in OSGI
> ------------------------------------------------------
>
>                 Key: CXF-7010
>                 URL: https://issues.apache.org/jira/browse/CXF-7010
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.1.7
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>             Fix For: 3.1.8, 3.2.0
>
>


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)