Skip to content

BPELtools/BPELlint

 
 

Repository files navigation

BPELlint Build Status Dependency Status Coverage Status

The tool BPELlint validates BPEL files according to 71 static analysis rules from the BPEL 2.0 specification.

This software is licensed under the LGPL Version 3 Open Source License.

Software Requirements

  • JDK 1.8.0 (64 Bit) or higher
    • JAVA_HOME should point to the jdk directory
    • PATH should include JAVA_HOME/bin

Licensing

Dual licensed under LGPL Version 3 and EPL 1.0

Usage

Requirements (see above) have to be fulfilled to execute BPELlint.

usage: BPELlint [OPTIONS] PATH
PATH can be either a FILE or a DIRECTORY.

 -f,--full                   Prints out the definitions of the violated
                             rules as well.
 -h,--help                   Print usage information.
 -s,--no-schema-validation   Disables xsd schema validations.

Please report issues at https://github.com/uniba-dsg/BPELlint/issues

Examples:
$ BPELlint empty.bpel # Validates the <empty.bpel> file.
$ BPELlint folder # Validates *.bpel files within the <folder> and all its subfolders.

$ BPELlint -f empty.bpel # Validates the <empty.bpel> file including rule definition.

Only the .bpel file path or directory has to be given as parameter, all needed and referenced files will be loaded. With no further parameters the output consists of error position and a short message. Parameter order is not important, only the last used parameter is of importance.

Development

$ gradlew test # run all unit tests
$ gradlew idea # Generating Intellij IDEA project files
$ gradlew eclipse # Generating Eclipse project files
$ gradlew javadoc # Generating JavaDoc

The folder Testcases/betsy is copied by hand for convenience from betsy src/main/tests/files. Checkout https://github.com/uniba-dsg/betsy to get the latest version.

The environment variable BPEL_LINT_SA_RULES constrains the SA rules that are validated. When BPEL_LINT_SA_RULES is not set or set to all then all SA rules are validated if set to 61,2,10 then SA00002, SA00010 and SA00061 are validated.

Authors (in alphabetical order)

David Bimamisa, Simon Harrer, Christian Preissinger, Stephan Schuberth

Contribution Guide

  • Fork
  • Send Pull Request

About

Validation tool which statically analyzes BPEL files using the statical analysis rules from the BPEL 2.0 specification.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 97.7%
  • Ruby 2.1%
  • Other 0.2%