[ https://issues.jboss.org/browse/JBIDE-22771?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22771: ------------------------------------- I looked into making a patch for this upstream, but it seems absolutely impossible. One of the general rules is that each page can have children pages. A page can only tell the framework to update itself, or its child pages. There's no way to tell the framework to reload all pages, or to reload the list of children available from the root fragment. In fact, adding such an API could add instability into how the pages are resolved, and what page is the current page. TaskWizardPage is package-private, which means nobody can see it, and looking back through their commit log, this seems 100% intentional. Even if I try to do this 100% in wtp, and keep all changes private in wtp, it still seems virtually impossible to instruct the root fragment of the wizard to re-load its children. The TaskWizard framework simply won't allow it, and that's probably because it's unsafe to make changes to any fragment that isn't in use or its direct children. Sadly, I'm going to have to reject this as won't fix. I know it's not a satisfying answer, but allowing a child fragment to force it's parent to reload / recreate the children just isn't appropriate, and that's the only way to accomplish the fix. -- This message was sent by Atlassian JIRA (v6.4.11#64026)