avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Updated: (RUNTIME-4) Provide a way to disable automatic dependency discovery
Date Fri, 07 May 2004 01:41:56 GMT
The following issue has been updated:

    Updater: Stephen McConnell (mailto:mcconnell@apache.org)
       Date: Thu, 6 May 2004 6:40 PM
             Version changed to 3.2
             Component changed to Composition
             Fix Version changed to 4.0
For a full history of the issue, see:


View the issue:

Here is an overview of the issue:
        Key: RUNTIME-4
    Summary: Provide a way to disable automatic dependency discovery
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Merlin Runtime Platform
   Fix Fors:

   Reporter: Scott Brickner

    Created: Fri, 9 Apr 2004 3:14 PM
    Updated: Thu, 6 May 2004 6:40 PM
Environment: Currently running under Merlin 3.2.4 on Sun's JDK 1.4.2 (also 1.5 beta) on RedHat

Can we have a way to disable Merlin's automatic discovery of components?

I have quite a number of distinct instances of a single component (a work queue). Each work
queue represents a different stage of processing within my application. Each queue is serviced
by a different component, usually resulting in further work items being enqueued to other
queues. My block.xml specifies which components service which queues, and then which subsequent
queues receive the output work items.

Unfortunately, if I forget to explicitly put the output queue mappings into the block.xml,
the system begins to fail in mysterious ways. Merlin has simply chosen one of the two dozen
work queues in some arbitrary fashion and enqueued the item there where it's not expected.

I'd really rather be able to put something in my block.xml - perhaps on a <container/>
tag to indicate that the automatic component discovery should be disabled within that component
and that dependencies which aren't explicitly filled by entries in the block.xml should result
in a failure to deploy.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message