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 2004/11/06 18:27:32 UTC
[jira] Created: (GERONIMO-449) New CLI deployer should accept foreign JAR file not impl class
New CLI deployer should accept foreign JAR file not impl class
--------------------------------------------------------------
Key: GERONIMO-449
URL: http://nagoya.apache.org/jira/browse/GERONIMO-449
Project: Apache Geronimo
Type: Improvement
Components: deployment
Versions: 1.0-M3
Reporter: Aaron Mulder
Priority: Minor
The --driver option should take a JAR file not a driver class. It's not obvious how to add a foreign driver to the CLASSPATH otherwise (because we use a teeny JAR which itself uses manifest Class-Path entries). This option should:
- prepare a classloader including the driver JAR and its manifest Class-Path entries
- identify and load the DeploymentFactory impl listed in the JSR-88 entry in the manifest file (or if it's not there, give an informative error message)
- register the DeploymentFactory (if the spec doesn't say it should do that itself)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-449) New CLI deployer should accept foreign JAR file not impl class
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-449?page=comments#action_55227 ]
Aaron Mulder commented on GERONIMO-449:
---------------------------------------
Still doesn't handle manifest classpath, but the help says that
> New CLI deployer should accept foreign JAR file not impl class
> --------------------------------------------------------------
>
> Key: GERONIMO-449
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-449
> Project: Apache Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Minor
> Fix For: 1.0-M3
>
> The --driver option should take a JAR file not a driver class. It's not obvious how to add a foreign driver to the CLASSPATH otherwise (because we use a teeny JAR which itself uses manifest Class-Path entries). This option should:
> - prepare a classloader including the driver JAR and its manifest Class-Path entries
> - identify and load the DeploymentFactory impl listed in the JSR-88 entry in the manifest file (or if it's not there, give an informative error message)
> - register the DeploymentFactory (if the spec doesn't say it should do that itself)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-449) New CLI deployer should accept foreign JAR file not impl class
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-449?page=history ]
Aaron Mulder closed GERONIMO-449:
---------------------------------
Assign To: Aaron Mulder
Resolution: Fixed
Fix Version: 1.0-M3
> New CLI deployer should accept foreign JAR file not impl class
> --------------------------------------------------------------
>
> Key: GERONIMO-449
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-449
> Project: Apache Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Minor
> Fix For: 1.0-M3
>
> The --driver option should take a JAR file not a driver class. It's not obvious how to add a foreign driver to the CLASSPATH otherwise (because we use a teeny JAR which itself uses manifest Class-Path entries). This option should:
> - prepare a classloader including the driver JAR and its manifest Class-Path entries
> - identify and load the DeploymentFactory impl listed in the JSR-88 entry in the manifest file (or if it's not there, give an informative error message)
> - register the DeploymentFactory (if the spec doesn't say it should do that itself)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira