Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <628492528.1245750607798.JavaMail.jira@brutus>
Date: Tue, 23 Jun 2009 02:50:07 -0700 (PDT)
From: "Rex Wang (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-4628) Console plan wizards need to save
 plans
In-Reply-To: <1009325868.1242347805597.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GERONIMO-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723020#action_12723020 ] 

Rex Wang commented on GERONIMO-4628:
------------------------------------

Currently, there are only RepositoryConfigurationStore and geronimo-farm's MasterConfigurationStore, different store might have different behavior when deploy packages.
I think the "save plan" action is better to go along with the action that intalling the config.ser. 
So in the Deployer, after store.install(configurationData) which will generate the config.ser, config.info, I add the store.savePlan(configurationData, planFile).

-Rex


> Console plan wizards need to save plans
> ---------------------------------------
>
>                 Key: GERONIMO-4628
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4628
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: David Jencks
>            Assignee: Rex Wang
>             Fix For: 2.1.5, 2.2
>
>         Attachments: GERONIMO-4628-b21.patch
>
>
> Currently we have a lot of console wizards that are great at creating basic plans for datasources, security realms, etc etc.  However once you've deployed the plan through the wizard the plan is gone gone gone never to be seen again.
> The wizards need to do _something_ so the plans are saved on disk somehow.
> One possibliity is that deployment could always save the plan into the car file, like the car-maven-plugin does.  I'm not certain but I think this would fix the admin console wizard problem as well.
> Also it would be very handy if the wizard inserted a comment mentioning the intended target artifact, such as which tranql adapter to use for a datasource plan.
> Furthermore you ought to be able to specify all components of the artifact id (groupId, etc) in all the wizards.  In fact you should be able to set the default groupId for the whole admin console -- probably your company wants all the groupIds the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.