Possible bug with DevKit connectors and until-successful MP?

[Franco Gasperino]

I've found that Mule 3.2 connectors using the new DevKit annotations seem to not play nice with with the until-successful processor. Since the new connector annotations perform connection management based on state, these seem to throw off the conditional evaluation for the message processor.

If needed, I can create a JIRA ticket for it, but cannot post a test case in the near term due to licensing.

Has anyone else experienced this?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[Emiliano Lesende]

Franco,

Can you elaborate about what is the general problem and how would you like them to work together?

We understand that until-sucessful and the general retry mechanism of the DevKit somewhat collide in purpose but still they should function correctly when used together.

Em

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[Franco Gasperino]

In my tests, it appears that surrounding a @Connector -annotated class with <until-successful ../> will result in the first attempt of invoking a message processor in the module will trigger the until-successful, instead of first attempting the connector's built-ins.

If i use the reconnection features of the connector without a surrounding until-successful, the connector will immediately retry its configured reconnection sequence, as expected. Should I surround with the until-successful, a failed connector message processor (due to invalid connection state), retry control will be passed back to the until-successful processor instead of first attempting the connector's retry behavior.

Ideally it would be:
1. Connector detects an invalid connection.
2. Connector attempts manager-level retry sequences (http://www.mulesoft.org/documentation/display/DEVKIT/Managing+Connections)
3. Connector fails to operate properly, passing through exception state to the until-successful processor.

Currently it seems the order is 1,3,2.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email