[ 
https://issues.apache.org/jira/browse/TUSCANY-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724519#action_12724519
 ] 

Andrew Mak commented on TUSCANY-3098:
-------------------------------------

Hi Simon, can you post the link to the 1.x schema?  The one I checked here:  
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-spec.html 
does not have a use="required" on the property name (so it defaults to 
optional):

  <complexType name="BindingProperty">
      <simpleContent>
         <extension base="string">
            <attribute name="name" type="NMTOKEN"/>
            <attribute name="type" type="string" use="optional"
                       default="xs:string"/>
         </extension>
      </simpleContent>
   </complexType>

The binding fragment I have is below; it's not a complete configuration as I 
was in the middle of editing it, but it should be valid w.r.t to the schema 
(the property name aside).

  <binding.jms>
    <destination name="dest">
      <property></property>
    </destination>
  </binding.jms>

> 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.

Reply via email to