[Seaside] How to reverse unregister handler?
Philippe Marschall
philippe.marschall at gmail.com
Sun Oct 23 15:43:49 UTC 2011
2011/10/22 Marco A. Gonzalez <marcoinc at mac.com>:
> To prepare my image for deployment, I created a "Developer-Only" page on which I have an anchor whose callback executes the following:
>
> unregisterAllHandlers
> (self confirm: 'Are you sure you want to unregister all handlers. This should only be done on an image that will be deployed. This action is irreversible for this image.')
> ifTrue: [
> WADispatcher default unregister: (WADispatcher default handlerAt: 'examples').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'comet').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'tests').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'tools').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'welcome').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'config').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'status').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'javascript').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'files').
> WADispatcher default unregister: (WADispatcher default handlerAt: 'browse').
> ].
>
> Is there a way to get those handlers back? If so, how is it done?
You can try:
WAEnvironment reloadApplications
> Is the above a reasonable way to "protect the image" in deployment?
As Lukas said we recommend not loading the tests, examples, and tools
into a production image.
Cheers
Philippe
More information about the seaside
mailing list