ws-muse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kam K. Yee (JIRA)" <>
Subject [jira] Updated: (MUSE-243) Dynamic discovery and aggregation of resource types
Date Mon, 07 Apr 2008 14:35:25 GMT


Kam K. Yee updated MUSE-243:


Attached is the implementation of this new feature contributed by the IBM Team

> Dynamic discovery and aggregation of resource types
> ---------------------------------------------------
>                 Key: MUSE-243
>                 URL:
>             Project: Muse
>          Issue Type: New Feature
>          Components: Core Engine - Resource and Capability APIs
>            Reporter: Balan Subramanian
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>         Attachments: muse-243 - Dynamic discovery and aggregation of resource types.pdf,
> In some cases all resource type definitions are not available at the time the Muse runtime
starts. So even though multiple resource types can be hosted by a single Muse instance, all
the resource type definitions must be available before Muse starts and listed in muse.xml.
It is desired that Muse be made dynamic so that it can monitor a particular folder where an
archive (JAR for example) is dropped. This archive will contain the necessary classes, descriptors,
router entries etc. and a muse.xml fragment which will be used by Muse to instantiate the
specified instances of that resource type. As an additional enhancement, it is desired that
in addition to support archive files, Muse supports this feature for OSGi bundles by registering
with the OSGi container's bundle registry. This enhancement is applicable only when the runtime
environment for Muse is OSGi.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message