THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<sm:activationSpec destinationUri="interface:http://www.foo.bar/MyInterface"> ... </sm:activationSpec> |
| Code Block | ||||
|---|---|---|---|---|
| ||||
<beans ... xmlns:my="http://servicemix.apache.org/demo/">
...
<sm:activationSpec componentName="component" service="my:service" endpoint="endpoint">
...
</sm:activationSpec>
...
</beans>
|
| Warning | ||||||
|---|---|---|---|---|---|---|
Be careful with namespaces. ServiceMix maintains an endpoint registry which it uses to look up endpoints. The example above registers the corresponding endpoint with the key:
However, an endpoint reference of
... will result in a different, non-matching key:
... which will ultimately cause the routing to fail. |
EIP component
See servicemix-eip.
...
The ServiceMix container can parse the following URIs:
interface:qnameunmigrated-wiki-markup- {{
operation:qname\[sep\]name}} service:qnameunmigrated-wiki-markup- {{
endpoint:qname\[sep\]name}}
Wiki Markup namespace\[sep\]name}}
The seprator separator used will be:
- '/' if the namespace looks like 'http://'
- ':' if the namespace looks like 'urn:foo:bar'
...