Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cocoon Wiki" for change notification.
The following page has been changed by BertrandDelacretaz: http://wiki.apache.org/cocoon/Blockathon2005Report New page: Info and reports about the ApacheCon 2005 Blockathon. = Monday July 17th = Daniel talks about the current state and next steps. == Current state of the Cocoon OSGI stuff == The whiteboard/osgi code is being integrated into the trunk, to make it more convenient to work on. Currently the OSGI-related code consists of three bundles: The cocoon bundle: * Contains all the code from src/java and all the libraries from lib/core * Currently all packages are exported (to make it easier to work now) via an OSGI manifest file * Does not include an OSGI Activator class The webapp bundle: * Contains all the files from src/webapp * Bundle-category: webapp * Passive bundle, only contains resources The cocoon-servlet bundle: When loaded: * Imports some classes from the Cocoon bundle (via an Activator class) * Gets resources from the webapp bundle, via the OSGI bundle: protocol * Creates the Cocoon Servlet * Registers the Servlet with the OSGI HttpService Main TODOs: * Package some or all libraries in their own bundles * Directory listing (e.g. for DirectoryGenerator) doesn't work in OSGI currently, throws Exceptions. Need to be converted to warnings at least, to avoid the need for patching the xconf files to run under OSGI (See http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=112167452021559&w=2). == Next steps == 1. Get the OSGI-based Cocoon Servlet to work in the trunk 1. Remove the need to patch the xconf files 1. Create a bundle for one existing block or create an "OSGI test" block 1. Demonstrate the dynamic loading of the block bundle via an URL
