|
|
|
The Model-Driven System Builder
|
|
JeeWiz Architect's Guide
|
|
|
|
Contents >
14. 'Business Object' Reference
|
|
|
14.14 BusinessObject Object
| Superclass | internalClass |
| Subclassed By |
|
| Description | The business object in the business object model embodies the notion of a logical object with
- attributes (from the business object model) and fields (from the Java meta-model)
- methods (from the business object model) and methods from the Java meta-model
- constraints that can apply to the whole holds business object.
If you are used to UML modelling, the business-object maps to the notion of a UML class with the idea that it provides a service outside of a particular location (i.e. package, or EJB container).
The 'access' for these objects is therefore fixed at public.
The business-object is used as a base for entities and sessions, which should be used if applicable in preference to business-object itself.
|
Contained
Lists |
|
| Validation |
The 'extends' attribute is not the name of a class
|
Inherited
properties |
|
14.14.1 Property 'access'
|
| Overrides | java:method.access |
| Description | In the business model, business object/methods and attributes are by definition public - they are designed for access by clients outside the object. Therefore the 'access' value is fixed at 'public'.
This factor hides the 'access' property from users.
However, the attribute can be set programmatically (i.e. in some patterns access is set to private) so that it will be rendered via normal field generators according to the architect's design.
|
| Type | String |
| Default | public |
| Hidden | true |
14.14.2 Property 'group'
|
| Overrides | businessMethod.group |
| Description | A group is a hint to generation scripts as to where to place this object.
It provides an alternative, more flexbile way of grouping business-methods, objects, data-views and pages.
For example, pages for data-maintenance might be in the "DataMaintenance" group,
while specially-designed sessions might be in the "BusinessFunctions" group.
(Expressing this grouping cannot be derived from the hierarchy: all pages are children of a single application.)
Another usage could be to group fields for presentation based on their group name.
The 'group' property should be used to guide presentation to the user, whereas 'style' should be used to guide further pattern generation.
The 'default' group is the null value (script writers must use '#if( !$group )' to identify the default group.
|
| Type | String |
14.14.3 Property 'userNameBase'
|
| Overrides | businessMethod.userNameBase |
| Description | This is the user-visible name for this object (currently it is used on business objects, business-methods and data-views.
In the standard rendering, this is further embellished in component.properties to create the userName, which the user will actually see.
For example, say the name of a session object is AccountTransaction.
Then the default for the user-name-base will be 'Account Transaction'.
This will be embellished in component.properties to give the userName 'Account Transactions'.
Either the userNameBase or the userName can then be used in scripts.
|
| Type | String |
14.14.4 Property 'generatePagesForBusinessMethods'
|
| Description | Set this to 'true' to generate pages based on a business method.
The default for this value (which is true in the standard distribution) comes from the generatePagesForBusinessMethods setting in the system.properties file.
If you want to disable this for a particular object, set the value to 'false'.
The standard pattern triggered by this value creates a page with a single button that will be linked to the business method.
|
| Type | boolean |
| Delegates | true |
Copyright (c) 2001-2008 New Technology/enterprise Ltd.
| |
