Project Analysis and Validation

In this task, you check the project for errors.

If you have configured it correctly, you’ll see warnings but no errors. Warnings indicate potential issues, such as absence of default events. It’s always worth checking them. In the FraudDetection project, the warnings do not indicate any actual issues.

Learning points

How can I validate that there are no basic errors in my code?
To perform checks that do not take project logic into account, use Project > Validate Project (or right-click on a project name, and use the same named option).
What if there are problems in my code?
You can debug it. TIBCO BusinessEvents builds on the Eclipse debugger features to provide additional checks. Developers familiar with the Eclipse debugger will find it intuitive to use.
How can I analyze that the logic of my project is OK?
For this kind of checking you use Project Analyzer or the Element Diagram or both. They work together to provide insights into your project. Project Analyzer is a document generated in the Problems view area. Element Diagram provides a visualization of the whole project or of selected project elements. It also shows all dependencies in a project. Project Analyzer and Element Diagram can be configured to run separately or together, using preferences.
How can I visualize different aspects of a project?
TIBCO BusinessEvents provides diagrams similar to UML sequence diagrams, class diagrams, and dependency diagrams.

How can I change the names of project resources, or move them around? Use the refactoring features. They ensure that changes you make are reflected throughout the project (with certain limitations).

More Information

In TIBCO BusinessEvents Developer’s Guide, see Testing and Debugging Projects.