Hi Amila,

Your understanding is correct, and the operation element is expected to add an operation to the service at the module engagement time.

What is the axis2 version that you are trying? This works on the trunk as well as most of the recent releases of axis2 and WSO2 based products, so it is hard to assume this as a bug on the axis2 or caching code. Have you deployed the module correctly and engaged it.

Thanks,
Ruwan

On 11/5/10 4:14 AM, Amila Liyanaarachchi wrote:
Hi Devs,

What exactly expected from putting the <operation> block in a module.xml file? Does it add that operation to the services when the module get engaged?

For example the module.xml of the caching module contains the following block, <operation name="CachedOperation" mep="http://www.w3.org/2006/01/wsdl/in-out";> <messageReceiver class="org.wso2.caching.receivers.CachedMessageReceiver"/>
</operation>

Then in the CachingInHandler it tries to access this operation from this code, AxisOperation cachedOperation = axisService.getOperation(CachingConstants.CACHED_OPERATION_QNAME);

where CACHED_OPERATION_QNAME = "CachedOperation"

I have moved the carbon\caching module to Axis2 and when I was debugging it can not find an operation with name "CachedOperation". Then I checked the axisService.operationsAliasesMap it also does not contain the "cachedOperation".

What may be the reason for this operation not being present in a service?

Thanks,
Amila


_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


--
Ruwan Linton
Software Architect&  Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: [email protected]; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton

_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to