[
https://issues.apache.org/jira/browse/MUSE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527055
]
Chris Twiner commented on MUSE-243:
-----------------------------------
I would like to request two things,
1) that the "monitoring" thread is easy to replace and
2) that there is a simple public interface for adding extra muse.xml fragments.
For point 1) in J2EE environments the creation of Threads is a big no-no.
Wherever possible I replace Threads with Work (JCA). At the very least use
Runnables instead and provide a template method to start the runnable. This
allows easy changes for J2EE compliance or allow any other threading scheme to
be used. Additionally Thread creation is expensive and should be avoided. I
would also suspect that this requires using protected member variables not
private to be useful.
2) I can recognise the need for some applications to be completely dynamic, but
for my own needs I would require that these extra locations for fragments were
explicitly configured (i.e. not just a jar drop directory) and used only at
load time.
> 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]
