Issues with Attachments: week of 2017-02-06
CXF - Monday, February 6, 2017 4 Issues with Attachments (sorted oldest to newest) [CXF-6567] Allow alternate wildcard in Camel CXF Transport for Blueprint - Created: 2015-08-27 - Updated: 2017-01-12 - Type: Bug - Fix Versions: [] - Reporter: metatech - Assigned: Akitoshi Yoshida - Attachments: [CXF_blueprint_alternate_wildcard.diff] - https://issues.apache.org/jira/browse/CXF-6567 [CXF-7168] CXF WSN Publisher SOAP 1.2 Binding - Created: 2016-12-07 - Updated: 2017-01-31 - Type: Improvement - Fix Versions: [] - Reporter: Fahrettin Gökgöz - Assigned: Freeman Fang - Attachments: [WSNTest.zip, WSNTest.zip] - https://issues.apache.org/jira/browse/CXF-7168 [CXF-7214] Login Register Changing reply-to causes NPE in MessageSenderInterceptor.java - Created: 2017-01-18 - Updated: 2017-01-18 - Type: Bug - Fix Versions: [] - Reporter: Jackson Thompson - Assigned: Unassigned - Attachments: [pom.xml, src.zip] - https://issues.apache.org/jira/browse/CXF-7214 [CXF-7229] ClassHelper usages not replacable by ClassUnwrapper - Created: 2017-01-25 - Updated: 2017-01-27 - Type: Bug - Fix Versions: [] - Reporter: Romain Manni-Bucau - Assigned: Andriy Redko - Attachments: [proxy-test-annotations.txt, proxy-test-case.txt] - https://issues.apache.org/jira/browse/CXF-7229
[jira] [Created] (CXF-7243) Setting replyToDestination uses wrong queue
Jens Kleine-Herzbruch created CXF-7243: -- Summary: Setting replyToDestination uses wrong queue Key: CXF-7243 URL: https://issues.apache.org/jira/browse/CXF-7243 Project: CXF Issue Type: Bug Components: Transports Affects Versions: 3.1.9 Reporter: Jens Kleine-Herzbruch The fix for using the replyToDestination from CXF-7008 is incomplete. replyToDestination is supposed to be set in the request header, but should not actually be used by the client to retrieve the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CXF-7243) Setting replyToDestination uses wrong queue
[ https://issues.apache.org/jira/browse/CXF-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Kleine-Herzbruch updated CXF-7243: --- Attachment: replytodestination.diff This patch fixes the issue for me. > Setting replyToDestination uses wrong queue > --- > > Key: CXF-7243 > URL: https://issues.apache.org/jira/browse/CXF-7243 > Project: CXF > Issue Type: Bug > Components: Transports >Affects Versions: 3.1.9 >Reporter: Jens Kleine-Herzbruch > Labels: jms > Attachments: replytodestination.diff > > > The fix for using the replyToDestination from CXF-7008 is incomplete. > replyToDestination is supposed to be set in the request header, but should > not actually be used by the client to retrieve the response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CXF-7244) CXF 3.1.10 importing wrong class
Hector Kikuchi Martins created CXF-7244: --- Summary: CXF 3.1.10 importing wrong class Key: CXF-7244 URL: https://issues.apache.org/jira/browse/CXF-7244 Project: CXF Issue Type: Bug Affects Versions: 3.1.10 Environment: Java 8, karaf Reporter: Hector Kikuchi Martins The fix correcting the issue CXF-7213, do the follow attribution: Class collCls = Collection.class.isAssignableFrom(valueType) ? valueType : returnType; that uses the: org.apache.olingo.odata2.api.servicedocument.Collection And I'm getting a crash on my app, because I'm using FIQL, i'm not importing any odata dependency. I think it should use java.utils.Collections instead. Am I right? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CXF-7244) CXF 3.1.10 importing wrong class
[ https://issues.apache.org/jira/browse/CXF-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854105#comment-15854105 ] Sergey Beryozkin commented on CXF-7244: --- Ouch, this is unfortunate. The problem it was not detected by the tests which have the Olingo dependencies. Can you please add the Olingo dep just to get that code working, it won't affect your FiqlParser code... > CXF 3.1.10 importing wrong class > > > Key: CXF-7244 > URL: https://issues.apache.org/jira/browse/CXF-7244 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.10 > Environment: Java 8, karaf >Reporter: Hector Kikuchi Martins > > The fix correcting the issue CXF-7213, do the follow attribution: > Class collCls = Collection.class.isAssignableFrom(valueType) ? valueType : > returnType; > that uses the: > org.apache.olingo.odata2.api.servicedocument.Collection > And I'm getting a crash on my app, because I'm using FIQL, i'm not importing > any odata dependency. > I think it should use java.utils.Collections instead. Am I right? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CXF-7244) CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class
[ https://issues.apache.org/jira/browse/CXF-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin updated CXF-7244: -- Fix Version/s: 3.1.11 3.0.13 3.2.0 Summary: CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class (was: CXF 3.1.10 importing wrong class) Let me edit the subject a bit > CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class > -- > > Key: CXF-7244 > URL: https://issues.apache.org/jira/browse/CXF-7244 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.10 > Environment: Java 8, karaf >Reporter: Hector Kikuchi Martins > Fix For: 3.2.0, 3.0.13, 3.1.11 > > > The fix correcting the issue CXF-7213, do the follow attribution: > Class collCls = Collection.class.isAssignableFrom(valueType) ? valueType : > returnType; > that uses the: > org.apache.olingo.odata2.api.servicedocument.Collection > And I'm getting a crash on my app, because I'm using FIQL, i'm not importing > any odata dependency. > I think it should use java.utils.Collections instead. Am I right? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CXF-7244) CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class
[ https://issues.apache.org/jira/browse/CXF-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned CXF-7244: - Assignee: Sergey Beryozkin > CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class > -- > > Key: CXF-7244 > URL: https://issues.apache.org/jira/browse/CXF-7244 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.10 > Environment: Java 8, karaf >Reporter: Hector Kikuchi Martins >Assignee: Sergey Beryozkin > Fix For: 3.2.0, 3.1.11 > > > The fix correcting the issue CXF-7213, do the follow attribution: > Class collCls = Collection.class.isAssignableFrom(valueType) ? valueType : > returnType; > that uses the: > org.apache.olingo.odata2.api.servicedocument.Collection > And I'm getting a crash on my app, because I'm using FIQL, i'm not importing > any odata dependency. > I think it should use java.utils.Collections instead. Am I right? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CXF-7244) CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class
[ https://issues.apache.org/jira/browse/CXF-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-7244. --- Resolution: Fixed Fix Version/s: (was: 3.0.13) > CXF 3.1.10 AbstractSearchConditionParser importing Olingo Collection class > -- > > Key: CXF-7244 > URL: https://issues.apache.org/jira/browse/CXF-7244 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.10 > Environment: Java 8, karaf >Reporter: Hector Kikuchi Martins > Fix For: 3.2.0, 3.1.11 > > > The fix correcting the issue CXF-7213, do the follow attribution: > Class collCls = Collection.class.isAssignableFrom(valueType) ? valueType : > returnType; > that uses the: > org.apache.olingo.odata2.api.servicedocument.Collection > And I'm getting a crash on my app, because I'm using FIQL, i'm not importing > any odata dependency. > I think it should use java.utils.Collections instead. Am I right? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
