Abstract: A computer system has a runtime environment (e.g. Java) and a deployment system (e.g. a Spring framework layer) arranged to deploy an application into the runtime environment. The application comprises bundles (e.g. OSGi bundles or JSR modules) each with manifest metadata defining dependencies for the respective bundle. A deployment management unit refers to one or more personality specific deployers to determine which of the bundles have a specific personality from a predetermined set of personality types. The personality specific deployers transform the respective personality-specific bundles by inserting one or more additional dependencies into the metadata of the bundle according to their personality type. The deployment management unit applies one or more operations to all of the plurality of bundles, including installing each of the bundles ready for deployment and deploys those bundles not having a specific personality type.

Abstract: A computer system has a runtime environment (e.g. Java) and a deployment unit (e.g. in a Spring framework layer) arranged to deploy the application into the runtime environment. The application comprises bundles (e.g. OSGi bundles) with manifest metadata having export statements defining exported packages. The deployment unit comprises a receiver unit to receive the bundles, an extractor unit to examine the metadata and extract the export statements, a converter unit to convert each of the export statements into a corresponding import statement, and a creator unit to add a synthetic bundle having the import statements inserted in its metadata. The deployment unit sets a thread context class loader to delegate class loading to a class loader of the synthetic bundle. Thus, at runtime, classes of the application are only loaded when they are explicitly exported packages as defined by the synthetic bundle.