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 90653 - REGRESSION: Using built-in types makes schema invalid
Summary: REGRESSION: Using built-in types makes schema invalid
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Schema Model (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Nam Nguyen
URL:
Keywords:
: 92271 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-12-06 11:56 UTC by Andrei Chistiakov
Modified: 2007-01-11 04:00 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
patch in xam (2.83 KB, patch)
2006-12-16 00:56 UTC, Nam Nguyen 		Details | Diff
patch in xdm (30.25 KB, patch)
2006-12-16 00:58 UTC, Nam Nguyen 		Details | Diff
patch in schema/api (20.26 KB, text/plain)
2006-12-16 00:59 UTC, Nam Nguyen 		Details
patch in wsdl/api (10.16 KB, patch)
2006-12-16 04:35 UTC, Nam Nguyen 		Details | Diff
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 Andrei Chistiakov 2006-12-06 11:56:38 UTC 
Reproduced in build 061204_17 (JDK 1.6.0-beta2).

To reproduce the bug:
- create a new schema;
- in column view add a new global element of a build-in type (e.g. xsd:decimal)
- validate the schema. The schema becomes invalid because of a prefix that is
not added to "decimal".

src-resolve.4.1: Error resolving component 'decimal'. It was detected that
'decimal' has no namespace, but components with no target namespace are not
referenceable from schema document
'file:/D:/Src/XMLJavaApp/src/pkg4/newXmlSchema.xsd'. If 'decimal' is intended to
have a namespace, perhaps a prefix needs to be provided...
Comment 1 Nam Nguyen 2006-12-06 19:27:41 UTC 
Seems to be a side-effect of the change to schema factory usage of
createElementNS AND change to more agressive namespace consolidation.
Comment 2 Nam Nguyen 2006-12-16 00:53:55 UTC 
The problem is, the agressive namespace consolidation just skipped attribute
values of QName kind  and went on with the refactoring.  This cause the
namespace part of the QName value unresolvable.

The fix is, for domain model to declare list of QName-valued attributes and the
consolidation just go ahead with refactoring the value, if known, or just leave
the in-doubt prefix declaration untouched.
Comment 3 Nam Nguyen 2006-12-16 00:56:34 UTC 
Created attachment 36703 [details]
patch in xam
Comment 4 Nam Nguyen 2006-12-16 00:58:47 UTC 
Created attachment 36704 [details]
patch in xdm
Comment 5 Nam Nguyen 2006-12-16 00:59:34 UTC 
Created attachment 36705 [details]
patch in schema/api
Comment 6 Nam Nguyen 2006-12-16 04:35:14 UTC 
Created attachment 36707 [details]
patch in wsdl/api
Comment 7 Nam Nguyen 2006-12-20 09:37:38 UTC 
Reviewed by Chris, and committed to release551.
Comment 8 Nam Nguyen 2006-12-20 09:38:39 UTC 
closed
Comment 9 Andrei Chistiakov 2006-12-26 12:46:26 UTC 
Verified in build 20061224 (release551).
Comment 10 Nam Nguyen 2007-01-11 04:00:27 UTC 
*** Issue 92271 has been marked as a duplicate of this issue. ***