The concept of the window controller and window plug is not implemented for Web Dynpro Java in SAP NetWeaver 2004s.
A window has one or several inbound or outbound plugs. Using these plugs, a window can be included into a navigation chain. The concept of these plugs corresponds to the concept of the plug for a view. Each plug of a window is visible within the entire window and can be used for navigating within this window. In addition, one or several plugs can be made accessible to the component interface so that they are visible even beyond the limits of the component in question. They thus belong to the interface view of the relevant window.
If an existing plug of a window is added to the component interface, it is then part of the interface view belonging to this window (see also Interface of a Component).
These interface plugs are required whenever
· A component window is embedded in a window of another component the display at the screen is to navigate there.
· A Web Dynpro application is to be set so that it can be called.
· A Web Dynpro application is to be exited.
Outbound plugs within a window lead from the window to the inbound plug of a view. Using these outbound plugs, it is possible to start navigation within the window with different views instead of using a predefined start view. You set the control as to which outbound plug is called using the event handler method of the called interface inbound plug (see below).
Inbound plugs within a window lead from the outbound plug of a view to the embedding window. Just like all other inbound plugs, they represent an event and thus call the event handler assigned to them. In this way, it is possible to control – within the window controller – which inner outbound plug is to be called next. In this way, you can dynamically define the sequence of the views displayed in the window.
The event handler of an inbound plug can also call an interface outbound plug, for example (see also the section entitled Plugs of the Interface View).