[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430240#comment-15430240
]
ASF GitHub Bot commented on CXF-6740:
-
Github user splatch commented on the issue:
https://github.com/apache/cxf/pull/160
Indeed, this binds cxf more to swagger than relying only on swagger option,
however this one offered consistency with Swagger approach. By this way we
could also bind lifecycle and flush swagger objects from servlet context when
endpoint goes down. Currently we can't do that with swagger bazed approach, for
that we need to control also ServletContext attributes.
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7011) same method signature needs to be added in Continuation
[ https://issues.apache.org/jira/browse/CXF-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430469#comment-15430469 ] Sergey Beryozkin commented on CXF-7011: --- Hi, sorry I did not follow closely the way you applied the fix at the Camel side earlier. As I said we can consider adding some more specific Continuation code if that can help - but hope you agree with my explanation of why isResumed is set to 'true' after the timeout. (JettyContinuationWrapper has always been setting isResumed to true in its onTimeout). I'll keep this issue open for now in case you have more ideas on how to enhance the CXF continuation code thanks > same method signature needs to be added in Continuation > --- > > Key: CXF-7011 > URL: https://issues.apache.org/jira/browse/CXF-7011 > Project: CXF > Issue Type: Sub-task > Components: Transports >Affects Versions: 3.1.7 >Reporter: onder sezgin > Fix For: 3.2.0 > > > As this method requires access over Continuation interface this should be > provided and other implementations like transport-jms and transport-http with > default implementation and transport-http-jetty with real implemenration > should be provided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430522#comment-15430522
]
Sergey Beryozkin edited comment on CXF-6740 at 8/22/16 10:28 AM:
-
Hey Lukasz, Andriy
I wonder if we even can combine multiple approaches here, but I'd like to
understand better, setting some opaque id seems straightforward too, for
example, instead of
{code:xml}
{code}
we can simplify and do
{code:xml}
{code}
and then in Swagger2Feature - simply have it represented as both
"swagger.config.id" & "swagger.scanner.id".
Lukasz, do we also have to set Swagger2 feature 'basePath' ?
So it looks like an option which is worth supporting.
Andriy, in the demo you have 2 CXFServlets (each servlet has a 'basePath' set
to a CXF servlet URL pattern and a usePathBasedConfig), how would a Spring
configuration look like if we have a single CXFServlet and 2 jaxrs endpoints ?
Thanks, Sergey
was (Author: sergey_beryozkin):
Hey Lukasz, Andriy
I wonder if we even can combine multiple approaches here, but I'd like to
understand better, setting some opaque id seems straightforward too, for
example, instead of
{code:xml}
{code}
we can simplify and do
and then in Swagger2Feature - simply have it represented as both
"swagger.config.id" & "swagger.scanner.id".
Lukasz, do we also have to set Swagger2 feature 'basePath' ?
So it looks like an option which is worth supporting.
Andriy, in the demo you have 2 CXFServlets (each servlet has a 'basePath' set
to a CXF servlet URL pattern and a usePathBasedConfig), how would a Spring
configuration look like if we have a single CXFServlet and 2 jaxrs endpoints ?
Thanks, Sergey
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430522#comment-15430522
]
Sergey Beryozkin commented on CXF-6740:
---
Hey Lukasz, Andriy
I wonder if we even can combine multiple approaches here, but I'd like to
understand better, setting some opaque id seems straightforward too, for
example, instead of
{code:xml}
{code}
we can simplify and do
and then in Swagger2Feature - simply have it represented as both
"swagger.config.id" & "swagger.scanner.id".
Lukasz, do we also have to set Swagger2 feature 'basePath' ?
So it looks like an option which is worth supporting.
Andriy, in the demo you have 2 CXFServlets (each servlet has a 'basePath' set
to a CXF servlet URL pattern and a usePathBasedConfig), how would a Spring
configuration look like if we have a single CXFServlet and 2 jaxrs endpoints ?
Thanks, Sergey
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430567#comment-15430567
]
Łukasz Dywicki commented on CXF-6740:
-
[~sergey_beryozkin] There is no need to set basepath when context/scanner is is
set, however it is still necessary to generate valid descriptor which could be
used by swagger-ui. These two solutions are quite similar because they affect
attribute name used to cache swagger instance.
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430602#comment-15430602
]
Sergey Beryozkin commented on CXF-6740:
---
Hi, we've discussed it further with Lukasz and Lukasz agrees that updating to
Swagger 1.5.10 (with useBasePathConfig) resolves this issue, so Andriy, please
resolve it for 3.1.8/3.2.0 :-) (FYI I merged it to 3.1.8 too)
Lukasz has more ideas on how to optimize and improve few things like trying to
get a basePath auto-calculated and also controlling the cached Swagger
instances which we can look at separately
thanks
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430636#comment-15430636
]
Andriy Redko commented on CXF-6740:
---
Hey [~sergey_beryozkin], [~splatch]
Right, those two approaches are very similar. The 'basePath'-based one does
implicit Swagger IDs manipulation (scanner / config / ...) by making base path
a part of identifier (it triggers when {code:java}usePathBasedConfig{code} is
set). So I think in this regards, we could make this property *true* by default
and cover quite a large number of collisions (there is no need to set Swagger
IDs). However, if I understand [~splatch] correctly, Swagger caching mechanism
causing the issues when endpoints are loaded / unloaded dynamically (like in
OSGi), in this case Swagger still exposes the API specs even if there are no
running endpoints, the fix for this ticket does not address the issue yet but
[~splatch] has a PR.
Regarding your question, [~sergey_beryozkin], for Spring-based configuration
with one CXF servlet we would need to have two JAXRSFactoryBean instances. In
this case the *basePath* will be taken from there.
Thanks.
Best Regards,
Andriy Redko
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430641#comment-15430641
]
ASF GitHub Bot commented on CXF-6740:
-
Github user splatch commented on the issue:
https://github.com/apache/cxf/pull/160
Closing this PR as agreed in JIRA.
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430642#comment-15430642
]
ASF GitHub Bot commented on CXF-6740:
-
Github user splatch closed the pull request at:
https://github.com/apache/cxf/pull/160
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430649#comment-15430649
]
Andriy Redko commented on CXF-6740:
---
Thanks a bunch, [~sergey_beryozkin], [~splatch]!
[~splatch] if you need my help with trying out your ideas, please let me know,
I would be happy to support you here. Thanks!
Best Regards,
Andriy Redko
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles
[
https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko resolved CXF-6740.
---
Resolution: Fixed
> Collision by Swagger2Feature in two OSGI bundles
> -
>
> Key: CXF-6740
> URL: https://issues.apache.org/jira/browse/CXF-6740
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 3.1.4
> Environment: Apache Karaf 4.0.2
>Reporter: Andre Schlegel
>Assignee: Andriy Redko
> Fix For: 3.2.0, 3.1.8
>
> Attachments: 0001-temporary-work-for-cxf-6740-take-2.patch,
> 0001-temporary-work-for-cxf-6740.patch, CXF-6740-Collision-by-Swagger.patch
>
>
> I have two separate bundles in my karaf, which are using cxf with the
> swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both
> bundles working fine. But I got on both swagger-URL the same swagger-File
> (both for the monitor endpoints).
> I'm using the blueprint for swagger2feature configuration and annotation for
> the endpoints.
> core bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.core.resource.AuthenticationResource" />
> class="de.virtimo.bpc.core.resource.Configuration" />
>
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Monitor Bundle
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:cxf="http://cxf.apache.org/blueprint/core";
>xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>http://cxf.apache.org/blueprint/core
> http://cxf.apache.org/schemas/blueprint/core.xsd
>http://cxf.apache.org/jaxrs
> http://cxf.apache.org/schemas/blueprint/jaxrs.xsd";>
>
> class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" />
>
> class="de.virtimo.bpc.module.monitor.resource.Monitor" />
>
> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
> Center"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json
> and /cxf/bpc-monitor/swagger.json
> Anyone suggestion how to handle this scenario?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6904) Unable to read swagger annotations if the file is in another osgi bundle
[ https://issues.apache.org/jira/browse/CXF-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430683#comment-15430683 ] Sergey Beryozkin commented on CXF-6904: --- Christian, can you verify a fix please with CXF 3.1.8-SNAPSHOT ? Have Swagger2Feature 'scan' property disabled and it should be sufficient thanks > Unable to read swagger annotations if the file is in another osgi bundle > > > Key: CXF-6904 > URL: https://issues.apache.org/jira/browse/CXF-6904 > Project: CXF > Issue Type: Bug > Components: JAX-RS, OSGi >Reporter: Christian Lutz > > I created a simple example to reproduce the error. > https://github.com/ChristianLutz/cxf-swagger-osgi-bug > = > JAX-RS Swagger2Feature OSGI Issue > = > This example is based on the code from > https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jax_rs/description_swagger2_osgi > How to reproduce the issue: > mvn install (on the example) > bin/karaf (I used the current karaf 4.0.5) > > on karaf@root()> > feature:repo-add cxf 3.1.6 > feature:install cxf-rs-description-swagger2 > install mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-base/2.6.5 > install mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-json-provider/2.6.5 > install -s mvn:de.kreeloo/cxf-swagger2-osgi-api/1.0.0 > install -s mvn:de.kreeloo/cxf-swagger2-osgi-impl/1.0.0 > > It may happen that one component is complaining about a missing guava class > even if you provided it before. All you have todo is copy guava-18.jar into > your deploy folder. I think this is a karaf bug. I have to create a ticket > for. After you place the guava file into your deploy folder and type list, > all bundles should be active. > Now open your web browser and type: > http://localhost:8181/cxf/swaggerSample/swagger.json > And all you see is the swagger header. > > I guess the problem is the ClasspathHelper.class from org.reflections it > looks like that this one is not able to access the osgi component. > > The behavior is similar to this error description: > > http://cxf.547215.n5.nabble.com/Swagger2Feature-via-blueprint-config-does-not-produce-the-expected-results-td5761841.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-5663) IllegalStateException using AsyncHTTPConduit
[
https://issues.apache.org/jira/browse/CXF-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430904#comment-15430904
]
Christoph Hümbert commented on CXF-5663:
Hello,
I am facing the same problem when using Apache CXF 3.1.7. I already changed the
HttpCore (4.4.4 > 4.4.5) but the result is the same. The following demo code
shows how I parametrized and that code is working in general beside that
exception.
{code:java}
SOAPMessage requestMessage = null;
MessageFactory mf;
try {
mf = MessageFactory.newInstance(jaxWsProtocol);
requestMessage = mf.createMessage(null, new
ByteArrayInputStream(requestMsg.getBytes("UTF-8")));
} catch (SOAPException e) { ...
} catch (UnsupportedEncodingException e) { ...
} catch (IOException e) {...}
SOAPMessage responseMessage = null;
DispatchImpl dispatchCxf = null;
if(requestMsg != null) {
Service service = Service.create(serviceQName);
service.addPort(portQName, bindingType, endpointUrl);
Dispatch dispatch = service.createDispatch(portQName,
SOAPMessage.class, Service.Mode.MESSAGE);
dispatchCxf = (DispatchImpl)dispatch;
Client client = dispatchCxf.getClient();
HTTPConduit conduit = (HTTPConduit) client.getConduit();
HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy();
httpClientPolicy.setAllowChunking(Boolean.FALSE);
httpClientPolicy.setAutoRedirect(Boolean.TRUE);
httpClientPolicy.setAsyncExecuteTimeout(3L);
httpClientPolicy.setReceiveTimeout(0);
httpClientPolicy.setConnectionTimeout(0);
//httpClientPolicy.setAsyncExecuteTimeoutRejection(true); //
orignal: false
conduit.setClient(httpClientPolicy);
Bus bus = client.getBus();
bus.setProperty("use.async.http.conduit", Boolean.TRUE);
bus.setProperty("org.apache.cxf.transport.http.async.SO_LINGER", 60);
Map rc = dispatch.getRequestContext();
rc.put("use.async.http.conduit", Boolean.TRUE);
rc.put("thread.local.request.context", Boolean.TRUE);
if(credentials != null) {
rc.put(Credentials.class.getName(), credentials);
}
if(soapAction != null){
rc.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
rc.put(BindingProvider.SOAPACTION_URI_PROPERTY, soapAction);
}
try {
responseMessage = dispatchCxf.invoke(requestMessage);
} catch (WebServiceException e) {
if(e.getCause().getClass().equals(IOException.class)) {
if(e.getCause().getMessage().startsWith("Authorization loop
detected on Conduit")) {
System.out.println("Authentication failed: Wrong credentials: "
+ e.getCause().getMessage());
}
} else if(e.getCause().getClass().equals(SocketTimeoutException.class))
{
System.out.println(e.getCause().getMessage());
} else { System.out.println(e.getCause().getMessage());}
throw new WsServiceException(e.getCause().getMessage());
} finally {
try {
dispatchCxf.close();
} catch (IOException e) { /* ignore */ }
}
}
{code}
I created a JUnit test which creates multiple objects with my implementation
by using the Callable interface. The DTOs contain connection information,
credentials,etc. So I have 3 different web services with different credentials
but on the same host. In this test I created 3000 request which will run in
thread pool. Sometimes it happened but sometimes not. When use my
implementation in Apache Tomcat the this exceptions occurs very quickly.
{code:java}
@Test
public void testWithCallable() {
int numberOfHandlers = 3;
SoapRequestHandler handler1 = new SoapRequestHandler(dto1);
...
Set> set = new HashSet>();
ExecutorService pool = Executors.newFixedThreadPool(50);
int numberOfCalls = 1000;
for(int i = 0; i < numberOfCalls; i++) {
TestSoapServiceCallableRunner run1 = new
TestSoapServiceCallableRunner(handler1);
set.add(pool.submit(run1));
TestSoapServiceCallableRunner run2 = new
TestSoapServiceCallableRunner(handler2);
set.add(pool.submit(run2));
TestSoapServiceCallableRunner run3 = new
TestSoapServiceCallableRunner(handler3);
set.add(pool.submit(run3));
}
for (Future afuture : set) {
OutputStream os;
try {
os = verifySoapResult(afuture.get()); IOUtils.closeQuietly(os);
} catch (InterruptedException e) {...
} catch (ExecutionException e) {... }
}
assertEquals(numberOfCalls * numberOfHandlers, set.size());
}
{code}
Workarounds like retrying often run in the same exception again hence it makes
no sense to use it. I try to dive deeper into the topic...
My system: Fedora 24; i5. Ubuntu 14.04/16.04; OpenJDk 1.8.0_101
> IllegalStateException using AsyncHTTPConduit
>
>
> Key: CXF-56
[jira] [Created] (CXF-7018) Cannot load WSDL behind proxy with Dynamic client
Logan created CXF-7018:
--
Summary: Cannot load WSDL behind proxy with Dynamic client
Key: CXF-7018
URL: https://issues.apache.org/jira/browse/CXF-7018
Project: CXF
Issue Type: Bug
Reporter: Logan
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7018) Cannot load WSDL behind proxy with Dynamic client
[
https://issues.apache.org/jira/browse/CXF-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Logan updated CXF-7018:
---
Description:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through
was:From what I understand we setting proxy settings on HttpConduit after we
created Client as described here (
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
) However with Dynamic Client I need to load WSDL which is behind a proxy.
Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
creating client and there is no way I set HttpConduit settings before WSDL url
is called
> Cannot load WSDL behind proxy with Dynamic client
> -
>
> Key: CXF-7018
> URL: https://issues.apache.org/jira/browse/CXF-7018
> Project: CXF
> Issue Type: Bug
>Reporter: Logan
>
> From what I understand we setting proxy settings on HttpConduit after we
> created Client as described here (
> http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
> Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
> creating client and there is no way I set HttpConduit settings before WSDL
> url is called.
> Note I am not using spring but rather through
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7018) Cannot load WSDL behind proxy with Dynamic client
[
https://issues.apache.org/jira/browse/CXF-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Logan updated CXF-7018:
---
Description:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
here ( http://cxf.apache.org/docs/dynamic-clients.html)
was:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through
> Cannot load WSDL behind proxy with Dynamic client
> -
>
> Key: CXF-7018
> URL: https://issues.apache.org/jira/browse/CXF-7018
> Project: CXF
> Issue Type: Bug
>Reporter: Logan
>
> From what I understand we setting proxy settings on HttpConduit after we
> created Client as described here (
> http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
> Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
> creating client and there is no way I set HttpConduit settings before WSDL
> url is called.
> Note I am not using spring but rather through programming just like described
> here ( http://cxf.apache.org/docs/dynamic-clients.html)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7018) Cannot load WSDL behind proxy with Dynamic client
[
https://issues.apache.org/jira/browse/CXF-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Logan updated CXF-7018:
---
Description:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
[here|http://cxf.apache.org/docs/dynamic-clients.html]
was:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
here ( http://cxf.apache.org/docs/dynamic-clients.html)
> Cannot load WSDL behind proxy with Dynamic client
> -
>
> Key: CXF-7018
> URL: https://issues.apache.org/jira/browse/CXF-7018
> Project: CXF
> Issue Type: Bug
>Reporter: Logan
>
> From what I understand we setting proxy settings on HttpConduit after we
> created Client as described here (
> http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
> Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
> creating client and there is no way I set HttpConduit settings before WSDL
> url is called.
> Note I am not using spring but rather through programming just like described
> [here|http://cxf.apache.org/docs/dynamic-clients.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7018) Cannot load WSDL behind proxy with Dynamic client
[
https://issues.apache.org/jira/browse/CXF-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Logan updated CXF-7018:
---
Description:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described
>[here|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient]
> However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
[here|http://cxf.apache.org/docs/dynamic-clients.html]
was:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described here (
>http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient
> ) However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
[here|http://cxf.apache.org/docs/dynamic-clients.html]
> Cannot load WSDL behind proxy with Dynamic client
> -
>
> Key: CXF-7018
> URL: https://issues.apache.org/jira/browse/CXF-7018
> Project: CXF
> Issue Type: Bug
>Reporter: Logan
>
> From what I understand we setting proxy settings on HttpConduit after we
> created Client as described
> [here|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient]
> However with Dynamic Client I need to load WSDL which is behind a proxy.
> Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
> creating client and there is no way I set HttpConduit settings before WSDL
> url is called.
> Note I am not using spring but rather through programming just like described
> [here|http://cxf.apache.org/docs/dynamic-clients.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7018) Cannot load WSDL behind proxy with Dynamic client
[
https://issues.apache.org/jira/browse/CXF-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Logan updated CXF-7018:
---
Description:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described
>[here|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient]
> However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("https://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
[here|http://cxf.apache.org/docs/dynamic-clients.html]
was:
>From what I understand we setting proxy settings on HttpConduit after we
>created Client as described
>[here|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient]
> However with Dynamic Client I need to load WSDL which is behind a proxy.
>Right now DynamicClientFactory.createClient("http://?WSDL";) fails before
>creating client and there is no way I set HttpConduit settings before WSDL url
>is called.
Note I am not using spring but rather through programming just like described
[here|http://cxf.apache.org/docs/dynamic-clients.html]
> Cannot load WSDL behind proxy with Dynamic client
> -
>
> Key: CXF-7018
> URL: https://issues.apache.org/jira/browse/CXF-7018
> Project: CXF
> Issue Type: Bug
>Reporter: Logan
>
> From what I understand we setting proxy settings on HttpConduit after we
> created Client as described
> [here|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient]
> However with Dynamic Client I need to load WSDL which is behind a proxy.
> Right now DynamicClientFactory.createClient("https://?WSDL";) fails before
> creating client and there is no way I set HttpConduit settings before WSDL
> url is called.
> Note I am not using spring but rather through programming just like described
> [here|http://cxf.apache.org/docs/dynamic-clients.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
