| Summary: | Invalid namespace of child elements after XML Serialization | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Renat Zubairov <rzubairov> | ||||
| Component: | XML/XMI | Assignee: | Ed Merks <Ed.Merks> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Renat Zubairov
Created attachment 167819 [details]
A project with Extended library tutorial (From galileo) and unit test
Added a project with Extended library tutorial (From galileo) and unit test
I'm not sure why you're expecting the employees element to be qualified. There's no extended meta data annotation that would direct it to be qualified so it's working as expected. I'm not expecting the employees element to be qualified, I'm just expecting it to be inside the same namespace as extlib element, right now it is in "null" namespace which seems to be strange. We also seen the same behaviour for other cases where for example elements inside the feature map are generated with empty namespace. It's supposed to be null because it's supposed to be unqualified. Similarly local element declarations in a complex type will generally be unqualified and hence will also have null namespace. Oh, right. Sorry, got it now. Thnx! |