PLEASE NOTE: These documents are being moved over from TPTP and are in the process of being updated
to reflect B2J rather than the TPTP Choreography Component.
- org.eclipse.hyades.choreography – The entire choreography component
- jengine - The choreography engine implementation
- misc - Utility classes for use across the entire component
- ui - The entire UI for the component
- xpath - An XPATH parser implementation
(
org.eclipse.tptp.choreography.jengine subpackages)
- api – The API to the engine (API to programmatically start a new engine and set the program etc)
- compiler – The classes to compile BPEL, WSDL, XSD etc to a Java engine program
- binding - legacy package
- bpel - BPEL translator classes
- wsdl - WSDL translator classes
- wsdlmap - WSDL file utility classes
- xmlns - XML namespacing utility classes
- xpath - XPATH translator classes
- xsd - XSD translator classes
- xsdmap - XSD file utility classes
- core – The classes implementing the runner-accessible interfaces of the runtime engine
- api – Runtime engine client side API
- bpel – Runtime BPEL classes which provide BPEL specific abstractions which map to usage of the engine’s distributed constructs (e.g. BPELVariable would map to or use the engine’ shared variable facilities)
- datapool – Runtime engine distributed data sharing facilities (distributed shared variables etc)
- picker – Runtime engine distributed picking classes (probably legacy)
- sync – Runtime engine distributed synchronisation facilities
- mainengine – A distributed implementation of the core engine interfaces
- api – API to the main engine implementation of the core engine interfaces
- miniengine – A small local implementation of the core engine interfaces
- api – API to the mini engine implementation of the core engine interfaces
- extensionpoints – All extension points the choreography engine exports
- wsdlbinding – the WSDL Binding extension point allowing contributions of WSDL Binding type implementations
- sessiontransport – the Session Transport extension point allowing contributions of point-to-point transport implementations
- extensions – Any in-house extensions of choreography engine extension points
- internal – The engine’s own internal messaging binding
- soap – The engine’s own SOAP binding implementation
- wsif – The engine’s own WSIF Java binding implementation
- message – Engine messaging and transaction abstraction
- multiplex – Engine multiplexing classes
- mutex – Engine high level synchronisation constructs
- trcagent – Engine TRCAgent utilities (for registering engine instance as a TPTP TRCAgent)
- utils – Utility classes for the runtime engine