Bug 353329 - Prepare does not work if the parent sub-application not already exists
Summary: Prepare does not work if the parent sub-application not already exists
Status: NEW
Alias: None
Product: Riena
Classification: RT
Component: navigation (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 10:22 EDT by Thorsten Schenkel CLA
Modified: 2011-07-28 10:29 EDT (History)
0 users

See Also:


Attachments
Sample to reproduve the problem (6.91 KB, patch)
2011-07-28 10:29 EDT, Thorsten Schenkel CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Schenkel CLA 2011-07-28 10:22:19 EDT
You have an application with two sub-applications. The 2nd application hasn't been activate yet. You navigate from the first sub-application to a sub-module in the 2nd sub-application. But module-group, module, a sibling sub-module of the sub-module and the sub-application itself are not yet a part of the 2nd sub-application. They will be created and added to the sub-application. Both sub-modules has a flag that informs that prepare is required. But in this scenario prepare does not work.
Maybe a this time not all necessary listeners exists. Usually when a module group is added to a sub-application a method is called that prepares the child nodes. This happens when the the listener ApplicationViewAdvisor.MyModuleGroupNodeListener handles the event parentChanged. But parentChanged isn't called in this scenario.
Comment 1 Thorsten Schenkel CLA 2011-07-28 10:29:25 EDT
Created attachment 200531 [details]
Sample to reproduve the problem

After starting the SWT Example Client activate "Navigate".
Click "Navigate to shared, prepared..."
Sub-Application will be activated. At the end of the navigation you will find the module "SharedPrepared". Both sub-modules have the flag "requiredPrepare". But the sub-module "Date" is not prepared at this moment. The sub-module has no marker. After activation of the sub-module you can see the error marker in the navigation tree. But this is too late.