I don't think that would be such a bad idea -- storing the original plan in the config-store somewhere.
Aaron On 11/17/05, David Jencks <[EMAIL PROTECTED]> wrote: > > On Nov 17, 2005, at 4:45 AM, Vamsavardhana Reddy wrote: > > > If deployment plans are inside the archive (ear, war, etc.) they can > > be obtained from config-store. If the deployment plan is supplied as > > an external file to the deployer and if the original file is not > > available, the only way to get any information on the configuration is > > from the Configuration GBeanData obtained from the kernel at runtime > > or from deserializing config.ser files under config-store. For > > analyzing any problems after an application is deployed, deployment > > plans will certainly be helpful. > > If you think this is really valuable information, I think a better > approach is to store the plan(s) in a known location in the > configuration so they may be retrieved directly. > > thanks > david jencks > >
