[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494840#comment-15494840
]
Andriy Redko commented on CXF-7045:
---
Hey Sergey,
Great, no problem! Yeah, exactly, for non-OSGi samples there are no issues. By
solution 3 you mean this one: *remove dependency="true" or use install="auto"*?
Thanks to Christian we could simplify it to just *remove dependency="true" for
com.fasterxml.jackson.jaxrs bundles only*. Yeah, it is still the option, right.
Thanks!
Best Regards,
Andriy Redko
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494495#comment-15494495
]
Sergey Beryozkin commented on CXF-7045:
---
Hey Andriy
Thanks for your patience, I think it is getting a bit clearer for me.
So, it appears to be an OSGI wiring issue, right, if, despite the dependency
graph change it is all working fine in non-OSGI ?
That solution 3 you mentioned - is still an option ?
Thanks. Sergey
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7059) ClientImpl.getBooleanValue() will return null for String values
[
https://issues.apache.org/jira/browse/CXF-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494226#comment-15494226
]
ASF GitHub Bot commented on CXF-7059:
-
GitHub user andymc12 opened a pull request:
https://github.com/apache/cxf/pull/171
CXF-7059 Update getBooleanValue to read String values
https://issues.apache.org/jira/browse/CXF-7059
Simple change to make getBooleanValue consistent with getIntValue, etc.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andymc12/cxf patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/171.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 #171
> ClientImpl.getBooleanValue() will return null for String values
> ---
>
> Key: CXF-7059
> URL: https://issues.apache.org/jira/browse/CXF-7059
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.7
>Reporter: Andy McCright
>Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The getBooleanValue(Object o) method looks like this:
> private static Boolean getBooleanValue(Object o) {
> return o instanceof Boolean ? (Boolean)o : o instanceof Boolean ?
> Boolean.valueOf(o.toString()) : null;
> }
> If o is not an instance of Boolean, it checks to see if it is a Boolean
> again. Instead, it should get to see if it is an instance of String like the
> getIntValue method:
> private static Integer getIntValue(Object o) {
> return o instanceof Integer ? (Integer)o : o instanceof String ?
> Integer.valueOf(o.toString()) : null;
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-7059) ClientImpl.getBooleanValue() will return null for String values
Andy McCright created CXF-7059:
--
Summary: ClientImpl.getBooleanValue() will return null for String
values
Key: CXF-7059
URL: https://issues.apache.org/jira/browse/CXF-7059
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 3.1.7
Reporter: Andy McCright
Priority: Minor
The getBooleanValue(Object o) method looks like this:
private static Boolean getBooleanValue(Object o) {
return o instanceof Boolean ? (Boolean)o : o instanceof Boolean ?
Boolean.valueOf(o.toString()) : null;
}
If o is not an instance of Boolean, it checks to see if it is a Boolean again.
Instead, it should get to see if it is an instance of String like the
getIntValue method:
private static Integer getIntValue(Object o) {
return o instanceof Integer ? (Integer)o : o instanceof String ?
Integer.valueOf(o.toString()) : null;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493952#comment-15493952
]
Andriy Redko edited comment on CXF-7045 at 9/15/16 5:06 PM:
Hey Sergey,
No problem. So here is the thing (Swagger 2 OSGi sample):
- yes, you see the usage of JAX-RS provider in the sample (which is part of
com.fasterxml.jackson.jaxrs artifacts)
- yes, cxf-rt-rs-service-description-swagger lists two
com.fasterxml.jackson.jaxrs artifacts in the feature.xml definition
- however, they won't be installed by Karaf, because our Swagger 2 integration
does not depend on any class from com.fasterxml.jackson.jaxrs artifacts (the
respective bundles are marked with dependency="true" attribute)
- but our Swagger 2 OSGi sample uses JacksonJsonProvider so when it is being
installed into Karaf container, two com.fasterxml.jackson.jaxrs have to be
installed manually as well
As Aki mention, previous version of Swagger had a dependency to
com.fasterxml.jackson.jaxrs and as such, Karaf installed them as part of
cxf-rt-rs-service-description-swagger feature. In this case, our samples just
work, nothing to be done. Now, the dependency graph has changed and
com.fasterxml.jackson.jaxrs are resolved as a unused dependencies (and as such
skipped), so when we ask user to install sample application bundle,
com.fasterxml.jackson.jaxrs bundles are not present and have to be installed
manually :( Hope I included all the pieces ... :-) Please let me know if
something is still not clear.
Thanks!
Best Regards,
Andriy Redko
was (Author: reta):
Hey Sergey,
No problem. So here is the thing (Swagger 2 OSGi sample):
- yes, you see the usage of JAX-RS provider in the sample (which is part of
com.fasterxml.jackson.jaxrs artifacts)
- yes, cxf-rt-rs-service-description-swagger lists two
com.fasterxml.jackson.jaxrs artifacts in the feature.xml definition
- however, they won't be installed by Karaf, because our Swagger 2 integration
does not depend on any class from com.fasterxml.jackson.jaxrs artifacts (the
respective bundles are marked with dependency="true" attribute)
- but our Swagger 2 OSGi sample uses JacksonJsonProvider so when it is being
installed into Karaf container, two com.fasterxml.jackson.jaxrs have to be
installed manually as well
As Aki mention, previous version of Swagger had a dependency to
com.fasterxml.jackson.jaxrs and as such, Karaf installed them as part of
cxf-rt-rs-service-description-swagger feature. In this case, our samples just
work, nothing to be done. Now, the dependency graph has changed and
com.fasterxml.jackson.jaxrs are resolved as a dependencies, so when we ask user
to install sample application bundle, com.fasterxml.jackson.jaxrs bundles are
not present and have to be installed manually :( Hope I included all the pieces
... :-) Please let me know if something is still not clear.
Thanks!
Best Regards,
Andriy Redko
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493952#comment-15493952
]
Andriy Redko commented on CXF-7045:
---
Hey Sergey,
No problem. So here is the thing (Swagger 2 OSGi sample):
- yes, you see the usage of JAX-RS provider in the sample (which is part of
com.fasterxml.jackson.jaxrs artifacts)
- yes, cxf-rt-rs-service-description-swagger lists two
com.fasterxml.jackson.jaxrs artifacts in the feature.xml definition
- however, they won't be installed by Karaf, because our Swagger 2 integration
does not depend on any class from com.fasterxml.jackson.jaxrs artifacts (the
respective bundles are marked with dependency="true" attribute)
- but our Swagger 2 OSGi sample uses JacksonJsonProvider so when it is being
installed into Karaf container, two com.fasterxml.jackson.jaxrs have to be
installed manually as well
As Aki mention, previous version of Swagger had a dependency to
com.fasterxml.jackson.jaxrs and as such, Karaf installed them as part of
cxf-rt-rs-service-description-swagger feature. In this case, our samples just
work, nothing to be done. Now, the dependency graph has changed and
com.fasterxml.jackson.jaxrs are resolved as a dependencies, so when we ask user
to install sample application bundle, com.fasterxml.jackson.jaxrs bundles are
not present and have to be installed manually :( Hope I included all the pieces
... :-) Please let me know if something is still not clear.
Thanks!
Best Regards,
Andriy Redko
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493754#comment-15493754
]
Sergey Beryozkin commented on CXF-7045:
---
Hey Andriy, I'm feeling terribly slow today :-), so stay with me please. I've
just looked at the CXF source and I saw these Jackson JAX-RS provider in the
list - so what I've missed so far is why having it there is not enough and why
users have to install it manually ?
Thanks, Sergey
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493728#comment-15493728
]
Andriy Redko commented on CXF-7045:
---
Hi Sergey,
That's right, that dependency is not here anymore for
cxf-rt-rs-service-description-swagger feature.
Rather, those become the dependency for sample applications only and as such,
have to be installed manually (before we installed them as part of
cxf-rt-rs-service-description-swagger feature).
Does it make things clearer a bit?
Thanks!
Best Regards,
Andriy Redko
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493599#comment-15493599
]
Sergey Beryozkin commented on CXF-7045:
---
Hi Andriy
I'm not understanding something. You and Aki are saying that 'that dependency'
is not there any more.
But non-OSGI demo does show these Jackson providers being pulled in.
I'm not sure why listing these jackson providers is not sufficient...
Cheers, Sergey
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493259#comment-15493259
]
Andriy Redko commented on CXF-7045:
---
Hi [~sergey_beryozkin],
I think this is the right decision. No, we don't need
com.fasterxml.jackson.jaxrs.json;resolution:=optional in this case. We could
remove com.fasterxml.jackson.jaxrs from feature.xml
and update README for the sample project to ask the users to install two
com.fasterxml.jackson.jaxrs bundles manually (if they are not present in Karaf
container). Sounds good?
Thanks!
Best Regards,
Andriy Redko
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6617) InInterceptor throws WstxLazyException with PrettyLogging
[
https://issues.apache.org/jira/browse/CXF-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493131#comment-15493131
]
Dennis Kieselhorst commented on CXF-6617:
-
I think this should be resolved as duplicate of CXF-6554 and CXF-7044.
> InInterceptor throws WstxLazyException with PrettyLogging
> -
>
> Key: CXF-6617
> URL: https://issues.apache.org/jira/browse/CXF-6617
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.1.1
> Environment: Java 1.8,
> spring-boot 1.2.4
>Reporter: member sound
>Priority: Critical
>
> Having PrettyLogging enabled on InInterceptor, I'm getting the following
> exception lately.
> Is it possible that you could log the response even if an error occurs?
> Because it's hard to find the rootcause if no soap-xml is logged due to an
> error inside the pretty-print-logging.
> Maybe it's possible to create some fallback and log the response unformatted
> in case of parsing/formatting errors?
> Maybe related to: CXF-6554
> {code}
> 2015-09-29 16:07:44,082 WARN o.a.c.p.PhaseInterceptorChain: Interceptor for
> {http://TheService#{http://TheService}service has thrown exception, unwinding
> now
> org.apache.cxf.interceptor.Fault: [com.ctc.wstx.exc.WstxLazyException]
> Unexpected end of input block in entity reference
> at [row,col {unknown-source}]: [489,6]
> at
> org.apache.cxf.interceptor.LoggingInInterceptor.logInputStream(LoggingInInterceptor.java:225)
> ~[cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.interceptor.LoggingInInterceptor.logging(LoggingInInterceptor.java:159)
> ~[cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.interceptor.LoggingInInterceptor.handleMessage(LoggingInInterceptor.java:80)
> ~[cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1641)
> [cxf-rt-transports-http-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1532)
> [cxf-rt-transports-http-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1330)
> [cxf-rt-transports-http-3.1.1.jar:3.1.1]
> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
> [?:1.8.0_51]
> at
> org.apache.cxf.io.AbstractWrappedOutputStream.close(AbstractWrappedOutputStream.java:77)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.io.AbstractThresholdOutputStream.close(AbstractThresholdOutputStream.java:102)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:56)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:215)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:652)
> [cxf-rt-transports-http-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
> [cxf-core-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> [cxf-rt-frontend-simple-3.1.1.jar:3.1.1]
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
> [cxf-rt-frontend-jaxws-3.1.1.jar:3.1.1]
> at com.sun.proxy.$Proxy186.service(Unknown Source) [?:?]
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown
> Source) ~[?:?]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
[jira] [Commented] (CXF-6554) Exception thrown in LoggingInInterceptor
[
https://issues.apache.org/jira/browse/CXF-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493127#comment-15493127
]
Dennis Kieselhorst commented on CXF-6554:
-
Is this fixed by CXF-7044?
> Exception thrown in LoggingInInterceptor
>
>
> Key: CXF-6554
> URL: https://issues.apache.org/jira/browse/CXF-6554
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.7.17
>Reporter: Damon Horrell
>Priority: Minor
>
> An exception is thrown for some inbound messages when logging is enabled via:
>
>
>
> Overriding the default 65536 character limit fixes the problem:
>
>
>
>
> -
> Exception in thread "main" javax.xml.ws.soap.SOAPFaultException:
> [com.ctc.wstx.exc.WstxLazyException] Unexpected end of input block in entity
> reference
> at [row,col {unknown-source}]: [1017,49]
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:158)
> at $Proxy42.getDocumentById(Unknown Source)
> at
> nz.govt.moh.eps.proxy.PrescriptionServiceProxy.getDocumentById(PrescriptionServiceProxy.java:82)
> at nz.govt.moh.eps.client.EpsTestClient.main(EpsTestClient.java:45)
> Caused by: [com.ctc.wstx.exc.WstxLazyException]
> com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in entity
> reference
> at [row,col {unknown-source}]: [1017,49]
> at
> com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45)
> at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:728)
> at
> com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3678)
> at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:860)
> at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:748)
> at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:697)
> at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:621)
> at
> org.apache.cxf.interceptor.AbstractLoggingInterceptor.writePayload(AbstractLoggingInterceptor.java:164)
> at
> org.apache.cxf.interceptor.LoggingInInterceptor.logInputStream(LoggingInInterceptor.java:215)
> at
> org.apache.cxf.interceptor.LoggingInInterceptor.logging(LoggingInInterceptor.java:153)
> at
> org.apache.cxf.interceptor.LoggingInInterceptor.handleMessage(LoggingInInterceptor.java:79)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:849)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1632)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1520)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1318)
> at
> org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:56)
> at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:223)
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:633)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:572)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:481)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:382)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:335)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:136)
> ... 3 more
> Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block
> in entity reference
> at [row,col {unknown-source}]: [1017,49]
> at
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:699)
> at
> com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1071)
> at
> com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:810)
> at com.ctc.wstx.sr.StreamScanner.resolveCharEnt(StreamScanner.java:2325)
> at
> com.ctc.wstx.sr.StreamScanner.resolveCharOnlyEntity(StreamScanner.java:1347)
> at
> com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4715)
> at
> com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3722)
> at
> com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3676)
> ... 28 more
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493078#comment-15493078
]
Sergey Beryozkin commented on CXF-7045:
---
Hi Andriy, Aki
I'd rather let the users deal with it, yes. The user may have already installed
Jackson for the JAX-RS application to work with.
Shoud we still have
com.fasterxml.jackson.jaxrs.json;resolution:=optional added to the
cxf.osgi.import section ?
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493062#comment-15493062
]
Andriy Redko commented on CXF-7045:
---
Hey [~ay]
Yeah, it looks like that, dependency may have been present but not anymore. So
what road we would take? I would better not introduce the dependencies we
really don't need (remove it from feature.xml and update README with those two
bundles only). Or, adding optional dependency would be also an easy win. What
do you think?
Thanks!
Best Regards,
Andriy Redko
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6732) Allow SOAPAction to be overwritten via RequestContext property
[
https://issues.apache.org/jira/browse/CXF-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493055#comment-15493055
]
David Taxgaard commented on CXF-6732:
-
Hi
After updating from CXF version 2.7.10 to version 3.1.7 I have problems with
SOAPAction being an empty string when the endpoint is called.
I am using CXF with Camel and using PAYLOAD/Dispatcher
I have tracked down the problem to the fix in this JIRA and after method
setSoapAction in SoapPreProtocolOutInterceptor.java was changed SOAPAction is
no longer being set when using Camel in dispatcher mode.
Instead the SOAPAction is always "" (empty String) when the endpoint is called.
The old version of the class to into consideration that the SOAPAction might
already be set in the Request headers
if (!reqHeaders.containsKey(SoapBindingConstants.SOAP_ACTION)) {
reqHeaders.put(SoapBindingConstants.SOAP_ACTION,
Collections.singletonList(action));
}
while the new version just always add the action which in this case is an empty
String - perhaps the solution is to when whether action is != "" before adding
it.
reqHeaders.put(SoapBindingConstants.SOAP_ACTION,
Collections.singletonList(action));
> Allow SOAPAction to be overwritten via RequestContext property
> --
>
> Key: CXF-6732
> URL: https://issues.apache.org/jira/browse/CXF-6732
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 2.7.18, 3.2.0
>Reporter: Tomohisa Igarashi
>Assignee: Freeman Fang
> Fix For: 3.1.5, 3.0.8, 3.2.0
>
>
> SoapPreProtocolOutInterceptor sets SOAPAction into PROTOCOL_HEADERS only when
> it's not yet set here:
> https://fisheye6.atlassian.com/browse/cxf/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapPreProtocolOutInterceptor.java?hb=true#to121
> If user reuses the client like Dispatch instance, the PROTOCOL_HEADERS is
> carried over multiple invocations including SOAPAction specified for the
> first invocation, thus the "javax.xml.ws.soap.http.soapaction.uri" property
> is ignored afterward. IMO the "javax.xml.ws.soap.http.soapaction.uri"
> standard property should precede existing SOAPAction in PROTOCOL_HEADERS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-7045) Update sample description_swagger2_osgi README.txt
[
https://issues.apache.org/jira/browse/CXF-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492793#comment-15492793
]
Akitoshi Yoshida commented on CXF-7045:
---
[~reta] Hi Andriy, thanks for investigating the root cause.
Regarding com.fasterxml.jackson.jaxrs, it was referenced by swagger-jars 1.5.4,
but not by the recent ones. And it used to all work with cxf-3.1.5. I remember
swagger-feature of cxf-3.1.6 was broken because of the late change to the
jackson version in parent/pom.xml that was inconsistent with the jackson
version used by swagger. I remember fixing this issue in 3.1.7-SNAPSHOT and
tested it to work using the cxf-rt-rs-service-description-swagger feature. But
somehow, the released cxf 3.1.7 seems to have the wiring issue.
> Update sample description_swagger2_osgi README.txt
> --
>
> Key: CXF-7045
> URL: https://issues.apache.org/jira/browse/CXF-7045
> Project: CXF
> Issue Type: Bug
> Components: Samples
>Reporter: John Poth
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0):
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi
> [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
> Unresolved requirements:
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
