Issues with Attachments: week of 2017-09-04
CXF - Monday, September 4, 2017 2 Issues with Attachments (sorted oldest to newest) [CXF-7463] No evaluation for spring expression as value for 'address' attribute in - Created: 2017-08-01 - Updated: 2017-08-07 - Type: Bug - Fix Versions: [NeedMoreInfo] - Reporter: RANADEEP SHARMA - Assigned: Unassigned - Attachments: [CXF_JaxWS_exception_trace.txt] - https://issues.apache.org/jira/browse/CXF-7463 [CXF-7490] JAX-RS REST server causes long bundle starting time in OSGi blueprint - Created: 2017-08-30 - Updated: 2017-08-30 - Type: Bug - Fix Versions: [] - Reporter: Max Schlüssel - Assigned: Unassigned - Attachments: [my-rest-test.zip] - https://issues.apache.org/jira/browse/CXF-7490
[jira] [Commented] (CXF-7494) Handle SOAPAction with single quotes
[ https://issues.apache.org/jira/browse/CXF-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152449#comment-16152449 ] Dennis Kieselhorst commented on CXF-7494: - I noticed this issue in a migration project from Axis 2 to CXF. While Axis 2 was handling single quotes, the request failed in CXF and it was not possible to do the migration without changes on the client side. > Handle SOAPAction with single quotes > > > Key: CXF-7494 > URL: https://issues.apache.org/jira/browse/CXF-7494 > Project: CXF > Issue Type: Improvement > Components: Soap Binding >Affects Versions: 3.1.12 >Reporter: Dennis Kieselhorst >Assignee: Dennis Kieselhorst >Priority: Minor > Fix For: 3.2.0 > > > SoapActionInInterceptor only handles double quotes. CXF should be robust and > also handle single quotes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CXF-7494) Handle SOAPAction with single quotes
Dennis Kieselhorst created CXF-7494: --- Summary: Handle SOAPAction with single quotes Key: CXF-7494 URL: https://issues.apache.org/jira/browse/CXF-7494 Project: CXF Issue Type: Improvement Components: Soap Binding Affects Versions: 3.1.12 Reporter: Dennis Kieselhorst Assignee: Dennis Kieselhorst Priority: Minor Fix For: 3.2.0 SoapActionInInterceptor only handles double quotes. CXF should be robust and also handle single quotes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CXF-7494) Handle SOAPAction with single quotes
[ https://issues.apache.org/jira/browse/CXF-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved CXF-7494. - Resolution: Fixed > Handle SOAPAction with single quotes > > > Key: CXF-7494 > URL: https://issues.apache.org/jira/browse/CXF-7494 > Project: CXF > Issue Type: Improvement > Components: Soap Binding >Affects Versions: 3.1.12 >Reporter: Dennis Kieselhorst >Assignee: Dennis Kieselhorst >Priority: Minor > Fix For: 3.2.0 > > > SoapActionInInterceptor only handles double quotes. CXF should be robust and > also handle single quotes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-7473:
Fix Version/s: 3.2.0
3.1.13
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13, 3.2.0
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152484#comment-16152484
]
Dennis Kieselhorst commented on CXF-7473:
-
Thanks for the bug report. I was able to reproduce this and commited
ProviderFactoryHierarchicalExceptionMapperTest for it.
[~sergey_beryozkin] can you please take a look? I think
ProviderFactory.getGenericInterfaces needs to be changed but you already did
several fixes in the past and I don't want to introduce new issues...
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152523#comment-16152523
]
Sergey Beryozkin commented on CXF-7473:
---
Thanks, I'd rather avoid risking tweaking that code to support yet another
hierarchy right...
By the way, the question is, given this declaration, "E extends Throwable", why
selecting IllegalArgumentExceptionMapper is a mistake given that both
UnmappedRuntimeException and IllegalArgumentExceptionMapper extend Throwable ?
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13, 3.2.0
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152523#comment-16152523
]
Sergey Beryozkin edited comment on CXF-7473 at 9/4/17 12:01 PM:
Thanks, I'd rather avoid risking tweaking that code to support yet another
hierarchy right just a day or so before the release...
By the way, the question is, given this declaration, "E extends Throwable", why
selecting IllegalArgumentExceptionMapper is a mistake given that both
UnmappedRuntimeException and IllegalArgumentExceptionMapper extend Throwable ?
was (Author: sergey_beryozkin):
Thanks, I'd rather avoid risking tweaking that code to support yet another
hierarchy right...
By the way, the question is, given this declaration, "E extends Throwable", why
selecting IllegalArgumentExceptionMapper is a mistake given that both
UnmappedRuntimeException and IllegalArgumentExceptionMapper extend Throwable ?
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13, 3.2.0
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152531#comment-16152531
]
Dennis Kieselhorst commented on CXF-7473:
-
Well in this case E is IllegalArgumentException and therefore you'll get a
ClassCastException.
But you're right, we should postpone it to 3.2.1.
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-7473:
Fix Version/s: (was: 3.2.0)
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152533#comment-16152533
]
Sergey Beryozkin commented on CXF-7473:
---
Is that visible at the runtime, that is what I'm not quite sure ?
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152535#comment-16152535
]
Sergey Beryozkin commented on CXF-7473:
---
Probably is, will need to check...
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152544#comment-16152544
]
Dennis Kieselhorst commented on CXF-7473:
-
It is, put a breakpoint in ProviderFactory.getGenericInterfaces and run
ProviderFactoryHierarchicalExceptionMapperTest.
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152558#comment-16152558
]
Sergey Beryozkin commented on CXF-7473:
---
Thanks, do you reckon there's an obvious fix there ? I'd just like to avoid
Syncope (or others who may have some hierarchies) starting failing so indeed,
lets make it work for 3.2.1
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CXF-7495) Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in older version
Marco Tenti created CXF-7495: Summary: Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in older version Key: CXF-7495 URL: https://issues.apache.org/jira/browse/CXF-7495 Project: CXF Issue Type: Task Components: JAXB Databinding, Soap Binding Affects Versions: 3.0.4, 2.2.12 Environment: Windows 10, java 1.8.0_131, Eclipse IE Reporter: Marco Tenti Priority: Minor I have a soap service . it support the mtom but not the xop include annotation , so it refused my request: _http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * http://www.w3.org/2004/08/xop/include"; href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/>* _ how can i set my request to this: _http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4* _ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CXF-7495) Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tenti updated CXF-7495: - Description: I have a soap service . it support the mtom but not the xop include annotation , so it refused my request: _ http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * http://www.w3.org/2004/08/xop/include"; href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/>* _ how can i set my request to this: _http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4* _ how can obtain this result? in more recent version there is a paramter for this https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE was: I have a soap service . it support the mtom but not the xop include annotation , so it refused my request: _http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * http://www.w3.org/2004/08/xop/include"; href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/>* _ how can i set my request to this: _http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4* _ > Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in > older version > > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: easyfix, newbie, starter > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > _ > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > * http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/>* > > > > > _ > how can i set my request to this: > _ xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > * cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4* > > > > > > _ > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CXF-7495) Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tenti updated CXF-7495: - Description: I have a soap service . it support the mtom but not the xop include annotation , so it refused my request: http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 http://www.w3.org/2004/08/xop/include"; href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> how can i set my request to this: http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 how can obtain this result? in more recent version there is a paramter for this https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE was: I have a soap service . it support the mtom but not the xop include annotation , so it refused my request: _ http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * http://www.w3.org/2004/08/xop/include"; href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/>* _ how can i set my request to this: _http://schemas.xmlsoap.org/soap/envelope/";> http://schemas.xmlsoap.org/soap/envelope/"/> http://sip.receive.core.iris.eng.it"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> ? ? SHA-256 HEX 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 * cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4* _ how can obtain this result? in more recent version there is a paramter for this https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE > Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in > older version > > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: easyfix, newbie, starter > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> > > > > > > how can i set my request to this: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 > > > > > > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CXF-7495) Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tenti updated CXF-7495: - Summary: Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version (was: Set EXPAND_XOP_INCLUDE_FOR_SIGNATURE for WSS4JOutInterceptor to 'false' in older version) > Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version > -- > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: easyfix, newbie, starter > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> > > > > > > how can i set my request to this: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 > > > > > > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152604#comment-16152604
]
Dennis Kieselhorst commented on CXF-7473:
-
I think if actualType is present and doesn't match we need to skip further
processing:
https://github.com/deki/cxf/commit/ccfa72289b3fbba46db0a9f8824011aefde8c9ba
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CXF-7495) Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tenti updated CXF-7495: - External issue URL: https://stackoverflow.com/questions/46038257/set-expand-xop-include-for-wss4joutinterceptor-to-false-in-older-version-of-ap > Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version > -- > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: easyfix, newbie, starter > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> > > > > > > how can i set my request to this: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 > > > > > > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7473) ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
[
https://issues.apache.org/jira/browse/CXF-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152625#comment-16152625
]
Sergey Beryozkin commented on CXF-7473:
---
I vaguely recall that the reason I did that extra check is that further
drilling down due to the current actualType being of some parameterized/etc
types does make it right for some hierarchies.
I guess it would be a bit safer if we check that if the actual type is not null
and it is not in the java.lang.reflect package then do that check ?
By the way, I think 'types' can never be null, so you can safely remove that
"if types != null" check...
thanks
> ExceptionMapper class hierarchies: incompatible ExceptionMapper selected
>
>
> Key: CXF-7473
> URL: https://issues.apache.org/jira/browse/CXF-7473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.11, 3.1.12
>Reporter: Jocelyn Lepage
> Fix For: 3.1.13
>
>
> CXF seems to select an incompatible ExceptionMapper when using class
> hierarchies.
> More precisely, if I define an abstract exception class like following:
> {code:java}
> @Provider
> public abstract class AbstractExceptionMapper implements
> ExceptionMapper {
> ...
> {code}
> Then I define a concrete one for IllegalArgumentExceptions:
> {code:java}
> public class IllegalArgumentExceptionMapper extends
> AbstractExceptionMapper {
> ...
> {code}
> IllegalArgumentExceptionMapper will then be selected even for
> RuntimeException subtypes unrelated to IllegalArgumentExceptions.
> See minimal project showing the problem
> [here|https://github.com/jlepage-appdirect/cxf-exception-mapper-bug]
> Similar (if not same) problem seems to have been reported via CXF-6635, but I
> do see this with 3.1.11 and 3.1.12.
> Thx!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CXF-7495) Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tenti updated CXF-7495: - Labels: cxf jaws mtom wss4j-configuration (was: cxf easyfix jaws mtom wss4j-configuration) > Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version > -- > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: cxf, jaws, mtom, wss4j-configuration > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> > > > > > > how can i set my request to this: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 > > > > > > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7495) Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152726#comment-16152726 ] Colm O hEigeartaigh commented on CXF-7495: -- Are you using WS-SecurityPolicy or not? What CXF version are you using? There is a JAX-WS configuration property "ws-security.store.bytes.in.attachment" that you can set to "false" (CXF 3.1.x) onwards that controls this behaviour: http://cxf.apache.org/docs/ws-securitypolicy.html > Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version > -- > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: cxf, jaws, mtom, wss4j-configuration > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> > > > > > > how can i set my request to this: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 > > > > > > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CXF-7495) Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version
[ https://issues.apache.org/jira/browse/CXF-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tenti updated CXF-7495: - Labels: cxf easyfix jaws mtom wss4j-configuration (was: easyfix newbie starter) > Set EXPAND_XOP_INCLUDE for WSS4JOutInterceptor to 'false' in older version > -- > > Key: CXF-7495 > URL: https://issues.apache.org/jira/browse/CXF-7495 > Project: CXF > Issue Type: Task > Components: JAXB Databinding, Soap Binding >Affects Versions: 2.2.12, 3.0.4 > Environment: Windows 10, java 1.8.0_131, Eclipse IE >Reporter: Marco Tenti >Priority: Minor > Labels: cxf, jaws, mtom, wss4j-configuration > > I have a soap service . it support the mtom but not the xop include > annotation , so it refused my request: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > http://www.w3.org/2004/08/xop/include"; > href="cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4-1@cxf.apache.org"/> > > > > > > how can i set my request to this: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/> > > http://sip.receive.core.iris.eng.it"; > xmlns:xmime="http://www.w3.org/2005/05/xmlmime";> > > ? > ? > SHA-256 > HEX > > 9e830c2ac56eca00023b17e3c17ed1014e055f960c3ee4778a84aa02c6dafcb9 > > > > cid:92dc39d3-e3d5-4aa2-a9cb-7582483934a4 > > > > > > how can obtain this result? in more recent version there is a paramter for > this > https://ws.apache.org/wss4j/apidocs/org/apache/wss4j/common/ConfigurationConstants.html#EXPAND_XOP_INCLUDE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[ https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152794#comment-16152794 ] Sergey Beryozkin commented on CXF-7485: --- Starting from CXF 3.1.13 and 3.2.0 setting a "cxf.servlet.init.use-x-forwarded-headers=true" will do, the property is already supported now but only really does something useful with X-Forwarded-Proto and X-Forwarded-For, ignoring all other X-Forwarded headers which are set by Zuul > Reverse proxy url is not reflected in Swagger UI response > - > > Key: CXF-7485 > URL: https://issues.apache.org/jira/browse/CXF-7485 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.12 >Reporter: na sam >Assignee: Sergey Beryozkin > Fix For: 3.1.13, 3.2.0 > > > I am using Swagger2Feature to generate the swagger out of my REST service > classes. > All the url's that is being generated are based on deployed server's web > path. Its working directly in my server. But If the request comes via reverse > proxy, then in my swagger ui response I am seeing still same my local > server's webpath instead of one coming via reverse proxy. > Need a way to support reverse proxy web path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CXF-7496) Parsing Bug in org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter: in-string "{"
Alon Bar-Lev created CXF-7496:
-
Summary: Parsing Bug in
org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter: in-string "{"
Key: CXF-7496
URL: https://issues.apache.org/jira/browse/CXF-7496
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 3.1.12, 3.1.7
Environment: java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
Reporter: Alon Bar-Lev
Hello,
We have found incorrect parsing of "{" within JSON strings. It seems like the
parser searches for "{" and "}" regardless of string boundary.
A reproduction program is attached, using latest 3.1.12 version.
Thanks!
h2. REPRODUCTION
{code}
import org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter;
public class JsonMapReaderNotWorking {
public static void main(String args[]) throws Exception
{
JsonMapObjectReaderWriter jsonMapObjectReaderWriter = new
JsonMapObjectReaderWriter();
String s = "{\"x\":{\"y\":\"{\"}}";
System.out.println(s);
jsonMapObjectReaderWriter.fromJson(s);
}
}
{code}
h2. RESULT
{code}
{"x":{"y":"{"}}
Exception in thread "main" java.lang.StringIndexOutOfBoundsException:
String index out of range: -6
at java.lang.String.substring(String.java:1967)
at
org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter.readJsonObjectAsSettable(JsonMapObjectReaderWriter.java:189)
at
org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter.fromJson(JsonMapObjectReaderWriter.java:162)
at JsonMapReaderNotWorking.main(JsonMapReaderNotWorking.java:13)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[ https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-7485. --- Resolution: Fixed Fix Version/s: 3.2.0 3.1.13 > Reverse proxy url is not reflected in Swagger UI response > - > > Key: CXF-7485 > URL: https://issues.apache.org/jira/browse/CXF-7485 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.12 >Reporter: na sam >Assignee: Sergey Beryozkin > Fix For: 3.1.13, 3.2.0 > > > I am using Swagger2Feature to generate the swagger out of my REST service > classes. > All the url's that is being generated are based on deployed server's web > path. Its working directly in my server. But If the request comes via reverse > proxy, then in my swagger ui response I am seeing still same my local > server's webpath instead of one coming via reverse proxy. > Need a way to support reverse proxy web path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[
https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152924#comment-16152924
]
na sam commented on CXF-7485:
--
hi
Following is the version I am testing it for swagger. Could you please share
which maven dependency I need to use?
3.1.11
org.apache.cxf
cxf-spring-boot-starter-jaxrs
${cxf.version}
org.apache.cxf
cxf-rt-rs-service-description
${cxf.version}
org.apache.cxf
cxf-rt-rs-service-description-swagger
${cxf.version}
> Reverse proxy url is not reflected in Swagger UI response
> -
>
> Key: CXF-7485
> URL: https://issues.apache.org/jira/browse/CXF-7485
> Project: CXF
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 3.1.12
>Reporter: na sam
>Assignee: Sergey Beryozkin
> Fix For: 3.1.13, 3.2.0
>
>
> I am using Swagger2Feature to generate the swagger out of my REST service
> classes.
> All the url's that is being generated are based on deployed server's web
> path. Its working directly in my server. But If the request comes via reverse
> proxy, then in my swagger ui response I am seeing still same my local
> server's webpath instead of one coming via reverse proxy.
> Need a way to support reverse proxy web path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[ https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152939#comment-16152939 ] Sergey Beryozkin commented on CXF-7485: --- Please try 3.1.13-SNAPSHOT or 3.2.0-SNAPSHOT > Reverse proxy url is not reflected in Swagger UI response > - > > Key: CXF-7485 > URL: https://issues.apache.org/jira/browse/CXF-7485 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.12 >Reporter: na sam >Assignee: Sergey Beryozkin > Fix For: 3.1.13, 3.2.0 > > > I am using Swagger2Feature to generate the swagger out of my REST service > classes. > All the url's that is being generated are based on deployed server's web > path. Its working directly in my server. But If the request comes via reverse > proxy, then in my swagger ui response I am seeing still same my local > server's webpath instead of one coming via reverse proxy. > Need a way to support reverse proxy web path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[ https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152942#comment-16152942 ] na sam commented on CXF-7485: -- I am getting "3.2.0-SNAPSHOT is missing" Following is the cxf git hub project that I am using to test it for swagger issue. git clone https://bitbucket.org/asimio/springboot-cxf-swagger-example.git > Reverse proxy url is not reflected in Swagger UI response > - > > Key: CXF-7485 > URL: https://issues.apache.org/jira/browse/CXF-7485 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.12 >Reporter: na sam >Assignee: Sergey Beryozkin > Fix For: 3.1.13, 3.2.0 > > > I am using Swagger2Feature to generate the swagger out of my REST service > classes. > All the url's that is being generated are based on deployed server's web > path. Its working directly in my server. But If the request comes via reverse > proxy, then in my swagger ui response I am seeing still same my local > server's webpath instead of one coming via reverse proxy. > Need a way to support reverse proxy web path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[ https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152947#comment-16152947 ] Sergey Beryozkin commented on CXF-7485: --- I don't why 3.2.0-SNAPSHOT is missing, try 3.1.13-SNAPSHOT. May be you need to enable the snapshot repo... > Reverse proxy url is not reflected in Swagger UI response > - > > Key: CXF-7485 > URL: https://issues.apache.org/jira/browse/CXF-7485 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.12 >Reporter: na sam >Assignee: Sergey Beryozkin > Fix For: 3.1.13, 3.2.0 > > > I am using Swagger2Feature to generate the swagger out of my REST service > classes. > All the url's that is being generated are based on deployed server's web > path. Its working directly in my server. But If the request comes via reverse > proxy, then in my swagger ui response I am seeing still same my local > server's webpath instead of one coming via reverse proxy. > Need a way to support reverse proxy web path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7496) Parsing Bug in org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter: in-string "{"
[
https://issues.apache.org/jira/browse/CXF-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152949#comment-16152949
]
Sergey Beryozkin commented on CXF-7496:
---
I might need to introduce Jackson internally, as an optional alternative to the
'home-grown' simple parser; for now I'll have a look if a quick fix is possible
> Parsing Bug in org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter:
> in-string "{"
> ---
>
> Key: CXF-7496
> URL: https://issues.apache.org/jira/browse/CXF-7496
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.7, 3.1.12
> Environment: java version "1.8.0_25"
> Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
> Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
>Reporter: Alon Bar-Lev
>
> Hello,
> We have found incorrect parsing of "{" within JSON strings. It seems like the
> parser searches for "{" and "}" regardless of string boundary.
> A reproduction program is attached, using latest 3.1.12 version.
> Thanks!
> h2. REPRODUCTION
> {code}
> import org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter;
> public class JsonMapReaderNotWorking {
>
> public static void main(String args[]) throws Exception
> {
> JsonMapObjectReaderWriter jsonMapObjectReaderWriter = new
> JsonMapObjectReaderWriter();
> String s = "{\"x\":{\"y\":\"{\"}}";
> System.out.println(s);
> jsonMapObjectReaderWriter.fromJson(s);
> }
> }
> {code}
> h2. RESULT
> {code}
> {"x":{"y":"{"}}
> Exception in thread "main" java.lang.StringIndexOutOfBoundsException:
> String index out of range: -6
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter.readJsonObjectAsSettable(JsonMapObjectReaderWriter.java:189)
> at
> org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter.fromJson(JsonMapObjectReaderWriter.java:162)
> at JsonMapReaderNotWorking.main(JsonMapReaderNotWorking.java:13)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CXF-7485) Reverse proxy url is not reflected in Swagger UI response
[ https://issues.apache.org/jira/browse/CXF-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152974#comment-16152974 ] na sam commented on CXF-7485: -- I tested with 3.1.13-SNAPSHOT version. I am able to see the webpath that is being sent via proxy server in the /api/swagger.json end point as part of "basePath" element. I am able to execute the api swagger end point via proxy server. But issue is same proxy basePath is cached always once I accessed it via proxy server. After that If I tried to access swagger ui directly (ie without proxy), then same basePath is cached showing in the swagger.json and getting 404 exception. > Reverse proxy url is not reflected in Swagger UI response > - > > Key: CXF-7485 > URL: https://issues.apache.org/jira/browse/CXF-7485 > Project: CXF > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.12 >Reporter: na sam >Assignee: Sergey Beryozkin > Fix For: 3.1.13, 3.2.0 > > > I am using Swagger2Feature to generate the swagger out of my REST service > classes. > All the url's that is being generated are based on deployed server's web > path. Its working directly in my server. But If the request comes via reverse > proxy, then in my swagger ui response I am seeing still same my local > server's webpath instead of one coming via reverse proxy. > Need a way to support reverse proxy web path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7496) Parsing Bug in org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter: in-string "{"
[
https://issues.apache.org/jira/browse/CXF-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153107#comment-16153107
]
Alon Bar-Lev commented on CXF-7496:
---
Thanks!
> Parsing Bug in org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter:
> in-string "{"
> ---
>
> Key: CXF-7496
> URL: https://issues.apache.org/jira/browse/CXF-7496
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.1.7, 3.1.12
> Environment: java version "1.8.0_25"
> Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
> Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
>Reporter: Alon Bar-Lev
>
> Hello,
> We have found incorrect parsing of "{" within JSON strings. It seems like the
> parser searches for "{" and "}" regardless of string boundary.
> A reproduction program is attached, using latest 3.1.12 version.
> Thanks!
> h2. REPRODUCTION
> {code}
> import org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter;
> public class JsonMapReaderNotWorking {
>
> public static void main(String args[]) throws Exception
> {
> JsonMapObjectReaderWriter jsonMapObjectReaderWriter = new
> JsonMapObjectReaderWriter();
> String s = "{\"x\":{\"y\":\"{\"}}";
> System.out.println(s);
> jsonMapObjectReaderWriter.fromJson(s);
> }
> }
> {code}
> h2. RESULT
> {code}
> {"x":{"y":"{"}}
> Exception in thread "main" java.lang.StringIndexOutOfBoundsException:
> String index out of range: -6
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter.readJsonObjectAsSettable(JsonMapObjectReaderWriter.java:189)
> at
> org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter.fromJson(JsonMapObjectReaderWriter.java:162)
> at JsonMapReaderNotWorking.main(JsonMapReaderNotWorking.java:13)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
