Closed Bug 285625 Opened 20 years ago Closed 20 years ago

Handling schemas without targetNamespace doesn't work

Categories

(Core Graveyard :: Web Services, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 285751

People

(Reporter: doronr, Unassigned)

Details

http://www.w3.org/TR/xmlschema-1/#declare-schema (scroll down a bit) "Since the empty string is not a legal namespace name, supplying an empty string for targetNamespace is incoherent, and is not the same as not specifying it at all. The appropriate form of schema document corresponding to a ·schema· whose components have no {target namespace} is one which has no targetNamespace attribute specified at all." This seems to imply that no targetNamespace is fine, and that type="foo" would match that schema. So currently, in nsSchemaLoader: http://lxr.mozilla.org/seamonkey/source/extensions/webservices/schema/src/nsSchemaLoader.cpp#805 we get an "" key, and nsCOMPtr<nsISchema> os = do_QueryInterface(old); returns an actual object, so we return out of the method. And mSchemas seems to have a entry length of 1, which I guess is created with key "". So, what should we do? I can't figure where that empty key item is coming from. So, should we, if no targetNamespace is found, make the value of the key be something ("-moz-no-target-namespace")?
bug is fixed by 285751 *** This bug has been marked as a duplicate of 285751 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.