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/04/15 21:16:00 UTC

[jira] Assigned: (GERONIMO-1859) Should be able to pass a JAR when deploying a service

     [ http://issues.apache.org/jira/browse/GERONIMO-1859?page=all ]

Aaron Mulder reassigned GERONIMO-1859:
--------------------------------------

    Assign To: Aaron Mulder

> Should be able to pass a JAR when deploying a service
> -----------------------------------------------------
>
>          Key: GERONIMO-1859
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1859
>      Project: Geronimo
>         Type: Improvement
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>      Fix For: 1.1

>
> When you deploy a service, currently, you have to install a JAR with any class files into the repository and then pass a standalone deployment plan to the deployer (CLI, console, Maven, whatever).  This means redeploy is a multi-step operation (you have to stop the configuration, update the JAR in the repository, and deploy the new plan).
> It should be possible to pass a plan and JAR both to the deployer, and have that JAR supply the classes required for the plan (in addition to any dependencies declared in the plan like normal).  That way redeploy of the JAR and plan together should work.
> It should also be possible to package the plan in the JAR at META-INF/geronimo-service.xml and pass only the JAR to the deployer.

-- 
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