Explicit namespace prefix control in Aegis xml files is disabled by BeanType
----------------------------------------------------------------------------
Key: XFIRE-815
URL: http://jira.codehaus.org/browse/XFIRE-815
Project: XFire
Issue Type: Bug
Components: Aegis Module
Affects Versions: 1.2.3
Environment: not relevant
Reporter: benson margulies
Assigned To: Dan Diephouse
Consider an Aegis file like:
<mappings xmlns:btrnm="urn:com.basistech.rnm">
<mapping name="btrnm:Name">
<!-- without this, the XML must contain an array, even if the array is
zero-length. -->
<property name='transliterations' mappedName='btrnm:transliterations'
minOccurs='0' nillable='true' />
</mapping>
</mappings>
According to the doc, this is requesting that the corresponding type live in
the specified namespace, and use the specified prefix. And all is well until
the code gets into BeanType.writeSchema.
The code here goes out of its way to discard this prefix and use a unique one
at the schema level. Maybe this is on purpose, but it's inconvenient.
String nameNS = name.getNamespaceURI();
String nameWithPrefix = getNameWithPrefix(root, nameNS,
name.getLocalPart());
String prefix = NamespaceHelper.getUniquePrefix((Element)
root.getParent(), type
.getSchemaType().getNamespaceURI());
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
