websphere - Why we need to specify jar dependency in MANIFEST file -
when deploying ejb jar part of ear, understand runtime jar dependencies of ejb (i.e log4j) need specified in ejb jar's manifest.mf. why this? if put log4j in same directory ejb jar, should automatically included in runtime classpath, no?
why need specify log4j in manifest.mf again? on same vein, jars automatically available ejb jar @ runtime without having specify them in manifest? jars shipped websphere?
you don't have specify dependencies in manifest starting java ee 5. location of libraries can specified through <library-directory>
element in application.xml. defaults lib
.
java ee 5 supported 7.0 , higher.
Comments
Post a Comment