Example (value of attribute)

From JRapid

Jump to: navigation, search

First line contains the category link and the parent element or property links. It also links to sibling values.

inline is a value of embedded.

Other values are:



1st phrase: Minimum sufficient description that identifies the result of using this value. The summary in the first row. After that, in each row, the other necessary ideas that provide the whole description. If you use bullets, remember to enter the dot at the end of each sentence.

When a property is declared as embedded inline (it must be a collection), the properties of the child entity are displayed as columns.

(Avoid repeating concepts that belong to the parent attribute. Link to the attribute instead.)

  • Embedded collections need to specify a childproperty attribute, which connects to the parent entity and plays as the "linking property" in this 1-N relation.
  • Embedded collections represent weak relations, so they map to cascade="all" hibernate relations, and ondelete="cascade" at the database.


Taking the closest ancestor template (Do not use {{Property spec}}, enter Template:Property spec instead, and copy-paste here, leaving only required attributes + those attributes related to the parent attribute

         name = NAME
         label = LABEL
         entity = ENTITY
         collection = COLLECTION
         embedded = (inline|detail|grid)
         childproperty = PROPERTY
         maxrows = ROWS
         minrows = ROWS
         listindex = LIST_INDEX
         listunique = LIST_UNIQUE
         setorder = SETORDER
         sort = SORT
         sortexpr = EXPR
         where = WHERE
         extendable = "extendable"
         sortable = "sortable"
         gridheader = "gridheader"
         gridvalue = "gridvalue" 
         displayproperties = PROPERTIES
         (foreach?, dynamicforeach?, ...)


Examples have an structure and need to be unique for the value. As we say for the description, they should not include nor explain concepts from the parent attribute.

  • Business Rules
    • Data Model (Screenshot)
    • Data Model (XML Source)
  • Screenshot of result
  • Conclusion text

Business rules

  • Main Company entity and a child Contact entity.
  • Contacts belong only to one Company (n-1).

File:Inline (value of embedded) ex1 model.jpg

    <entity label="Company" menu="Main" name="Company">
        <property display="primary" label="Name" name="name"/>
        <property display="secondary" label="Contacts" name="contacts" entity="Contact" collection="set" embedded="inline" childproperty="company" extendable="extendable"/>

    <entity label="Contact" name="Contact">
        <property entity="Company" label="Company" name="company"/>
        <property label="First Name" name="firstName"/>
        <property label="Last Name" name="lastName"/>
        <property label="Phone" name="phone"/>

  • We have few fields, so a column-disposition is a good way of presenting (for more columns see detail.
  • We will never have many rows (for many rows consider embeddedlisting).

File:Inline (value of embedded) ex1.jpg

Here we get the child entity with its properties displayed as columns. Additionally, we get a remove-line button at the end.

See also

Most important wikiwords that appear in the article, and how they link, when needed

Include corresponding category


Personal tools