geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4628) Console plan wizards need to save plans
Date Mon, 22 Jun 2009 08:40:07 GMT


David Jencks commented on GERONIMO-4628:

I'm no longer sure this is a good way to proceed.  This functionality ought to be able to
work with any kind of configuration store, such as one where the plugins are still packed
jars, and we can't write the plan into them.

I now think that each config builder needs to save the plan it comes up with into the configuration.
 The config builder does have write access to whatever its building.

I haven't looked at the code today... maybe the Deployer has access to the DeploymentContext
and can use that to write the plan?

> Console plan wizards need to save plans
> ---------------------------------------
>                 Key: GERONIMO-4628
>                 URL:
>             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.

View raw message