deployment behavior

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

deployment behavior

Pavel Perikov-2
Create a package, create a subclass of ConsoleSessionManager, put it in the
package. Select 'deploy executable', then 'Save Settings'.
Delete session manager class. Select 'Deploy executable'. You'll get a
walkback.

Yours, Pavel


Reply | Threaded
Open this post in threaded view
|

Re: deployment behavior

Blair McGlashan
"Pavel Perikov" <[hidden email]> wrote in message
news:[hidden email]...
> Create a package, create a subclass of ConsoleSessionManager, put it in
the
> package. Select 'deploy executable', then 'Save Settings'.
> Delete session manager class. Select 'Deploy executable'. You'll get a
> walkback.

Then don't delete the SessionManager class.

More seriously, the image stripper setup for a package is stored in a
serialized form because this allows one to load the package into a system
without Dolphin Professional's application deployment capabilities, save it,
and reload it into DPro retaining the original image stripper settings.
However, as a result, there will be no obvious references to (or instances
of) of the SessionManager class, and so the system will not know to warn you
not to uninstall it. I hardly think this is a big issue though.

Regards

Blair