Uploaded image for project: 'SwitchYard'
  1. SwitchYard
  2. SWITCHYARD-365

targetNamespace is being ignored by NamedModel.getQName()

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.1
    • Fix Version/s: 0.2
    • Component/s: configuration
    • Labels:
      None

      Description

      The QName returned by NamedModel.getQName() should have a namespaceURI of the targetNamespace of the application. Currently, "" is being returned.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            dward David Ward added a comment -

            SWITCHYARD-351 fixed the issue where the targetNamespace attribute was being lost, however now we need to actually USE it in NamedModel.getQName().

            Show
            dward David Ward added a comment - SWITCHYARD-351 fixed the issue where the targetNamespace attribute was being lost, however now we need to actually USE it in NamedModel.getQName().
            Hide
            dward David Ward added a comment - - edited

            (comment removed)

            Show
            dward David Ward added a comment - - edited (comment removed)
            Hide
            kcbabo Keith Babo added a comment -

            Pull requests have been closed as David is adding more.

            Show
            kcbabo Keith Babo added a comment - Pull requests have been closed as David is adding more.
            Hide
            dward David Ward added a comment -

            https://github.com/jboss-switchyard/core/pull/271
            https://github.com/jboss-switchyard/components/pull/206
            https://github.com/jboss-switchyard/quickstarts/pull/64

            This change bubbled out in a big way, mainly because of the how we keep track of service references based on the qname of services (which are NamedModels).

            With this change, it is important to note that ALL test switchyard.xml files are now validated against the schemas. This turned up MANY bad xml files we had, which are now fixed. In the future, it is important to realize that:
            1) <implementation>s must come before <service>s and <reference>s inside a <component>.
            2) <reference>s must have a multiplicity attribute. For now, we just use multiplicity="1..1".
            3) <composite> <service>s must have a promote attribute. It should be equal to the <component> name, or the <component> name / (slash) <component> <service> name.
            4) <composite>s must have both name and targetNamespace attributes defined.

            Show
            dward David Ward added a comment - https://github.com/jboss-switchyard/core/pull/271 https://github.com/jboss-switchyard/components/pull/206 https://github.com/jboss-switchyard/quickstarts/pull/64 This change bubbled out in a big way, mainly because of the how we keep track of service references based on the qname of services (which are NamedModels). With this change, it is important to note that ALL test switchyard.xml files are now validated against the schemas. This turned up MANY bad xml files we had, which are now fixed. In the future, it is important to realize that: 1) <implementation>s must come before <service>s and <reference>s inside a <component>. 2) <reference>s must have a multiplicity attribute. For now, we just use multiplicity="1..1". 3) <composite> <service>s must have a promote attribute. It should be equal to the <component> name, or the <component> name / (slash) <component> <service> name. 4) <composite>s must have both name and targetNamespace attributes defined.
            Hide
            kcbabo Keith Babo added a comment -

            pushed

            Show
            kcbabo Keith Babo added a comment - pushed

              People

              • Assignee:
                dward David Ward
                Reporter:
                dward David Ward
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development