[shrinkwrap-issues] [JBoss JIRA] (SHRINKDESC-128) Missing attributes
[
https://issues.jboss.org/browse/SHRINKDESC-128?page=com.atlassian.jira.pl...
]
Jesper Pedersen commented on SHRINKDESC-128:
--------------------------------------------
The "id" attribute is part of the specification, and hence the XSD.
And at least one vendor is making heavy use of it.
The metadata parser should follow the XSD, and not make any assumptions on what is being
used and what isn't.
Missing attributes
------------------
Key: SHRINKDESC-128
URL: https://issues.jboss.org/browse/SHRINKDESC-128
Project: ShrinkWrap Descriptors
Issue Type: Bug
Components: metadata-parser
Affects Versions: 2.0.0-alpha-3
Reporter: Jesper Pedersen
Assignee: Ralf Battenfeld
Fix For: 2.0.0-alpha-4
The connector XSD defines
{noformat}
<xsd:complexType name="config-propertyType">
<xsd:sequence>
<xsd:element name="description"
type="j2ee:descriptionType"
minOccurs="0"
maxOccurs="unbounded"/>
<xsd:element name="config-property-name"
type="j2ee:config-property-nameType"/>
<xsd:element name="config-property-type"
type="j2ee:config-property-typeType"/>
<xsd:element name="config-property-value"
type="j2ee:xsdStringType"
minOccurs="0">
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
{noformat}
However, the metadata parser doesn't generate methods to allow access to
"id"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira