Search Results for "trace"

iii is a backend unification engine that organizes application behavior around a small set of primitives such as functions, triggers, and workers. It is designed to connect existing backend systems into a more inspectable and programmable runtime. The project includes a console for developers and operators to inspect functions, triggers, traces, and live state. Its goal is to reduce backend sprawl by giving teams a single operational layer for event-driven and function-based workflows. iii...

...A major use for this project is continuous integration -- so we must have reliable results. We usually balance correctness over performance. And, if necessary, we should be able to trace this program's detection of HTML errors back to documented best practices or standards, such as W3 specifications. Third-party modules. We want this product to be useful for continuous integration so we prefer to avoid subjective tests which are prone to false positive results, such as spell checkers, indentation checkers, etc. If you want to work on these items, please see the section on custom tests and consider adding an implementation as a third-party module.

Offline Wily Transaction Inspector is a Java standalone application with which one can analyze trace files offline generated by Wily Introscope Workstation or Webview.

- quick-json features - # Compliant with JSON specification (RFC4627) # High-Performance JSON parser # Supports Flexible/Configurable parsing approach # Configurable validation of key/value pairs of any JSON Heirarchy # Easy to use # Very Less foot print # Raises developer friendly and easy to trace exceptions # Pluggable Custom Validation support - Keys/Values can be validated by configuring custom validators as and when encountered # Validating and Non-Validating parser support # Support for two types of configuration (JSON/XML) for using quick-json validating parser # Require JDK 1.5 # No dependency on external libraries # Support for Json Generation through object serialization # Support for collection type selection during parsing process