| Key: |
MULE-3638
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Dimitar Dimitrov
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Labels: |
|
| User impact: |
High
|
| Configuration: |
<endpoint name="abstract.foo" address="protocol://user:pass@blah.blah/foo/bar?key=value#fragment"/>
<endpoint name="foo" ref="abstract.foo" transformer-refs="FOO BAR" remoteSync="true">
<property key="cache" value-ref="cache.foo"/>
</endpoint>
<endpoint name="abstract.foo" address="protocol://user:pass@blah.blah/foo/bar?key=value#fragment"/>
<endpoint name="foo" ref="abstract.foo" transformer-refs="FOO BAR" remoteSync="true">
<property key="cache" value-ref="cache.foo"/>
</endpoint>
|
| Migration Impact: |
None - the schema allows the ref attribute and the schema docs say:
A reference to a global endpoint.
If this attribute is used then the endpoint is used as a template to construct this endpoint.
A template fixes the address (protocol, path, host, etc), and may specify initial values for
various properties, but further properties can be defined locally (as long as they don't
change the address in any way).
None - the schema allows the ref attribute and the schema docs say:
A reference to a global endpoint.
If this attribute is used then the endpoint is used as a template to construct this endpoint.
A template fixes the address (protocol, path, host, etc), and may specify initial values for
various properties, but further properties can be defined locally (as long as they don't
change the address in any way).
|
In the configuration bellow, I am trying to define a minimal "abstract" endpoint, defining only the address; and use it as a base for a service endpoint (defining everything else). Mule fails with error that the EndpointBuilder does not have a "ref" property.
In my real scenario, both definitions reside in different files. I have multiple versions of the file containing abstract endpoints - one for unit testing, one for QA (where some systems are stubbed, some are real) and a third one for UAT and PROD. Right now I repeat the transformers and filter deffinitions in all three files, but it's getting annoying.
|
|
Description
|
In the configuration bellow, I am trying to define a minimal "abstract" endpoint, defining only the address; and use it as a base for a service endpoint (defining everything else). Mule fails with error that the EndpointBuilder does not have a "ref" property.
In my real scenario, both definitions reside in different files. I have multiple versions of the file containing abstract endpoints - one for unit testing, one for QA (where some systems are stubbed, some are real) and a third one for UAT and PROD. Right now I repeat the transformers and filter deffinitions in all three files, but it's getting annoying. |
Show » |
|
Allow global endpoints to extend other global endpoints
If I understood correctly this is more like a feature request than a bug I think. You want to be able to have one global endpoint extend another global endpoint. The reference you are using fails because it's a reference from a global endpoint rather than from a concrete endpoint.