Mule

Provide default model and service names

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Fixed
  • Affects Version/s: 2.0.0-RC2
  • Fix Version/s: 2.0.0-RC3
  • Component/s: Core: Configuration
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    MULE-3146 Services should use the Model ExceptionStrategy if none is specified on the service itself
    MULE-5895 As a user I want to be able to define a custom default exception strategy that is used when a a flow or service does not define one explicitly
    MULE-14 Default exception strategy on the Model
    MULE-4515 default-service-exception-strategy does not honor exception-type-filter
    MULE-5227 Unable to set namespace, service and endpoint name because MuleServiceConfiguration has no effect
    MULE-3202 Users can no longer set a default pooling-profile in a seda-model
    MULE-2097 Migrate unbounded choice model group's in schema in favor of sequence/all where applicable
    MULE-1753 "stream.message.adapter" not set when streaming model used
    MULE-2108 JSR181 annotations not used during service name lookup in XFire service registry.
    MULE-4040 Re-introduce the Inherited Model

Description

Model and service names often aren't used. It's trivial to provide a default from the UUID library, so let's do that.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
andrew cooke added a comment - 19/Feb/08 12:04 PM

Done (but used spring config code to provide default, not uuids).

Show
andrew cooke added a comment - 19/Feb/08 12:04 PM Done (but used spring config code to provide default, not uuids).
Hide
Permalink
Ross Mason added a comment - 19/Feb/08 06:10 PM

Service names should NOT be auto generated, please revert this. Think about how you would manage a service over JMX. A property service name is always required. Model names can be generated.

Also Agent names should be fixed.

Show
Ross Mason added a comment - 19/Feb/08 06:10 PM Service names should NOT be auto generated, please revert this. Think about how you would manage a service over JMX. A property service name is always required. Model names can be generated. Also Agent names should be fixed.
Hide
Permalink
andrew cooke added a comment - 29/Feb/08 06:34 AM

if you want to specify a name for jmx, you can. i only added the option to omit the specification - most people don't use jmx, so why force them to name something?

anyway, will make it required in the schema.

Show
andrew cooke added a comment - 29/Feb/08 06:34 AM if you want to specify a name for jmx, you can. i only added the option to omit the specification - most people don't use jmx, so why force them to name something? anyway, will make it required in the schema.

People

Vote (0)
Watch (0)

Dates

  • Created:
    19/Feb/08 11:29 AM
    Updated:
    29/Feb/08 09:21 AM
    Resolved:
    29/Feb/08 09:21 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.