eva/3 Application BuilderDeveloping Additional eva/3 ComponentsUser BeansBean Shema 

Usage of a Bean Schema

To add the new bean in the Form- or Report editor The page User in the Beans dialog is to be selected (s. fig. 290 ). After right click in the Beans dialog, the menu entry Add bean has to be selected. The dialog Choose Bean opens (s. fig. 291 ).

To remove a user bean, it can be right clicked, followed by selecting the menu item Delete bean.

Fig. 290: User Defined Beans in the Bean Dialog
Fig. 290: User Defined Beans in the Bean Dialog

Adding a Bean Schema to the Beans Dialog

The selection of the wanted bean can be done by double click in the Choose Bean dialog (s. fig. 290 ). There is a bean shema in the selection when it is:

Fig. 291: Selection of a Bean
Fig. 291: Selection of a Bean

Visibility of a Bean Schema

The beans mostly can be used very universal. So it often is usefull to pack them in an own .jar archive, to import them into other projects.

When separating the beans from the current project, the following is to be regarded:

Form-/Report editor The described (self written) classes (Bean, Converter, Renderer, Editor) must be on the class path of the current project or one of the imported projects.

Please note that the .jar archive must contain the eva/3 files system.eva3 and system.forms.
Runtime The .jar files and the used projects from wich beans are imported, must explicitly set in th project path.

The described (self written) classes (Bean, Converter) must be reachable by their class path or the project path sein.

These settings are made automatically at the Execution (as eva/3 application) from eclipse