net.open-esb.core:jbi_framework 2.4.2

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.

Categories	Net
GroupId	net.open-esb.core
ArtifactId	jbi_framework
Version	2.4.2
Type	jar

Download jbi_framework 2.4.2

Filename	Size
jbi_framework-2.4.2.pom
jbi_framework-2.4.2.jar	367 bytes
jbi_framework-2.4.2-javadoc.jar	334 bytes

Apache Maven

<!-- https://jarcasting.com/artifacts/net.open-esb.core/jbi_framework/ -->
<dependency>
    <groupId>net.open-esb.core</groupId>
    <artifactId>jbi_framework</artifactId>
    <version>2.4.2</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/net.open-esb.core/jbi_framework/
implementation 'net.open-esb.core:jbi_framework:2.4.2'

Gradle Kotlin

// https://jarcasting.com/artifacts/net.open-esb.core/jbi_framework/
implementation ("net.open-esb.core:jbi_framework:2.4.2")

Apache Buildr

'net.open-esb.core:jbi_framework:jar:2.4.2'

Apache Ivy

<dependency org="net.open-esb.core" name="jbi_framework" rev="2.4.2">
  <artifact name="jbi_framework" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='net.open-esb.core', module='jbi_framework', version='2.4.2')
)

Scala SBT

libraryDependencies += "net.open-esb.core" % "jbi_framework" % "2.4.2"

Leiningen

[net.open-esb.core/jbi_framework "2.4.2"]