[
https://issues.apache.org/jira/browse/TUSCANY-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724440#action_12724440
]
Simon Laws commented on TUSCANY-3099:
-------------------------------------
Scott's right. The OASIS spec tightens this up as this is driving an underlying
JMS API that expects a number. I think we should stick with this restriction
but we could put some validation in that gives a more sensible message if you
don't put a number in. Sound ok?
> NumberFormatException occurs when parsing a JMSPriority attribute with string
> value
> -----------------------------------------------------------------------------------
>
> Key: TUSCANY-3099
> URL: https://issues.apache.org/jira/browse/TUSCANY-3099
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-1.5
> Reporter: Andrew Mak
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
