You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by Supun Kamburugamuva <su...@gmail.com> on 2008/07/01 08:32:24 UTC

Specifying MEP in services.xml for non in-only operations should be mandatory

Hi all,

Previously it wasn't mandatory to specify the MEP in the services XML for
operations. But due to the recent fixes non in-out message patterns are not
working properly without the MEP in some scenarios. The need arises in case
of fault messages. If the service business logic is not implemented for an
in-out MEP, withought the MEP Axis2/C cannot deside weather the behaviour is
logical or not. This happens because for a in-only message the service
doesn't return a value.

Now we are checking the MEP in the message receiver. So if a in-only
operation doesn't specify the MEP in the service XML it will fail. Also we
need to add this to code generation as well.

Here are the Jiras that are related to this

https://issues.apache.org/jira/browse/AXIS2C-1215
https://issues.apache.org/jira/browse/AXIS2C-1213
https://issues.apache.org/jira/browse/AXIS2C-1154

Regards,
Supun..