err:XQST0036 no longer exists.
Bug #1043294 reported by
Ghislain Fourny
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zorba |
Fix Released
|
Undecided
|
Markos Zaharioudakis | ||
Bug Description
Following this bug entry:
https:/
the WG has decided to no longer throw err:XQST0036. If I am correct, the engine must be able to deal with a module import (say, A importing B) where B imports and uses types in its signatures that A does not import - provided A does not explicitly use such types.
Revision history for this message
| Sorin Marian Nasoi (sorin.marian.nasoi) wrote | #1 |
| Changed in zorba: | |
| assignee: | Sorin Marian Nasoi (sorin.marian.nasoi) → Markos Zaharioudakis (markos-za) |
Revision history for this message
| Sorin Marian Nasoi (sorin.marian.nasoi) wrote | #2 |
| Changed in zorba: | |
| status: | New → Fix Committed |
| Changed in zorba: | |
| milestone: | none → 2.8 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Ghislain assigned this issue to me because I wrote the test module16 that checks for this error: XQST0036.
@Markos: can you please take a look because AFAIK you implemented the module import feature:
http://
section J.3.1 Substantive Changes:
58. Eliminated err:XQST0036 - implementations must be able to determine whether a type in the schemas of one module is derived from a type in the schemas of another module. Resolves Bug 12173.