Xsemble follows a clean data separation philosophy. A repository contains the components, a project contains the data flow and control flow, and the application is the resultant source code of the whole application. Even within the repository, the component definitions and their implementations (in terms of source code and any dependencies) are kept seperately.
Given below are top 10 features of Xsemble. For details, please refer the documentation that accompanies Xsemble.
Xsemble components may be reused across projects, and sometimes within the same project. They are reusable components in their true meaning.
Each component is designed and developed independently from the other components. It is the responsibility of the glue code generated during the burn phase to weave them together.
Projects may be used as subprojects within other projects, and even those can be reused.
A repository may be conveniently opened as a Java project in a Java IDE for component implementation.
Xsemble generates a code template for a component, which is the starting point of development.
One or more components from a repository may be exported as a test bundle. The test bundles can themselves be opened as projects within a Java IDE and deployed and run, without needing Xsemble tool. This is the way programmers may be utilized for component development and testing, without needing Xsemble license.
While creating the flow, the data types can be matched -- which impart type safety and robustness.
Health checking functionality looks for common issues such as unused files or unresolved dependencies. This avoids code bloat and keeps the repository up-to-date.
Xsemble components may be assigned a complexity as XS, S, M, L and XL -- quite like a T shirt. This sizing information can be used in a progress report dialog for project estimation and tracking.
You can connect with the live application and monitor it visually in terms of the control and the data flow. For that, the application needs to be burned with the "debug" option on. Even remotely deployed "live" application may be monitored.