[
https://issues.apache.org/jira/browse/TUSCANY-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724561#action_12724561
]
Simon Laws commented on TUSCANY-3098:
-------------------------------------
I could fix this but there is another problem hiding. In the code properties
are stored in a map indexed by name. If you put multiple properties in without
a name you'll only get one out. We need to get some clarification from the spec
people about whether a no-name property is valid. I'll ask the question.
> NPE in JMSBindingProcessor writing out property with no name
> ------------------------------------------------------------
>
> Key: TUSCANY-3098
> URL: https://issues.apache.org/jira/browse/TUSCANY-3098
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-1.5
> Reporter: Andrew Mak
>
> We are reading a composite file with a JMS binding into the Tuscany model,
> then trying to write out that model again but ran into an NPE:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.writeBindingProperties(JMSBindingProcessor.java:1266)
> at
> org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.writeDestinationProperties(JMSBindingProcessor.java:1335)
> at
> org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.write(JMSBindingProcessor.java:1006)
> at
> org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor.write(JMSBindingProcessor.java:144)
> at
> org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.write(ExtensibleStAXArtifactProcessor.java:162)
> at
> org.apache.tuscany.sca.assembly.xml.CompositeProcessor.write(CompositeProcessor.java:717)
> It turns out the problem was the JMS binding had a property which is missing
> the name attribute (oddly, the schema allows this...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.