On 5/12/06, Paul McMahan <[EMAIL PROTECTED]> wrote:
Also, I think you (or someone) mentioned earlier that it might be useful to make this utility available from the admin console. Seems like one reasonable approach would be to enable the current application deployment portlet to detect when a backlevel plan is provided (assuming that's always possible) and invoke your utility to provide a head start on creating a new plan. If there's consensus around that idea then I can help with the UI.
I attached a patch to GERONIMO-2006 that implements this idea. When a deployment fails the console looks for a configId attribute in the plan and if found provides the user with a new plan generated by the upgrader. They can edit the upgraded plan in place and save it locally. In some cases (welcome app, jmx-debug, and others) the upgraded plan needs no further editing so the user can save the plan and then immediately deploy again from the same portlet. In some cases (daytrader) manual editing is required but the upgraded plan at least provides a starting place. Best wishes, Paul
Paul On 5/12/06, David Jencks <[EMAIL PROTECTED]> wrote: > I put the upgrade jar at > > http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar > > It would be very helpful to find out to what extent this works in > real life. > > It's supposed to include all the classes it needs (that's why its so > big) > > usage: > > java -jar geronimo-upgrade-1.1-SNAPSHOT.jar <path to source plan> > [<path to target plan>] > > if you leave out the target, you'll get output in the same directory > as the source. > > thanks > david jencks > >
