Hi Sanjiva, all: Sanjiva Weerawarana wrote:
+1 .. plus, IMO OMNamespace.getName() is in fact the right name .. the namespace URI is called the namespace name isn't it??
That's a terrible spec-ese term, though. It's like SOAP header vs. SOAP header block - everyone calls individual headers "SOAP headers". Everyone calls namespaces either "namespaces" or "namespace URIs".
namespaceURI() was/is the right name when you ask someone else (like an element) for its NSURI, but when you're talking to the OMNamespace node what we have now seems ok to me.
I think that's a stretch. :) To me, getName() says "get a javax.xml.soap.Name", or "get a simple string name for this object", neither of which feels right here.
Really, getNamespaceName() would even be better. getNamespace() is also fine, although since we're in an OMNamespace object that feels a little weird to me. getNamespaceURI() matches QName, OMElement, MessageElement from Axis1, NamespaceContext, SOAPElement from SAAJ, etc... that would be my preference.
Personally, I agree with Ruchith and think that interface renames like this should happen before 1.0.
--Glen
