[daisy] [JIRA] Created: (DSY-479) Daisy Wiki extensions need to be able to provide / embed java components and have own classloader

Bruno Dumon (JIRA) issues at cocoondev.org
Fri May 25 08:26:20 CDT 2007


Daisy Wiki extensions need to be able to provide / embed java components and have own classloader
-------------------------------------------------------------------------------------------------

         Key: DSY-479
         URL: http://issues.cocoondev.org//browse/DSY-479
     Project: Daisy
        Type: Improvement
  Components: Frontend - platform  
 Reporter: Bruno Dumon
    Priority: Minor


The current Wiki extensions are flexible and lightweight, but are limited to responding to HTTP requests:
  - We need a clean way to use Java code in extensions:
      - extension-specific classpath (now jars need to be added to WEB-INF/lib, which means extensions are not self-contained and the Daisy Wiki needs to be changed)
      - component container per extension
      - making components available to other extensions
  - An extension shouldn't necessarily provide a new URL space, but could simply exist for the purpose of making Java component available, registering a hook, ...

Most of these things need to be made available on the level of Cocoon, and might already be OK (to some extent) in Cocoon 2.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



More information about the daisy mailing list