[jira] Updated: (GERONIMO-2286) app client plan still uses Strings for dependency Module IDs

["Prasad Kashyap (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasad Kashyap updated GERONIMO-2286:
-------------------------------------

    Fix Version/s:     (was: 2.0-M5)
                   2.0

> app client plan still uses Strings for dependency Module IDs
> ------------------------------------------------------------
>
>                 Key: GERONIMO-2286
>                 URL: https://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.x, 2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.