This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 75581 - NB55 Entpak/TPR3: Schema Columns View shows unbound global element
Summary: NB55 Entpak/TPR3: Schema Columns View shows unbound global element
Status: VERIFIED INVALID
Alias: None
Product: xml
Classification: Unclassified
Component: Schema Tools (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: bhate
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-26 19:25 UTC by Ayub Khan
Modified: 2006-10-05 21:48 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ayub Khan 2006-04-26 19:25:33 UTC 
After I tried to add a global element that is not bound to a namespace in the
Text veiw and switched to Schema Columns, Columns View shows global element even
though the element is invalid for this given schema.

See For eg:-

<schema xmlns="http://www.w3.org/2001/XMLSchema"
       xmlns:po="http://www.example.com/PO1"
       targetNamespace="http://www.example.com/PO1"
       elementFormDefault="unqualified"
       attributeFormDefault="unqualified">

<xsd:element name=something"/>
</schema> 

here <xsd:element name=something"/> is not bound.

Ideally schema model should not add this as a valid element.
Comment 1 Chris Webster 2006-07-11 16:44:51 UTC 
The targetNamespace applies to all global elements and attributes regardless of
whether formDefault is qualified or unqualified. The formDefault is applied to
locally defined elements and attributes which may not require qualification
depending on the value of the form default. The schema below requires that
something be defined in the targetNamespace. Local elements do not require
qualification.
Comment 2 Ayub Khan 2006-10-05 21:48:35 UTC 
I agree this is not a valid issue.