[esb-issues] [JBoss JIRA] Commented: (JBESB-575) Standardize on a message delivery mechanism...

Thu Jun 28 10:22:57 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBESB-575?page=comments#action_12367173 ] 

Tom Fennelly commented on JBESB-575:
------------------------------------

lol, no... I mean remove ServiceInvoker and rename MessageDeliveryAdapter to ServiceInvoker.  The only thing we want from ServiceInvoker is its name ;-)

> Standardize on a message delivery mechanism...
> ----------------------------------------------
>
>                 Key: JBESB-575
>                 URL: http://jira.jboss.com/jira/browse/JBESB-575
>             Project: JBoss ESB
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2 Milestone Release 2
>            Reporter: Tom Fennelly
>         Assigned To: Tom Fennelly
>             Fix For: 4.2
>
>
> A few "(anti-)patterns" have developed re ESB-Aware message delivery to an endpoint:
> 1. Raw code that deals right down to the level of EPRs and Couiers (Yeuukieee...).  The code is littered with this stuff :-(
> 2. Classes like the ServiceInvoker (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/src/org/jboss/soa/esb/listeners/ServiceInvoker.java) and MessageDeliveryAdapter (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/src/org/jboss/soa/esb/listeners/message/MessageDeliveryAdapter.java).  Both of these classes essentially do the same thing.  They're created against a Service Cat:Name combo and they take care of looking up EPRs and Couriers etc.
> Basically, I think we should settle on using one of classes listed in #2, and (where the opportunity arises) remove that ugly code described in #1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira