This is a test message to test the length of the message box.
Login
|

Write a comment

Writing comments is only allowed to registered users, registration is free and does not require an email address and can be done quickly here.

ABAP Cloud - How read multiple namespace in XSD

spera_marco - 08/01/2025 - 12:04

Hi,

How do I read multiple xmlns namespaces prefixed with an xsd file using the abap cl_sxml_string_reader class?

Here's an example:

  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
             xmlns:ns1="http://example.com/ns1"
             xmlns:ns2="http://example.com/ns2"
             targetNamespace="http://example.com/ns1">
  </xs:schema>`.

Thanks in advance.

Xexer - 08/01/2025 - 16:04

Hello Marco,

the class reads the XML structure node by node, so you get the namespace of the actual node returned. So you can parse or do with the node what you need to do. All the informations are filled into the fields of the object.

Greetings Björn

spera_marco - 08/01/2025 - 17:44

Hello Bjorn, i developed this demo report.

If you try to debug, you will be able to notice that you don't able to read the attribute xmlns:myns="http://www.w3.org/2001/XMLSchema".

By your experience there is a way to resolve this.

Thank in advance.

REPORT ztest_namespace.

DATA(lv_xsd_string) =
  `<xs:schema xmlns:myns="http://www.w3.org/2001/XMLSchema" ` &&
  `           xmlns="http://www.example.com/myns" ` &&
  `           xmlns:xs="http://www.example.com/default" ` &&
  `           targetNamespace="http://www.example.com/default">` &&
  `</xs:schema>`.

DATA(reader) = cl_sxml_string_reader=>create( cl_abap_codepage=>convert_to( lv_xsd_string ) ).

WHILE reader->node_type <> if_sxml_node=>co_nt_final.
  reader->next_node( ).

  DATA(output) = |Namespace: { reader->nsuri }, Name: { reader->name }, XML Type: { reader->xml_type }, Node Type: { reader->node_type }, Prefix: { reader->prefix }|.
  output &&= | Value: { reader->value }, Value-Raw: { reader->value_raw }, Value-Type: { reader->value_type }, Offset: { reader->get_byte_offset( ) }|.

  WRITE: / output.

  IF reader->node_type = if_sxml_node=>co_nt_element_open.

    reader->next_attribute( ).
    WHILE reader->node_type = if_sxml_node=>co_nt_attribute.

      output = |Namespace: { reader->nsuri }, Name: { reader->name }, XML Type: { reader->xml_type }, Node Type: { reader->node_type }, Prefix: { reader->prefix }|.
      output &&= | Value: { reader->value }, Value-Raw: { reader->value_raw }, Value-Type: { reader->value_type }, Offset: { reader->get_byte_offset( ) }|.

      WRITE: / output.
      reader->next_attribute( ).

    ENDWHILE.

  ENDIF.

ENDWHILE.

Xexer - 08/04/2025 - 09:17

Hello Marco,

from my perspective this a correct behavior. The tag uses the namespace XS, so the namespace for this is http://www.example.com/default. The framework uses the namespace definition, but you can't read it because it's not part of the XML content. If you define a node in the XML that uses the namespace, it will also be listed as a namespace.

In yor example 'targetNamespace' is a normal attribute, so you read it. The namespace of the node is assigned there and it's still XS.

Hope this helps you.

Greetings Björn