wookie-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Wilson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WOOKIE-210) Refactor Feature loading and enable runtime inclusion
Date Wed, 11 May 2011 13:25:47 GMT

     [ https://issues.apache.org/jira/browse/WOOKIE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Scott Wilson updated WOOKIE-210:

    Component/s: Server

> Refactor Feature loading and enable runtime inclusion
> -----------------------------------------------------
>                 Key: WOOKIE-210
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-210
>             Project: Wookie
>          Issue Type: Improvement
>          Components: Configuration, Server
>            Reporter: Scott Wilson
> Features currently consist of a Java class that is complied at build time, plus a number
of js and css resources. These are then installed and persisted using the ServerFeature bean
and queried at runtime.
> However, there is no reason to require such a complex process for creating, building
and installing features, and I propose instead we follow Shindig's approach and create an
XML-based loading process.
> This would use a feature.xml file to configure each Feature object, e.g.: 
> <feature>
> 	<name>http://jquerymobile.com</name>
> 	<script src="jquery.mobile-1.0a4-patched.min.js"/>
> 	<script src="jquery-1.5.min.js"/>
> 	<stylesheet src="jquery.mobile-1.0a4-patched.min.css"/>
> </feature>
> This can then be loaded and transformed into an IFeature implementation class at runtime.
> The Wave feature is a little more complex, but could be handled more simply as an exceptional
case where the WaveAPIImpl <IFeature> class is added explicitly to the feature loader.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message