The component PAGEBEANCOMPONENT opens up an area into which the dialog of a page bean component is placed.
The page bean component is referenced by attribute PAGEBEANBINDING.
You may define the PAGEBEANCLASS inside the layout definition as well - in this case meta information that is associated with the page bean component is directly shown in side the tool environment.
Typically used attributes
All attributes are
General attributes are
Used inside: ADAPTIVETILECONTAINER, ADAPTIVETOOLBAR, AREASELECTOR, BLOCKABLEAREA, COLSYNCHEDROW, DRAWAREA, FOLDABLEPANEHEADERROW, GRIDCOL, GRIDFOOTER, GRIDHEADER, GRIDHEADERLABEL, GRIDLAYOUTROW, LABELCONTAINER, OVERLAYAREABASEITEM, OVERLAYAREAITEM, PAGEBEANROOT, PAINTAREAITEM, REPEAT, ROW, ROWADAPTIVELINE, ROWFLEXCOLUMNCONTAINER, ROWFLEXLINECONTAINER, ROWFOOTER, ROWHEADER, ROWTITLEBAR, SCHEDULEITEM, SPANGRIDCOL, STABLEAREA, TEXTWITHCONTROLS, TREENODE
Using inside: PAGEBEANCONFIG, PANE
Name of macro that is used for generating certain attributes of this component. Please pay attention: the value of this attribute is read one time for each control and cannot be changed afterwards.
Name that is assigned to the component at client side: there is no specific function associated with the name - but it can be used on client side to describe the component in a clearer way. The name is e.g. used by UI test tools that replay certain user interaction sequences - and that reference components via their name.
Comment that can be asigned to any component. The comment is not operationally used.
Any text | Any text |
Configuration information that is attached to this component. This information is not functionally used by CaptainCasa, but may be used for any application specific purpose.
Binding to a server side object implementing the IPageBean interface.
#{tobedefined} | Binding to IPageBean instance |
Class of the page bean component.
Complex value (name1:value1;name2:value2) that is passed into the initialization of the page bean component.
Reference to an outside object that is the content behind the component. E.g. a field is representing a certain field of a database table: in this case you could define the value table;column. The reference plays a siginficant role within the attributemacro management.
ref | One reference |
ref1;ref2 | Two references |
ref1;ref2;ref3 | Three references |
Flag that indicated if this component is rendered at all. If set to false then the component is not rendered - there is no component data sent to the client.
true | Component is rendered (default) |
false | Component is not rendered |
Deifnition if some (dummy) content is shown if the page bean that is bound is null. If no dummy content is shown, then nothing is show if the page bean is null.
true | Show null content |
false | Show nothing |
If set to true then an user interface update within this component will not cause a rendering of other ROWINCLUDE areas, but will be isolated to this area only.
true | Only updates this area on inner events |
false | Normal update |
If set to true then by default the included page will only be updated in case of UI events that directly happen within this page.
true | Only updated in case of inner events |
false | Always updated (default) |