[esb-issues] [JBoss JIRA] Closed: (JBESB-1274) Support explicit MEP specification
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Wed Oct 31 01:29:54 EDT 2007
[ http://jira.jboss.com/jira/browse/JBESB-1274?page=all ]
Kevin Conner closed JBESB-1274.
-------------------------------
Resolution: Done
The actions element in the jboss-esb.xml file now suports an optonal 'mep' attribute.
If this attribute is specified then the action processing happens as follows
'OneWay' processing
- all non-error responses are ignored. This allows all actions to return a message without
concern for the service contract.
'RequestResponse' processing
- non-error responses perform the same checking as the current default but do not emit a
warning message if no EPR can be discovered. This allows a client to specify no interest
in any response from the service.
- null responses cause a warning to be emitted.
This was committed in revision 16187.
> Support explicit MEP specification
> ----------------------------------
>
> Key: JBESB-1274
> URL: http://jira.jboss.com/jira/browse/JBESB-1274
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 4.2.1 IR2
> Reporter: Kevin Conner
> Assigned To: Kevin Conner
> Fix For: 4.2.1
>
>
> At present a one-way action pipeline is supported by having one action in the pipeline return a null message to indicate termination.
> There have been numerous one-way services where this was not done, resulting in spurious messages being returned to unsuspecting services.
> We need to support an explicit specification of the mep so that actions are free to return a message without concern over the outcome of the pipeline processing.
--
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
More information about the esb-issues
mailing list