Which of the following are asset packaging best practices?

Which of the following are asset packaging best practices?

Which of the following are asset packaging best practices?

A.
Every reusable asset must contain at least one manifest file that self-describes the contents of
the package.

B.
Any components that can be precompiled must be precompiled in the package.

C.
Non-runtime artifacts such as build and test artifacts must be included in the package.

D.
Packaging of components must be modular and all common components must be packaged as
independent libraries that can beincluded in multiple packages.

Explanation:
Assets must be packaged using standards-based approaches
with the goal of improving flexibility, reuse, and runtime
performance.
Applying packaging standards and best practices is a critical
step in ensuring that the assets are deployed for the best quality
and performance. It also accelerates the time-to-deployment.
Implications:
* Every reusable asset must contain at least one manifest file
that self-describes the contents of the package.
* Any components that can be precompiled must be
precompiled in the package.
* Non-runtime artifacts must not be included in the
deployment package. (e.g. build and test artifacts) (not C)
* Packaging of components must be modular and all common
components must be packaged as independent libraries that
can be included in multiple packages.
Note: Further implications
* Libraries provided by the platform should not be included
in the package. (e.g. Application Server system libraries)
* Libraries and components in a package must not be
duplicated. The classloader hierarchy must be used to
design the packages to avoid duplication.
* Common libraries must be placed outside the package to be
loaded by a higher level classloader (e.g. System
classloader).
* Packages must follow predefined industry or company
standard naming conventions and structures.
* Static content must not be included in the deployable
package. They must be served separately in exploded
format.
Reference: Oracle Reference Architecture, Software Engineering, Release 3.0,



Leave a Reply 0

Your email address will not be published. Required fields are marked *