Group: net.open-esb.core - All Dependencies

base-interfaces · Shared interfaces between JBI Runtime modules

jbi-interfaces-version-1 · Interfaces specified by the JSR 208 Expert Committee

management-services · JBI Runtime Management components, providing installation, deployment, and other JMX interfaces for remote management consoles.

jbi-admin-common · The "jbi-admin-common" Common CLI code

messaging-services · JBI Messaging components

esb-util · Open ESB utility classes shared between clients and runtime

wsdl2 · WSDL 2 Classes

uber-core · Builds the OpenESB runtime jar.

core-framework-services · JBI Framework Services

ui-runtime · JBI UI Runtime Classes

jbi-api-interfaces-version-1 · API Interfaces specified by the JSR 208 Expert Committee

esb-manage · ESB Runtime Management Infrastructure

testbinding-rt · Test Binding Runtime Code

testbinding-boot · Test Binding Boot Code

testengine-boot · Test Engine Boot Code

jbi-ant-tasks · The "jbi-ant-tasks" ant tasks code for jbi admin tasks

wsdl · JBI WSDL Shared Library

esb-internal-interfaces · Open ESB Internal (IPI) interfaces

jbi-spi-interfaces-version-1 · SPI Interfaces specified by the JSR 208 Expert Committee

jbi_framework · In order to get around the JBI Lifecycle Classpath limitation in the application server, a new JBI jar file is being created called esb_jbi_framework.jar. This jar file will contain a MANIFEST.MF file that contains Class-Path: entries that point towards the jbi_rt.jar (JBI Runtime) and jbi_tests.jar (Scaffolding Registry et al) . This way we dont have to combine the throwaway jbi_tests.jar with the main jbi_rt.jar later. We would simply have to dereference it from jbi_framework.jar. Likewise adding a new JAR to the same classpath would simply mean adding a new entry to the ClassPath: header field.

message-tracking · JBI Message Tracking Facility

core-distribution

wsdl11-wrapper · WSDL 11 Wrapper

testengine-rt · NMR Engineg Test Engine Runtime Code