Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 257165 - navigation context objects should be accessible via key (-> change context model from object to map)
Summary: navigation context objects should be accessible via key (-> change context mo...
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: navigation (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-02 04:34 EST by Holger Hoch CLA
Modified: 2009-01-15 17:37 EST (History)
0 users

See Also:

Attachments
implements proposed changes (41.65 KB, patch)
2008-12-02 04:34 EST, Holger Hoch CLA 		christian.campo: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Hoch CLA 2008-12-02 04:34:16 EST 
Build ID: xxx

Steps To Reproduce:
none

More information:
- the navigation context should be a map and objects within the context should therefore be accessible via a key, eg getContext("riena.example.customer")
- the parameter slot of the navigation argument should be stored within the context (proposed key: "riena.navigation.parameter")
- the attribute 'typeId' of the assembly element is not named correctly anymore -> rename to 'id'
- adjust examples
- make NavigationProcessorTest run successfully
Comment 1 Holger Hoch CLA 2008-12-02 04:34:55 EST 
Created attachment 119242 [details]
implements proposed changes
Comment 2 Christian Campo CLA 2008-12-02 04:52:02 EST 
patch modified to only allocate context in NavigationNode if needed