Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Java-SCA-1.5
-
None
Description
When a JMS binding has a headers/@JMSPriority attribute with a string value, a NumberFormatException occurs when parsing the composite. Looking at the JMS binding spec, @JMSPriority has type string so I don't think it should throw an exception in this case.
The stacktrace:
java.lang.NumberFormatException: For input string: "medium"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.parseOperationHeaders(Unknown Source)
at org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.parseOperationProperties(Unknown Source)
at org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.read(Unknown Source)