Page History

...

<sm:activationSpec targetUri="interface:http://www.foo.bar/MyInterface">
 ...
 </sm:activationSpec>

EIP component

...

See servicemix-

...

eip.

URI syntax

The ServiceMix container can parse the following URIs:

...

It is up to binding components to resolve such EPR and provide an adequate ServiceEndpoint.
If used to resolve an EPR, only the endpoint: protocol can be used.

Currently, only the servicemix-http and servicemix-jms BCs are able to resolve such endpoints. 

Examples

• interface:urn:foo:bar:MyInterface
• operation:http://foo.bar/MyInterface/MyOperation
• service:http://foo.bar.org/MyService
• endpoint:urn:foo:bar:MyService:MyEndpoint
• http://localhost:8192/service/?http.soap=true
• jms://queue/foo...

Basic idea

Use a simple URI syntax to refer to explicit JBI endpoints. e.g.

• jms://activemq/queue/FOO.BAR?persistent=true
• file://foo/bar
• http://host:port/whatnot
• interface:qname
• service:qname
• spring://contextName/pojoName

...

• bar.myqueue?jms.soap=true

Auto-creation

TODO: allow the use of URIs to expose a JBI endpoint over several transports without having to rely on creating a Service Unit for each component.

One of the neat things about using ActiveMQ is that once its up and running, you can refer to JMS endpoints (queues/topics) by name and things are auto-created for you by default. If required you can apply security access roles to this to prevent certain users creating new endpoints within a namespace.

...