You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until recently I worked with single schema file and root-element as first element in file. "add selected top-level element" to diagram works great and I can expand the visualization.
Now IT tells me to work with imported schema for signature. I have the problem that default selected top-level element is now picked from signature schema, rather than from my payload schema. Can I apply naming convention on schema or element, or modify the import statement in payload schema to get back the earlier behavior: default selected top level element is first element in payload schema?
Until recently I worked with single schema file and root-element as first element in file. "add selected top-level element" to diagram works great and I can expand the visualization.
Now IT tells me to work with imported schema for signature. I have the problem that default selected top-level element is now picked from signature schema, rather than from my payload schema. Can I apply naming convention on schema or element, or modify the import statement in payload schema to get back the earlier behavior: default selected top level element is first element in payload schema?
example payload (you need to download the schema first): https://pinggg.mywire.org/Alpha/IATA_Baggage_BagRQ.xsd
signature schema: https://pinggg.mywire.org/Alpha/xmldsig-core-schema.xsd, or https://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd
Element to root the diagram: IATA_Baggage_BagRQ
The text was updated successfully, but these errors were encountered: