[
https://issues.apache.org/jira/browse/MUSE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527261
]
Kam K. Yee commented on MUSE-243:
---------------------------------
I had a few comments/questions...
1. Its been mentioned in the comments for this JIRA and implied in the design
document, but it might be worth explicitly stating in the design document that
this feature is targetted for the J2EE Axis2 and the mini runtimes only (and
not OSGi).
2. In the feature description section, there are a couple of statements
implying that no reboot of the server will be needed and that the new resource
types will be detected, loaded and available without needing a server bounce.
Is the feature implementation going to be truly dynamic or will it require a
restart of the server?
3. In the "Axis2" subssection under "Design and Architecture", will the
structure of the resource type jar be compatible with how an Axis2 services
archive (.aar (?)) is packaged? In other words, will dropping a resource type
jar be recognized as a new service by Axis2?
> 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]
