You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/08/06 02:10:13 UTC
[jira] Created: (GERONIMO-2286) app client plan still uses Strings
for dependency Module IDs
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
[jira] Updated: (GERONIMO-2286) app client plan still uses Strings
for dependency Module IDs
Posted by "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.
[jira] Updated: (GERONIMO-2286) app client plan still uses Strings
for dependency Module IDs
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-2286:
-----------------------------------
Fix Version/s: (was: 2.0.x)
updated Fixed For field
> 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
> Assignee: David Jencks
> Fix For: 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.
[jira] Closed: (GERONIMO-2286) app client plan still uses Strings
for dependency Module IDs
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-2286.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.x)
2.0.x
Fixed in trunk rev 561259
Fixed in 2.0 rev 561286
Fixed in daytrader (schema mods) rev 561287.
Use PatternType element for external rars, and external paths, and cook up an ArtifactResolver so you can leave bits out. This means client_artifact_aliases.properties will be used when available to help with app client deployment.
> 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
> Assignee: David Jencks
> Fix For: 2.0, 2.0.x
>
>
> 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.
[jira] Updated: (GERONIMO-2286) app client plan still uses Strings
for dependency Module IDs
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2286?page=all ]
Vamsavardhana Reddy updated GERONIMO-2286:
------------------------------------------
Fix Version/s: 1.x
2.0
(was: 1.2)
> 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.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.
-
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
[jira] Assigned: (GERONIMO-2286) app client plan still uses Strings
for dependency Module IDs
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-2286:
--------------------------------------
Assignee: David Jencks
> 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
> Assignee: David Jencks
> 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.