Add basic set of OSGi bundle headers to manifest
Add basic set of OSGi bundle headers to manifest

The manifest now contains all headers for the war file to be accepted as a monolithic OSGi bundle, which contains (almost) all runtime dependencies.

Required runtime packages for servlets, JSPs and XML processing are imported.

The bundle's web context path is the application name.

The bundle classpath consists of the Grails app's code (from WEB-INF/classes) and all provided libraries (from WEB-INF/lib) as well as the resources available in the web app (.)

The bundle classpath is determined after the event handlers had a chance to add or remove jars or otherwise modify the war's content.

The created war file can for example be deployed into Spring DM Server by copying it into the $DMS_HOME/pickup directory. Note that the Heap and PermGen space should be increased to at least 256m (heap) and 128m (PermGen) respectively, e.g. by setting JAVA_OPTS="-Xmx256m -XX:MaxPermSize=128m" before starting DM Server.

clockworkorange/grails-core,erdi/grails-core,clockworkorange/grails-core,clockworkorange/grails-core,erdi/grails-core,erdi/grails-core,clockworkorange/grails-core,clockworkorange/grails-core