Uploaded image for project: 'Axiom'
  1. Axiom
  2. AXIOM-334

Prefix mismatch of OMSourcedElement

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      Discussion here - http://markmail.org/message/ks7taa4upual3ufj

      ============== Text from initial email ==================
      Hi folks,

      I am facing prefix mismatch problem of OMSourcedElement. If we get a
      prefix from non-expanded OMSE by using OMSE.getNamespace().getPrefix(),
      the returned prefix is "". But if we get the prefix from expanded OMSE,
      then the returned prefix is "ns1". The first default OMNamespace is set by
      OMSE creater (can be outside of axiom and axis2) through constructor
      argument, The second OMNamespace is created from OMDatasource when it is
      expanded. Since these two OMNamespace are created by different ways, the
      prefixes can be mismatch.

      OMSourcedElement should return the same data regardless of whether it is
      expanded or not. I think the OMNamespace should not be provided by
      Constructor, but should be provided by OMDataSource to avoid such prefix
      mismatch, otherwise we have to expand OMSourcedElement when getNamespace()
      is invoked. I am not sure there are other ways to avoid this problem...

      ============== Text from initial email ==================

      Attachments

        Activity

          People

            scheu@us.ibm.com Rich Scheuerle
            dims Davanum Srinivas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: