Given an optional prefix, creates a javax.xml.namespace.QName
from this EName
Given an optional prefix, creates a QName
from this EName
The String
representation, in the format of the javax.xml.namespace.QName.toString
method
The String
representation, in the format of the javax.xml.namespace.QName.toString
method
Expanded name. See http://www.w3.org/TR/xml-names11/. It has a localPart and an optional namespace URI. Semantically like a
QName
in Java, but not keeping the prefix.To get an EName from a QName, the latter needs to be resolved against a Scope.
The short class name illustrates that expanded names are at least as important as qualified names, and should be equally easy to construct (using the companion object).
Typical usage may lead to an explosion of different EName objects that are equal. That is a bit wasteful. Of course the user can define constants for ENames that are used often. Maybe in the future SIP-15 (value classes) can help make ENames completely inlined, thus making it efficient to use them at a large scale.