[
https://jira.jboss.org/jira/browse/JBESB-1975?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-1975.
-------------------------------
Resolution: Rejected
The mep attribute does not define the behaviour from a service contract perspective but
rather from the view of the pipeline implementation.
It is perfectly valid for one service, defined as a OneWay, to forward a request to a
second service in order to generate a response to the client.
MEP type and out XSD attributes should be forced to be in sync
--------------------------------------------------------------
Key: JBESB-1975
URL:
https://jira.jboss.org/jira/browse/JBESB-1975
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.4 CP1
Reporter: Jiri Pechanec
Priority: Critical
Right now the WSDL generated MEP is based on presence of outXSD attribute but real
behaviour is based on MEP attribute of service. Thi can lead to async invocation of sync
service (not a big problem) or sync invocation of async service - this can cause to hard
to detect bugs.
ESB should throw and error when the outXsd and mep attributes are not synced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira