JeeWiz Home  
The Model-Driven System Builder

JeeWiz Architect's Guide
 
Contents  >   14.  'Business Object' Reference
 


14.17 DataViewEnd Object

SuperclassbaseViewEnd
Contained
Lists
1
Name  style
Type  String
Inherited from  internalClass
 
2
Name  rolesReadonly
Type  String
Inherited from  entity
 
3
Name  rolesAllowed
Type  String
Inherited from  entity
 
4
Name  rolesBlocked
Type  String
Inherited from  entity
Validation The dataViewEnd's 'view' property does not name a data-view in this jar/assembly
Inherited
properties
name from associationEnd.name

description from baseViewEnd.description

template (base property)

text (base property)

jwpattern (base property)

multiplicity from associationEnd.multiplicity

allowDuplicates from associationEnd.allowDuplicates

required from baseViewField.required

useOnSummary from associationEnd.useOnSummary

useOnSearch from associationEnd.useOnSearch

accessor from associationEnd.accessor

roleName from associationEnd.roleName

initialRoleName from associationEnd.initialRoleName

access from businessMethod.access

package from baseViewRelation.package

readable from baseViewRelation.readable

writeable from baseViewRelation.writeable

uid from constraint.uid

view from baseViewEnd.view

externalName from baseViewEnd.externalName

format from baseViewEnd.format

visible from baseViewEnd.visible

group from businessMethod.group

screenPosition from baseView.screenPosition


14.17.1  Property 'endRoleName'
OverridesbaseViewEnd.endRoleName
DescriptionThis optional property is for advanced use. It names the role of the object at this end of the view relation.

It is used as follows:

  • data-view-relations between data-views that both have underlying entities (i.e. those with an 'initial-entity') must match to a relation between the underlying entities

  • this matching is normally implicit, because there is only one possible relation between the two underlying entities - so this is assumed to be the matching relations, regardless of the role-name.

  • however, if there is more than one possibility, the end-role-name can be used to explicitly identify the role-name of the matching relation.

  • there is a third possibility - that the data-view-end's role-name is used to match to the correct end on the entity.
This is fine if both levels of relations - at the entity and the data-view level - can use the same role names. But if this is inconvenient, the end-role-name can be used so that different role names can be used on the entity and data-view relations. This also affects coding in some tools - such as IBM Rational's RSA-RSM, which joins the concept of role name and setter/getter for the related object.
TypeString
 


Copyright (c) 2001-2008 New Technology/enterprise Ltd.