Uploaded image for project: 'Tuscany'
  1. Tuscany
  2. TUSCANY-4001

Error handling in JMSBindingProcessor.read could be improved for UnexpectedElement

    XMLWordPrintableJSON

Details

    Description

      Error handling in JMSBindingProcessor.read could be improved for UnexpectedElement. For example, when processing a .composite file which contained "wireFormat.jmsdefault" in the Tuscany namespace the following exception was thrown:

      Incomplete binding.jms definition found unexpected element: org.apache.tuscany.sca.assembly.impl.ExtensionImpl@21e7c65

      (FYI, the correct element should have been "wireFormat.jmsDefault" in the OASIS SCA namespace.)

      I had to run with a debugger to determine what the offending element was. It would be more useful to know the QName rather than the classtype & hash code.

      Attachments

        Activity

          People

            aelder ant elder
            jennthom Jennifer Thompson
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: