web dynpro notes

visual part and programatic part
external visible and internal visible.
one to one bwtween interface view and window
component can has exactly one interface controller , 0 or more interface view
parent can call child and child can react to parent's event.
interface controller can only instantiated when used as child of another component.
interface view -> web dynpro framework.
an application is an url that defines the entry point into web dynpro components.
 the only entity can be accessed by url.
 often 1:1 to view
 define: the component to invoke(root component) ; initial view of the root component; inbound plug

with startup checkbox selected.

in eclipse:
 project: can contains many webdynpro app.
 webdynpro :
  application; entry point accessed by url.
  model; 
  component interface; (interface needed to implemented by all the components)
  components:(business logic , not accessible by url)
   component controller;  (created default to drive the entire component)
   component interfaces;(interface present to web dynpro framework or other component)
   custom controllers; (encapsure non user interaction logic. added to optimize or simplify

the application)
    interface controller:can accessed by other components.
   messagepool;
   used models;
   used webdynpro components;
   views; (user interactive) means viewcontroller
   windows; (view assambly, must contain at least one view)
 dictionary: local(all used ); seperated dictionary per object;
 src: configurations; mimes; packages(metadata not java code.)

 componentName/componentInterface/InterfaceViews/<WindowName>InterfaceView  

componentName/windows/<WindowName>
 the aboving two are one and the same entity.  the first is used for Web Dynpro framework and the second is

used for programatic access.
 
 

cusom controller archtecture.
[context,instance method,events,required controllers]
1.instantiated as singletons respect to their parent component
2.instantiated by web dynpro framework, and the order is undefined.
3.store runtime data in context,and by default is private.
4.lifespane of a component is equal to that of a component controller.
5.interface controller exist as long as the component usage exist.

view controller architecture.
[content,instance method,events,required controllers,Actions,Navigation plugin,layout]
1.singletons
2.context,not share data.
3.interface controller has no hooked method nor has context.

windows,view set,view area
1.window can have 0 or more view sets.
2.view sets can be subdivided into several view area.
3.an view area can have one or more views or view sets , but can only display onne.

4.when define a window , you defined all possible views , their layout and the navigation link.
5.empty view.

 

view assembly
1.the subset of vies visible at any one time(active views).

navigation between views
1.inbound and outbound to entry and exit.
2.double click or right mouse->open navigation modeler on window.
3.example:
 customListView,customSeachView,customDetailView,
4:
 outbound: call an outbound plug causes a navigation event to be raised. navigation queue.
 inbound: called when related outbound event be processed.
 link: input subscribe event of output.

 

context mapping:
1.share data between controllers.
2.Terminology: Internal Mapping(both controllers are in the same component)
  External Mapping.
  Mapping Origin Node, Mapped Node.
3.Prerequirement:
 1.the node exists.
 2.origin must be custom controller
 3.mapped controller must use source controller

data binding: putting data on the screen.