4.6 Automatic Imports for the Web subsystem
Prev | 4. Developing Applications | Next

## 4.6 Automatic Imports for the Web subsystem

The Virgo Web Server generates automatic package imports (i.e., via the `Import-Package` manifest header) for the web subsystem’s artifacts. This section lists which packages are automatically generated.

All WARs, as required by the OSGi Web Applications specification, and Web application bundles (see Default Web Application Bundle Headers) will automatically import the following packages:

- `javax.servlet;version="2.5"`
- `javax.servlet.http;version="2.5"`
- `javax.servlet.jsp";version="2.1"`
- `javax.servlet.jsp.el;version="2.1"`
- `javax.servlet.jsp.tagext;version="2.1"`
- `javax.el";version="1.0"`

In addition to the above-described imports, VWS will also generate automatic imports for all of the packages that are exported by the system bundle, unless an import for the package already exists in the artifact’s manifest, or the artifact contains the package, i.e. within `WEB-INF/classes`, or in a jar file in `WEB-INF/lib`. When an import is generated, it is versioned such that it exactly matches the version or versions of the package that are exported from the system bundle. For example, a package that’s exported only at version `1.0.0` will generate an import with a version of `[1.0.0,1.0.0]`, and a package that’s exported at version `1.0.0` and version `2.0.0` will generate an import with a version of `[1.0.0,2.0.0]`.

| System Bundle Package Exports
For further details on which packages are exported by the OSGi system bundle, consult the `java6-server.profile` file located in the `SERVER_HOME/lib` directory.

Prev | Up | Next
4.5 Programmatic Access to The Deployer Pipeline | Home | 4.7 Working with dependencies