Hi Richard, I was actually thinking more of Dean's case where, if I got it right, he just needs to refresh the browser subapp view, i.e. the tree list of a content app after his custom action has changed the underlying repository.
You, instead, have added a custom action to the Pages detail subapp, so the content which should refresh is the the page being edited. Indeed, AbstractRepositoryAction is of no use in your case. What you need to do is to ensure that your action fires a ContentChangeEvent on the subapp eventbus (inject in its constructor something like [code]@Named(SubAppEventBus.NAME) EventBus subAppEventBus[/code]) so that eventually it's PageEditorPresenter to handle the event and refresh the view. HTH, Federico -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=4ac3261f-9e28-4546-a32d-cdc561af07bf ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
