[
https://issues.apache.org/jira/browse/GERONIMO-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725387#action_12725387
]
David Jencks commented on GERONIMO-4628:
----------------------------------------
Adding a method to ConfigurationStore is just not acceptable to solve this.
Deployer has access to the DeploymentContext. I think you can use one of the
deploymentContext.addFile methods to add the plan without changing any apis. I
think this could be called right after Deployer line 256.
> 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.
