Several applications in an organization use a common Java library, commom.jar. Two applications App1 and App2 have their own shared libraries shlib1.jar and shlib2.jar that reference common.jar…

Question

Options

• ADeploy all the jar files as static libraries.
• BDeploy all the jar files as part of the applications.
• Ccommon.jar deployed as a shared library along with the shlib1.jar and shlib2.jar as shared
• Dshlib1.jar and shlib2.jar must now be deployed as static libraries and common.jar as a shared

• A
  12% (4)
• B
  6% (2)
• C
  3% (1)
• D
  79% (27)

Explanation

Consider a scenario when you want to develop a set of common resources and make them available to multiple applications. Shared libraries If you want to deploy and manage just one copy of those common resources, use a shared library. A shared library can be deployed directly to an integration server. Any application can changes are immediately visible to all referencing applications. Static libraries If you want each application to use a different version of the contained resource, use a static library. Each application that references that static library is deployed with its own private copy of that library. If a static library is updated, each application that references it must be repackaged and redeployed with the updated static library.

No community discussion yet for this question.