app client plan still uses Strings for dependency Module IDs
------------------------------------------------------------
Key: GERONIMO-2286
URL: http://issues.apache.org/jira/browse/GERONIMO-2286
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: application client, deployment
Affects Versions: 1.1
Reporter: Aaron Mulder
Fix For: 1.2
The geronimo-application-client schema has:
<xs:complexType name="resourceType">
<xs:sequence>
<xs:choice>
<xs:element name="external-rar" type="xs:string"/>
<xs:element name="internal-rar" type="xs:string"/>
</xs:choice>
<xs:element ref="connector:connector"/>
</xs:sequence>
</xs:complexType>
That would typically be used like this:
<resource>
<external-rar>tranql/tranql-connector/1.2/rar</external-rar>
<connector ...
</resource>
Everywhere else we've changed elements holding module IDs to be of patternType,
using separate groupId, artifactId, version, and type elements. There's no
reason external-rar should still be a single slash-delimited String here
(though internal-rar should be since it's presumably a path within the JAR?).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
