Download all versions of jbi_framework JAR files with all dependencies
jbi_framework from group net.open-esb.core (version 2.4.3)
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.
Artifact jbi_framework
Group net.open-esb.core
Version 2.4.3
Last update 25. January 2016
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.open-esb.core
Version 2.4.3
Last update 25. January 2016
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jbi_framework from group net.open-esb.core (version 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.
Artifact jbi_framework
Group net.open-esb.core
Version 2.4.2
Last update 24. June 2015
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.open-esb.core
Version 2.4.2
Last update 24. June 2015
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jbi_framework from group net.open-esb.core (version 2.4.1)
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.
Artifact jbi_framework
Group net.open-esb.core
Version 2.4.1
Last update 13. February 2015
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.open-esb.core
Version 2.4.1
Last update 13. February 2015
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jbi_framework from group net.open-esb.core (version 2.4.0)
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.
Artifact jbi_framework
Group net.open-esb.core
Version 2.4.0
Last update 02. December 2014
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.open-esb.core
Version 2.4.0
Last update 02. December 2014
Tags: likewise have esb_jbi_framework being manifest runtime contains towards from same jbi_rt would order created file lifecycle combine path mean entries jbi_framework with application jbi_tests later class limitation classpath header around main field point that scaffolding dont simply contain entry will called server registry throwaway dereference this adding
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Page 1 from 1 (items total 4)