Note, this documentation is still very much work in progress

RIFE/Crud can be customized in a number of ways.

Below is a list of all supported entities:

• Element properties
• L10n properties files
• Custom element implementations
  • Element IDs
  • Exit names

Element properties

Element properties are set in the site structure during the declaration.

They provide you with ways to:

• provide custom implementations for specific CRUD elements in the auto-generate site
• provide custom templates that will be used to layout the CRUD element views
• configure the paging settings

crud_implementation-add
crud_implementation-browse
crud_implementation-delete
crud_implementation-edit
crud_implementation-home
crud_implementation-menu
crud_implementation-move

crud_template_name-add
crud_template_name-browse
crud_template_name-delete
crud_template_name-edit
crud_template_name-home
crud_template_name-menu
crud_template_name-blueprint
crud_template_name-ranged_table_components
crud_template_name-ranged_table

crud_paging-limit
crud_paging-span

L10n properties files

The standard CRUD templates contain placeholders everywhere localizable text should be displayed. For most parts, RIFE/Crud tries to figure out usable English default texts from the bean's class names or the site structure. However, you will most certain want to change some of those texts with your own, even you don't use another language.

RIFE/Crud looks for the localization properties files in a cascading fashion. You can provide very specific ones for every bean, and if properties aren't found there, it will look in the general properties file.

The bean-specific file should have the following name and location:

l10n/crud/admin-{escaped_full_classname}_{language}.properties

(an escaped class name replaces the dots by underscores: com.uwyn.MyClass becomes com_uwyn_MyClass)

The general file should have the following name and location:

l10n/crud/admin_{language}.properties

These are the localization property keys that are supported by each standard RIFE/Crud template:

crud.admin.add

window_title
page_title-add
page_content-add-success_header
page_content-add-success_message
button_label-add_more
button_label-browse

crud.admin.browse

window_title
page_title-browse
column_width-{property_name}
column_width-actions
{property_name}
column_label-actions
association_header-{full_association_classname}
column_nowrap-{property_name}
button_label-edit
button_label-delete
button_label-up
button_label-down
button_label-browse_assocation
button_label-add_assocation
page_content-browse-none_available
button_label-add_first
button_label-home

crud.admin.delete

window_title
page_title-delete
{property_name}
button_label-delete
button_label-cancel
page_content-delete-success_header
page_content-delete-success_message
button_label-browse

crud.admin.edit

window_title
page_title-edit
page_content-edit-success_header
page_content-edit-success_message
button_label-browse

crud.admin.form

{property_name}
{property_name}-legend
{property_name}-help
form_label-mandatory
button_label-save
button_label-add
button_label-cancel

crud.admin.home

window_title
page_title-home
page_content-home
button_label-browse
button_label-add

crud.admin.menu

menu_item-{full_bean_classname}
menu_item-{full_bean_classname}-home
menu_item-{full_bean_classname}-browse
menu_item-{full_bean_classname}-add
menu_item-{full_bean_classname}-edit
menu_item-{full_bean_classname}-delete
menu_item-home
menu_item-browse
menu_item-add
menu_item-edit
menu_item-delete

crud.common.blueprint_admin

crud_css_file
product_title
product_name
product_copyright

crud.common.error_area

error_area_title
error_mandatory
error_wronglength
error_notsame
error_invalid
error_unicity
error_notnumeric
error_unexpected

crud.common.ranged_table

label-pages

Custom element implementations

Thanks to the element properties it's possible to make RIFE/Crud use your own custom implementations for the CRUD elements. You can also use RIFE's site structure to link from elements outside RIFE/Crud to auto-generated elements.

You can use the nomenclature below to find out what the generate element IDs and exits are:

Element IDs

{short_bean_classname}.HOME
{short_bean_classname}.MENU
{short_bean_classname}.BROWSE
{short_bean_classname}.ADD
{short_bean_classname}.SERVECONTENT
{short_bean_classname}.MODIFICATION.EDIT
{short_bean_classname}.MODIFICATION.DELETE
{short_bean_classname}.MODIFICATION.MOVE
{short_bean_classname}.MODIFICATION.{short_association_classname}.HOME
{short_bean_classname}.MODIFICATION.{short_association_classname}.MENU
{short_bean_classname}.MODIFICATION.{short_association_classname}.BROWSE
{short_bean_classname}.MODIFICATION.{short_association_classname}.ADD
{short_bean_classname}.MODIFICATION.{short_association_classname}.SERVECONTENT
{short_bean_classname}.MODIFICATION.{short_association_classname}.MODIFICATION.EDIT
{short_bean_classname}.MODIFICATION.{short_association_classname}.MODIFICATION.DELETE
{short_bean_classname}.MODIFICATION.{short_association_classname}.MODIFICATION.MOVE

Exit names

{full_bean_classname}-home
{full_bean_classname}-browse
{full_bean_classname}-add
{full_bean_classname}-edit
{full_bean_classname}-delete