| Summary: | XML namespace declarations not as documented in 1.0.0.RELEASE | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Gemini.Blueprint | Reporter: | Olaf Otto <olaf> | ||||
| Component: | Core | Assignee: | Glyn Normington <glyn.normington> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | glyn.normington | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 2.0.0.M01 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Olaf Otto
Created attachment 224097 [details]
Example of mixed namespaces from META-INF/spring
I did some experiments which confirmed your finding about the default namespace needing to be blueprint when mixing namespaces. However, this only seemed to work when the blueprint file was in META-INF/spring. See the example attached. Fixed documentation in commit b998e148ba4581429852c88380d277c72e6a39d9. |