[jira] Updated: (SPICE-2) Resource Manager Toolkit

The following issue has been updated:

    Updater: Peter Donald (mailto:peter-4lf8KW9E9MLMqX/[email protected])
       Date: Wed, 25 Jun 2003 9:27 PM
    Changes:
          description changed from We need a toolkit that allows libraries (aka .jar files) to export resources. The resources exported would be things like dtds, schemas, images, components, component profiles etc.

Each library would have a descriptor (META-INF/spice/resources.xml) which lists the resources it exports. A sample of this may look like

<resources version="1.0">

  <!-- declare some resource types -->
  <type shortname="dtd" uri="http://www.w3c.org/1995/dtd"/>
  <type shortname="png" uri="http://www.images-r-us.com/2000/png"/>
  <type shortname="component"
        uri="http://jakarta.apache.org/avalon/component/1.0"/>
  <type shortname="service"
        uri="http://jakarta.apache.org/avalon/service/1.0"/>

  <!-- declare some instances of above resource types -->
  <dtd key="assembly"
       resource="/org/apache/avalon/phoenix/tools/assembly.dtd"/>
  <png key="banner"
       resource="/org/apache/avalon/phoenix/tools/phoenix.png"/>
  <png key="built-with"
       resource="/org/apache/avalon/phoenix/tools/built-with-phoenix.png"/>
  <component key="kernel"
       resource="org.apache.avalon.phoenix.components.kernel.DefaultKernel"/>
  <service key="kernel"
       resource="org.apache.avalon.phoenix.interfaces.Kernel"/>

</resources>

Each resource entry declares a single resource. Each resource has a particular type (type defined by a URI). The way that a resource is extracted from library is not specified by this toolkit. 

This approach would also allow libraries to "extend" or "cascade" existing libraries. So you could replace the resource of type "component" in above config via something like (Assuming that the above descriptor was in a library named 'phoenix')

<resources extends="phoenix" version="1.0">
  <type shortname="component"
        uri="http://jakarta.apache.org/avalon/component/1.0"/>
  <component key="kernel"
       resource="org.apache.avalon.phoenix.components.kernel.DefaultKernel"/>

</resources>
 to We need a toolkit that allows libraries (aka .jar files) to export resources. The resources exported would be things like dtds, schemas, images, components, component profiles etc.

Each library would have a descriptor (META-INF/spice/resources.xml) which lists the resources it exports. A sample of this may look like

<resources version="1.0">

  <!-- declare some resource types -->
  <type shortname="dtd" uri="http://www.w3c.org/1995/dtd"/>
  <type shortname="png" uri="http://www.images-r-us.com/2000/png"/>
  <type shortname="component"
        uri="http://jakarta.apache.org/avalon/component/1.0"/>
  <type shortname="service"
        uri="http://jakarta.apache.org/avalon/service/1.0"/>

  <!-- declare some instances of above resource types -->
  <dtd key="assembly"
       resource="/org/apache/avalon/phoenix/tools/assembly.dtd"/>
  <png key="banner"
       resource="/org/apache/avalon/phoenix/tools/phoenix.png"/>
  <png key="built-with"
       resource="/org/apache/avalon/phoenix/tools/built-with-phoenix.png"/>
  <component key="kernel"
       resource="org.apache.avalon.phoenix.components.kernel.DefaultKernel"/>
  <service key="kernel"
       resource="org.apache.avalon.phoenix.interfaces.Kernel"/>

</resources>

Each resource entry declares a single resource. Each resource has a particular type (type defined by a URI). The way that a resource is extracted from library is not specified by this toolkit. 

This approach would also allow libraries to "extend" or "cascade" existing libraries. So you could replace the resource of type "component" in above config via something like (Assuming that the above descriptor was in a library named 'phoenix')

<resources extends="phoenix" version="1.0">
  <type shortname="component"
        uri="http://jakarta.apache.org/avalon/component/1.0"/>
  <component key="kernel"
       resource="org.apache.avalon.phoenix.components.kernel.DefaultKernel"/>

</resources>
          Component changed from  to NewComponents
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=SPICE-2&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=SPICE-2


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: SPICE-2
    Summary: Resource Manager Toolkit
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: Spice
 Components: 
             NewComponents

   Assignee: 
   Reporter: Peter Donald

    Created: Sat, 5 Apr 2003 10:30 PM
    Updated: Wed, 25 Jun 2003 9:27 PM

Description:
We need a toolkit that allows libraries (aka .jar files) to export resources. The resources exported would be things like dtds, schemas, images, components, component profiles etc.

Each library would have a descriptor (META-INF/spice/resources.xml) which lists the resources it exports. A sample of this may look like

<resources version="1.0">

  <!-- declare some resource types -->
  <type shortname="dtd" uri="http://www.w3c.org/1995/dtd"/>
  <type shortname="png" uri="http://www.images-r-us.com/2000/png"/>
  <type shortname="component"
        uri="http://jakarta.apache.org/avalon/component/1.0"/>
  <type shortname="service"
        uri="http://jakarta.apache.org/avalon/service/1.0"/>

  <!-- declare some instances of above resource types -->
  <dtd key="assembly"
       resource="/org/apache/avalon/phoenix/tools/assembly.dtd"/>
  <png key="banner"
       resource="/org/apache/avalon/phoenix/tools/phoenix.png"/>
  <png key="built-with"
       resource="/org/apache/avalon/phoenix/tools/built-with-phoenix.png"/>
  <component key="kernel"
       resource="org.apache.avalon.phoenix.components.kernel.DefaultKernel"/>
  <service key="kernel"
       resource="org.apache.avalon.phoenix.interfaces.Kernel"/>

</resources>

Each resource entry declares a single resource. Each resource has a particular type (type defined by a URI). The way that a resource is extracted from library is not specified by this toolkit. 

This approach would also allow libraries to "extend" or "cascade" existing libraries. So you could replace the resource of type "component" in above config via something like (Assuming that the above descriptor was in a library named 'phoenix')

<resources extends="phoenix" version="1.0">
  <type shortname="component"
        uri="http://jakarta.apache.org/avalon/component/1.0"/>
  <component key="kernel"
       resource="org.apache.avalon.phoenix.components.kernel.DefaultKernel"/>

</resources>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php