geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (GERONIMO-10) Start of JSR-88 Console Deployer
Date Thu, 04 Sep 2003 14:03:11 GMT
The following comment has been added to this issue:

     Author: Aaron Mulder
    Created: Thu, 4 Sep 2003 9:02 AM
The sample XML files were for you to use to try it out.  I don't think they should be committed
yet.  We can put together some JUnit tests that try to load and save the XML files and add
them to the repository at that point.

The way the deployer currently works is that there's a Twiddle command that launches it (o.a.g.command.DeployCommand),
but once launched, all the flow goes through the o.a.g.console.cli classes.  Twiddle does
not seem to offer an interactive mode yet, and even once it does, it wasn't clear to me that
I could "lock the user in" to the deploy area and make them finish their deploy work before
going on to execute other deploy commands, and it wasn't clear whether different deploy-related
commands would be able to share context (such as the current working DD data).  Essentially,
I wanted the deploy commands to be the command-line equivalent of a modal dialog.
View the issue:

Here is an overview of the issue:
        Key: GERONIMO-10
    Summary: Start of JSR-88 Console Deployer
       Type: Improvement

     Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: 1 hour

    Project: Apache Geronimo

   Assignee: Jeremy Boynes
   Reporter: Aaron Mulder

    Created: Sat, 23 Aug 2003 2:39 AM
    Updated: Wed, 3 Sep 2003 11:47 PM

Hook up the JSR-88 DDBeans and DConfigBeans, and start a console-based deployer.  Right now
it just starts navigating the EJB DD and printing info to the screen, but it's enough to show
it working.

This includes:
 - fixes to DDBeans and DConfigBeans to make them work well together
 - a new tool implementation of DeployableObject for EJB JAR (with subclass)
 - a new CLI console package, which right now consists solely of a command-line deployer.
 I assume this will be expanded in the future.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message