Search Results

The authorization descriptor is an XML describing the different authorizations that can be granted to users. This file should be located at /com/soffid/addon/authorization.xml The template for this file is: <?xml version="1.0" encoding="utf-8"?> <autorit...

Schema description The schema must be expressed as an XML file. This file should be located at a core addon module and be named plugin-ddl.xml. This DDL file can contain descriptions for tables, indexes and foreign keys. Tables A table is composed of a <ta...

Soffid Business Processes use JBoss JBPM engine. You can find the original JBPM documentation here. In order to develop a new business process addon you need Eclipse Java EE IDE for Web Developers and three plugins installed on it: JBPM plugin. You can fin...

Introduction To define the user interface for a task, a .zul file must be located at the ui directory, and the corresponding task tag should be located at ui.xml file. The user interface must be a ZK .zul page. This zul page must contain a task tag. This cus...

Introduction The user interface descriptor follows the attached schema: ui.xsd Versioning JBPM denotes business process definition using a sequential number. This approach is not practical for business process management. So, every ui.xml file should have a...

Introduction zkdb is a set of Java classes and ZK components designed to easy the development of web applications driven by a data model. ZKIB aims to fill the gap between the user interface defined in ZK and logic stored mainly in EJBs. ZKIB basic componen...

Soffid is concerned about component versioning and how to upgrade them. A upgrade system is designed in order to easiest Soffid core components upgrade, as well as Soffid addons addition, suppression or upgrades. Soffid also defines the interface to use servi...

Soffid addons should be able to manage data schema changes. Soffid gives addons a standard procedure to perform data and schema upgrades. The data upgrade process is performed in three steps: 1. The addons to upgrade are deployed into the soffid console using...

Soffid upgrades are managed using the same mechanisms as addon upgrades. Data upgrade The data upgrade process is performed in three steps: 1. The console is upgraded using soffid installer. 2. On console boot, the data schema is updated. To perform the sc...

Web add-ons are standard war files. The files included in the war file will be copied onto Soffid console war file. In order to keep compatibility between add-ons, it's forbidden to overwrite existing file. Instead, the war file can contain xslt files to modi...

Introduction Soffid allows building add-ons that can customize data model, business logic and user interface. There are six different types of add-ons: BPM process archive (par). They follow the JBPM archive guidelines plus some additional files for managi...

There are three alternative ways to implement user interface data model. The first one is to retrieve information from an XML file. Its use is simple and easy to implement during user interface prototyping phase. A second alternative is to create a set of glu...

In the previous section, we saw how to declare a sample data model. To bind a component to a data model element, the bind attribute can be used. The bind attribute value must be composed of the data source path to be used, a colon separator, and the xPath elem...

To easiest the readability and maintainability of the code, and to shorten in XPath paths, some components can works as a relative xpath context for the contained ZK components. When a container type object is associated with a data model element, binds on chi...

Components of type listbox and grid behave as complex containers of object collections. These components can be assigned a Xpath expression that does not identify a single object, but a collection of objects or values. In this case, the system will generate a ...

The listbox component has a dual role, as a data consumer and as a data source. We've seen how listbox component can act as a data consumer in the previous pages. No we'll see how is it acting as a data source. Any zul component can use the listbox path as th...

The data model can be manipulated directly using the JXPathContext interface or indirectly through components, Whenever the user changes the contents of a ZK component, which is bound to a data model object, the change is propagated to the model, which in turn...

While building the data model using XML files is possible, it's advisable to use more dynamic data models in the production environment. Alternatively, ZKIB module provides a set of classes that ease interaction with data models based on JDBC databases and obj...

It is possible to define the underlying data model without having to write java code. To do this, you must use an XML descriptor which describes the DataNodes and their relationships. An skeleton XML descriptor has the following structure: <?xml version="1.0"...

It is responsible for persisting the object via a stateless session bean. The following attributes are supported: Attribute Usage jndi JNDI path to EJB Home interface if EL expression that must be evaluated to true...