Dynamic service provider

Details

  • Type: Patch submission Patch submission
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Transport: (new transport)
  • Labels:
    None
  • Similar Issues:
    None

Description

create New service provider "dynamic". When add endpoint "dynamic://message_property" in outbound router, it will create real endpoint in runtime. The real endpoint is defined in message property: message_property. This is usefull for some application, it only know endpoint in runtime. Example:
IBM MQ's reply message for different Queue Manager. IBM MQ has Reply-Queue and Reply-QueueManager setting in MQMD. For automatically reply, it only know connector( Queue Manager) in runtime.
It could also use for Rule base message routing, see http://jira.symphonysoft.com/browse/MULE-60

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-973 Can't use TemplateEndpointRouter with SpringConfigurationBuilder

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Song added a comment -

attach implementation for this feature

Show
David Song added a comment - attach implementation for this feature
Hide
Permalink
David Song added a comment -

attach service provider configuration file

Show
David Song added a comment - attach service provider configuration file
Hide
Permalink
David Song added a comment -

Send new implementation of this provider according some suggestion by Ross Masson

Show
David Song added a comment - Send new implementation of this provider according some suggestion by Ross Masson
Hide
Permalink
Mark Panahi added a comment -

I'm really interested in this feature but it doesn't compile with 1.4 (lots of unimplemented methods). Is anyone working on getting this to work with Mule 1.4?

Show
Mark Panahi added a comment - I'm really interested in this feature but it doesn't compile with 1.4 (lots of unimplemented methods). Is anyone working on getting this to work with Mule 1.4?
Hide
Permalink
Andrew Perepelytsya added a comment -

Mark,

Please post the errors to the user list so fixes can be suggested. I can't even tell which Mule version it was designed against.

Show
Andrew Perepelytsya added a comment - Mark, Please post the errors to the user list so fixes can be suggested. I can't even tell which Mule version it was designed against.
Hide
Permalink
Mark Panahi added a comment -

I am trying to compile with 1.4.0. It looks like the dynamic provider was designed for a 1.3.x version. It seems like a lot of abstract methods were added in UMOMessageDispatcher, AbstractConnector, and UMOMessageDispatcherFactory from 1.3 to 1.4. Here are the errors. Please note this is after I tried implementing a few dummy methods myself, so you may not get the same errors in the beginning.

[INFO] Compiling 5 source files to /home/mpanahi/mule/mule-1.4.0-src/core/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

/home/mpanahi/mule/mule-1.4.0-src/core/src/main/java/org/mule/providers/dynamic/DynamicMessageDispatcher.java:[40,7] org.mule.providers.dynamic.DynamicMessageDispatcher is not abstract and does not override abstract method activate() in org.mule.umo.provider.UMOMessageDispatcher

/home/mpanahi/mule/mule-1.4.0-src/core/src/main/java/org/mule/providers/dynamic/DynamicConnector.java:[15,7] org.mule.providers.dynamic.DynamicConnector is not abstract and does not override abstract method doStop() in org.mule.providers.AbstractConnector

/home/mpanahi/mule/mule-1.4.0-src/core/src/main/java/org/mule/providers/dynamic/DynamicMessageDispatcherFactory.java:[18,7] org.mule.providers.dynamic.DynamicMessageDispatcherFactory is not abstract and does not override abstract method validate(org.mule.umo.endpoint.UMOImmutableEndpoint,org.mule.umo.provider.UMOMessageDispatcher) in org.mule.umo.provider.UMOMessageDispatcherFactory

Show
Mark Panahi added a comment - I am trying to compile with 1.4.0. It looks like the dynamic provider was designed for a 1.3.x version. It seems like a lot of abstract methods were added in UMOMessageDispatcher, AbstractConnector, and UMOMessageDispatcherFactory from 1.3 to 1.4. Here are the errors. Please note this is after I tried implementing a few dummy methods myself, so you may not get the same errors in the beginning. [INFO] Compiling 5 source files to /home/mpanahi/mule/mule-1.4.0-src/core/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /home/mpanahi/mule/mule-1.4.0-src/core/src/main/java/org/mule/providers/dynamic/DynamicMessageDispatcher.java:[40,7] org.mule.providers.dynamic.DynamicMessageDispatcher is not abstract and does not override abstract method activate() in org.mule.umo.provider.UMOMessageDispatcher /home/mpanahi/mule/mule-1.4.0-src/core/src/main/java/org/mule/providers/dynamic/DynamicConnector.java:[15,7] org.mule.providers.dynamic.DynamicConnector is not abstract and does not override abstract method doStop() in org.mule.providers.AbstractConnector /home/mpanahi/mule/mule-1.4.0-src/core/src/main/java/org/mule/providers/dynamic/DynamicMessageDispatcherFactory.java:[18,7] org.mule.providers.dynamic.DynamicMessageDispatcherFactory is not abstract and does not override abstract method validate(org.mule.umo.endpoint.UMOImmutableEndpoint,org.mule.umo.provider.UMOMessageDispatcher) in org.mule.umo.provider.UMOMessageDispatcherFactory
Hide
Permalink
Andrew Perepelytsya added a comment -

Those are pretty trivial to implement, quite often they can be just no-ops (have a look at some other transports).

Show
Andrew Perepelytsya added a comment - Those are pretty trivial to implement, quite often they can be just no-ops (have a look at some other transports).
Hide
Permalink
Mark Panahi added a comment -

Ok, thanks. I'll do that and post a new version if I can get it working.

Show
Mark Panahi added a comment - Ok, thanks. I'll do that and post a new version if I can get it working.
Hide
Permalink
Daniel Feist added a comment -

This can almost certainly be achieved with template based router, recipient list router or expressions. Even if not a new "dynamic" transport is the correct approach for this.

Show
Daniel Feist added a comment - This can almost certainly be achieved with template based router, recipient list router or expressions. Even if not a new "dynamic" transport is the correct approach for this.

People

  • Assignee:
    Unassigned
    Reporter:
    David Song
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: