[ 
https://issues.apache.org/jira/browse/MUSE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530046
 ] 

Arun Ramakrishnan commented on MUSE-243:
----------------------------------------

I have a couple of questions about this.

1) Do we need some interface, like a listener, to notify muse of the updates 
and pass on the jar file so that muse can load resource types? The 
ResourceTypeLoaderPoller will need to have add/remove listener methods then. 
That way the code that loads the resource type from the jar will be independent 
of the code polling (actively or at initialization) a directory.

2) If a user wants to directly change the DirectoryPoller, where will this be 
configured? Another element in muse.xml right? Since the DirectoryPoller is a 
Runnable, and will be managed by the ResourceTypeLoaderPoller this means that 
by changing only the DirectoryPoller, and using the default 
ResourceTypeLoaderPoller, we still will use a threaded approach?


> Dynamic discovery and aggregation of resource types
> ---------------------------------------------------
>
>                 Key: MUSE-243
>                 URL: https://issues.apache.org/jira/browse/MUSE-243
>             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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to