[jira] [Resolved] (CAMEL-6435) Remove obsolete 'transient' modifier from static fields
[ https://issues.apache.org/jira/browse/CAMEL-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6435. Resolution: Fixed Fix Version/s: (was: Future) (was: 3.0.0) 2.12.0 Assignee: Claus Ibsen Thanks Matthew for the patch Remove obsolete 'transient' modifier from static fields --- Key: CAMEL-6435 URL: https://issues.apache.org/jira/browse/CAMEL-6435 Project: Camel Issue Type: Improvement Affects Versions: 2.11.0 Reporter: Henryk Konsek Assignee: Claus Ibsen Priority: Minor Fix For: 2.12.0 In many places within the Camel code base we can find static fields with transient modifier. Static fields are automatically transient, so the latter declaration is obsolete. We should clean the code base from the obsolete transient keywords. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6625) potential NPE in CxfConsumer if the PAYLOAD not match the ServiceModel
[
https://issues.apache.org/jira/browse/CAMEL-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-6625.
-
Resolution: Fixed
Fix Version/s: 2.12.0
2.11.2
2.10.7
potential NPE in CxfConsumer if the PAYLOAD not match the ServiceModel
--
Key: CAMEL-6625
URL: https://issues.apache.org/jira/browse/CAMEL-6625
Project: Camel
Issue Type: Bug
Components: camel-cxf
Reporter: Freeman Fang
Assignee: Freeman Fang
Fix For: 2.10.7, 2.11.2, 2.12.0
currently in CxfConsumer we have code like
{code}
BindingOperationInfo boi =
cxfExchange.getBindingOperationInfo();
// make sure the boi is remained as wrapped in PAYLOAD mode
if (dataFormat == DataFormat.PAYLOAD boi.isUnwrapped()) {
boi = boi.getWrappedOperation();
cxfExchange.put(BindingOperationInfo.class, boi);
}
{code}
however, the boi could be NULL if the message PAYLOAD not match the
ServiceModel, which means can't determine the operation from the PAYLOAD,
should add a NPE guarder before boi.isUnwrapped to avoid the NPE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6435) Remove obsolete 'transient' modifier from static fields
[
https://issues.apache.org/jira/browse/CAMEL-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740825#comment-13740825
]
Babak Vahdat commented on CAMEL-6435:
-
I also removed the {{transient}} modifier even by the loggers declared as
instance variables as since SLF4J version 1.5.3 the logger instances survive
serialization so that when using a deserialized class object we prefer to avoid
a NPE when the given logger instance variable is accessed inside the logic of
the encapsulating object, owning the logger instance variable itself. For more
details see the Logger serialization paragraph here:
http://slf4j.org/faq.html#declared_static
Remove obsolete 'transient' modifier from static fields
---
Key: CAMEL-6435
URL: https://issues.apache.org/jira/browse/CAMEL-6435
Project: Camel
Issue Type: Improvement
Affects Versions: 2.11.0
Reporter: Henryk Konsek
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.12.0
In many places within the Camel code base we can find static fields with
transient modifier. Static fields are automatically transient, so the latter
declaration is obsolete.
We should clean the code base from the obsolete transient keywords.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6435) Remove the obsolete 'transient' modifier from both the static/non-static SLF4J Logger fields.
[ https://issues.apache.org/jira/browse/CAMEL-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-6435: Summary: Remove the obsolete 'transient' modifier from both the static/non-static SLF4J Logger fields. (was: Remove obsolete 'transient' modifier from static fields) Remove the obsolete 'transient' modifier from both the static/non-static SLF4J Logger fields. - Key: CAMEL-6435 URL: https://issues.apache.org/jira/browse/CAMEL-6435 Project: Camel Issue Type: Improvement Affects Versions: 2.11.0 Reporter: Henryk Konsek Assignee: Claus Ibsen Priority: Minor Fix For: 2.12.0 In many places within the Camel code base we can find static fields with transient modifier. Static fields are automatically transient, so the latter declaration is obsolete. We should clean the code base from the obsolete transient keywords. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6639) SimpleLanguage.simple should detect if its a predicate and use that instead
Claus Ibsen created CAMEL-6639: -- Summary: SimpleLanguage.simple should detect if its a predicate and use that instead Key: CAMEL-6639 URL: https://issues.apache.org/jira/browse/CAMEL-6639 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.11.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.11.2, 2.12.0 When using predicates with the simple language static methods, then ppl should use the correct method. We should improve the javadoc, and as well add methods for easy to create predicates. See nabble http://camel.465427.n5.nabble.com/How-to-check-that-a-file-is-empty-tp5737256.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6639) SimpleLanguage.simple should detect if its a predicate and use that instead
[ https://issues.apache.org/jira/browse/CAMEL-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6639. Resolution: Fixed SimpleLanguage.simple should detect if its a predicate and use that instead --- Key: CAMEL-6639 URL: https://issues.apache.org/jira/browse/CAMEL-6639 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.11.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.11.2, 2.12.0 When using predicates with the simple language static methods, then ppl should use the correct method. We should improve the javadoc, and as well add methods for easy to create predicates. See nabble http://camel.465427.n5.nabble.com/How-to-check-that-a-file-is-empty-tp5737256.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6622) Support XML Encryption 1.1 features in the camel-xmlsecurity component
[ https://issues.apache.org/jira/browse/CAMEL-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740881#comment-13740881 ] Colm O hEigeartaigh commented on CAMEL-6622: Thanks Claus, I have updated the wiki with the new configuration options. Colm. Support XML Encryption 1.1 features in the camel-xmlsecurity component -- Key: CAMEL-6622 URL: https://issues.apache.org/jira/browse/CAMEL-6622 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Fix For: 2.12.0 Attachments: camel-6622.patch This task is to support XML Encryption 1.1 functionality in the camel-xmlsecurity component. This includes: a) Support for the GCM versions of AES b) Support for SHA 1 with the RSA OAEP algorithm c) Support for MGF algorithms with SHA 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6622) Support XML Encryption 1.1 features in the camel-xmlsecurity component
[ https://issues.apache.org/jira/browse/CAMEL-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740896#comment-13740896 ] Claus Ibsen commented on CAMEL-6622: Colm, fell free to add a note on the 2.12 release notes about this new functionality if you want http://camel.apache.org/camel-2120-release.html Support XML Encryption 1.1 features in the camel-xmlsecurity component -- Key: CAMEL-6622 URL: https://issues.apache.org/jira/browse/CAMEL-6622 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Claus Ibsen Fix For: 2.12.0 Attachments: camel-6622.patch This task is to support XML Encryption 1.1 functionality in the camel-xmlsecurity component. This includes: a) Support for the GCM versions of AES b) Support for SHA 1 with the RSA OAEP algorithm c) Support for MGF algorithms with SHA 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6622) Support XML Encryption 1.1 features in the camel-xmlsecurity component
[ https://issues.apache.org/jira/browse/CAMEL-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6622. Resolution: Fixed Assignee: Claus Ibsen Thanks Support XML Encryption 1.1 features in the camel-xmlsecurity component -- Key: CAMEL-6622 URL: https://issues.apache.org/jira/browse/CAMEL-6622 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Claus Ibsen Fix For: 2.12.0 Attachments: camel-6622.patch This task is to support XML Encryption 1.1 functionality in the camel-xmlsecurity component. This includes: a) Support for the GCM versions of AES b) Support for SHA 1 with the RSA OAEP algorithm c) Support for MGF algorithms with SHA 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6238) support JSONPath as a Camel Language for easy JSON filtering and expression evaluation
[ https://issues.apache.org/jira/browse/CAMEL-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740899#comment-13740899 ] Claus Ibsen commented on CAMEL-6238: James I wonder if we should get what you got into the code base? Even just support for expressions seems good, as that can help grab stuff from json more easily than what you can do today. support JSONPath as a Camel Language for easy JSON filtering and expression evaluation -- Key: CAMEL-6238 URL: https://issues.apache.org/jira/browse/CAMEL-6238 Project: Camel Issue Type: New Feature Reporter: james strachan Assignee: james strachan Fix For: 2.12.0 JSON is a very popular message format; yet its kinda painful performing expressions on it as typically you have to marshal it first into some specific domain model (or Maps / Lists) and then use some general purpose Java expression language on it. JSONPath looks pretty cool though; kinda like XPath but designed for arbitrary JSON payloads https://code.google.com/p/json-path/ the library is small Apache licensed so it should be pretty easy to wrap up as a Camel Language -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6238) support JSONPath as a Camel Language for easy JSON filtering and expression evaluation
[ https://issues.apache.org/jira/browse/CAMEL-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740919#comment-13740919 ] james strachan commented on CAMEL-6238: --- the predicates part is a bit icky though to be honest; without predicates its kinda useless for many common camel use cases (as we tend to use predicates alot for content based routing and whatnot). I'm wondering if instead it might be better to just make a JSONPath as a kinda filter/wrapper around one or more other languages, which just ensure the JSON gets 'beanified' first then delegates to a real expression language that supports expressions and predicates? e.g. I was wondering now the EL is standardised and has methods and property support along with predicates expressions; being a standard, that might be a nice default EL for JSON; we just need to ensure we add a 'JSON parse' step to turn a String into Maps of Lists/Maps etc with jackson; then we use Juel on that? support JSONPath as a Camel Language for easy JSON filtering and expression evaluation -- Key: CAMEL-6238 URL: https://issues.apache.org/jira/browse/CAMEL-6238 Project: Camel Issue Type: New Feature Reporter: james strachan Assignee: james strachan Fix For: 2.12.0 JSON is a very popular message format; yet its kinda painful performing expressions on it as typically you have to marshal it first into some specific domain model (or Maps / Lists) and then use some general purpose Java expression language on it. JSONPath looks pretty cool though; kinda like XPath but designed for arbitrary JSON payloads https://code.google.com/p/json-path/ the library is small Apache licensed so it should be pretty easy to wrap up as a Camel Language -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6471) CxfPayload - Dont output the body in toString if streaming mode
[ https://issues.apache.org/jira/browse/CAMEL-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CAMEL-6471: --- Fix Version/s: 2.11.2 CxfPayload - Dont output the body in toString if streaming mode --- Key: CAMEL-6471 URL: https://issues.apache.org/jira/browse/CAMEL-6471 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.11.2, 2.12.0 org.apache.camel.component.cxf.CxfPayload#toString This forces outputting the body even if its streaming mode. This is bad. We should not load the stream into memory. There is already good logging support by the log component where you can turn on|off logging streams etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6471) CxfPayload - Dont output the body in toString if streaming mode
[ https://issues.apache.org/jira/browse/CAMEL-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740934#comment-13740934 ] Aki Yoshida commented on CAMEL-6471: integrated the fix into 2.11.x and updated the fix version info. CxfPayload - Dont output the body in toString if streaming mode --- Key: CAMEL-6471 URL: https://issues.apache.org/jira/browse/CAMEL-6471 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.11.2, 2.12.0 org.apache.camel.component.cxf.CxfPayload#toString This forces outputting the body even if its streaming mode. This is bad. We should not load the stream into memory. There is already good logging support by the log component where you can turn on|off logging streams etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-6629) Add requestBufferSize and requestHeaderSize options for jetty
[ https://issues.apache.org/jira/browse/CAMEL-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-6629: -- Assignee: Claus Ibsen Add requestBufferSize and requestHeaderSize options for jetty - Key: CAMEL-6629 URL: https://issues.apache.org/jira/browse/CAMEL-6629 Project: Camel Issue Type: Improvement Components: camel-jetty Affects Versions: 2.10.4, 2.11.1 Reporter: Pratyusha Ghosh Assignee: Claus Ibsen Add requestBufferSize and requestHeaderSize options for jetty server to allow configuration of allowable request header limit This option is exposed by standalone jetty server but not exposed by camel-jetty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6629) Add requestBufferSize and requestHeaderSize options for jetty
[ https://issues.apache.org/jira/browse/CAMEL-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6629. Resolution: Fixed Fix Version/s: 2.12.0 2.11.2 There is now options to make it easier to setup these settings on the jetty component. Add requestBufferSize and requestHeaderSize options for jetty - Key: CAMEL-6629 URL: https://issues.apache.org/jira/browse/CAMEL-6629 Project: Camel Issue Type: Improvement Components: camel-jetty Affects Versions: 2.10.4, 2.11.1 Reporter: Pratyusha Ghosh Assignee: Claus Ibsen Fix For: 2.11.2, 2.12.0 Add requestBufferSize and requestHeaderSize options for jetty server to allow configuration of allowable request header limit This option is exposed by standalone jetty server but not exposed by camel-jetty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6640) Migrate XML Security key cipher algorithm away from RSA v1.5
Colm O hEigeartaigh created CAMEL-6640: -- Summary: Migrate XML Security key cipher algorithm away from RSA v1.5 Key: CAMEL-6640 URL: https://issues.apache.org/jira/browse/CAMEL-6640 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.12.0 Currently, the XML Security component uses RSA v1.5 as the default Key Transport algorithm. As there are a number of attacks on this algorithm, it is better to use the RSA OAEP algorithm instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6640) Migrate XML Security key cipher algorithm away from RSA v1.5
[ https://issues.apache.org/jira/browse/CAMEL-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-6640: --- Attachment: camel-6640.patch Please apply the following patch to trunk. It contains the following functionality: a) Some setter methods for the MGFAlgorithm in camel-core, that should have been in my last patch b) Changed the default Key Transport algorithm to use RSA OAEP instead of RSA v1.5 c) Reject requests with RSA v1.5 unless it has been explicitly configured as the key transport algorithm. Colm. Migrate XML Security key cipher algorithm away from RSA v1.5 Key: CAMEL-6640 URL: https://issues.apache.org/jira/browse/CAMEL-6640 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.12.0 Attachments: camel-6640.patch Currently, the XML Security component uses RSA v1.5 as the default Key Transport algorithm. As there are a number of attacks on this algorithm, it is better to use the RSA OAEP algorithm instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
Nigel Longton created CAMEL-6641: Summary: SJMS component throws class cast error when used with IBM Webshpere MQ Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Priority: Minor When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nigel Longton updated CAMEL-6641: - Labels: (was: patch) SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Priority: Minor Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nigel Longton updated CAMEL-6641: - Patch Info: Patch Available SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Priority: Minor Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nigel Longton updated CAMEL-6641: - Attachment: patchfile.txt Created a patch that fixes it on my desktop. SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Priority: Minor Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6014) cxf:rsServer requires class instead of interface in the serviceClass attribute
[ https://issues.apache.org/jira/browse/CAMEL-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741467#comment-13741467 ] Mark Ford commented on CAMEL-6014: -- I will try to add a test case shortly. However, you must still specify a class for serviceClass. The CxfRsInvoker only overrides performInvocation so its super class will have already created the serviceClass instance in order to pass to this method. The CxfRsInvoker actually uses this serviceClass object to invoke the method if it's a sub resource locator. cxf:rsServer requires class instead of interface in the serviceClass attribute -- Key: CAMEL-6014 URL: https://issues.apache.org/jira/browse/CAMEL-6014 Project: Camel Issue Type: Improvement Components: camel-cxf Affects Versions: 2.10.3 Reporter: Jason Chaffee See Issue CAMEL-4014 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller reassigned CAMEL-6641: --- Assignee: Christian Müller SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Assignee: Christian Müller Priority: Minor Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6641: Fix Version/s: 2.12.0 2.11.2 SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Assignee: Christian Müller Priority: Minor Fix For: 2.11.2, 2.12.0 Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-6641. - Resolution: Fixed SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Assignee: Christian Müller Priority: Minor Fix For: 2.11.2, 2.12.0 Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6641) SJMS component throws class cast error when used with IBM Webshpere MQ
[ https://issues.apache.org/jira/browse/CAMEL-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741538#comment-13741538 ] Christian Müller commented on CAMEL-6641: - Thanks Nigel for the patch! It's applied into the master and the camel-2.11.x maintenance branch. SJMS component throws class cast error when used with IBM Webshpere MQ -- Key: CAMEL-6641 URL: https://issues.apache.org/jira/browse/CAMEL-6641 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 2.11.1 Environment: Windows 7 Reporter: Nigel Longton Assignee: Christian Müller Priority: Minor Fix For: 2.11.2, 2.12.0 Attachments: patchfile.txt When using the IBM MQ JMS classes and pub/sub over a TOPIC the JmsObjectFactory.createMessageConsumer method throws a cast class exception. The session is being cast to a TopicSession which for MQ it is not. Using pure jms this cast is not required as the session class is aware of the destination type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
