Hi, When I was debugging this persistence issue [1], I noticed that version of some modules are not set correctly. For example, at module deploy time, there were one version (which will be persisted). And then, during a service deployment time, when I see the version of those modules, I see a different one. For example, for metering the persisted module version was *2.1 *but at service deployment time, it says *2.0*. This was observed for wso2throttle too 4.0/4.1.
This is the reason why these issues are arises. I know that there's no versioning concept for modules. But when I look at the module metadata, I see that there can be one module with several versions. And, I can retrieve each of these module versions from AxisConfiguration IIRC. I don't think there were duplicated jars in the system that caused this issue, because this doesn't happen much frequently. (I noticed this when I tried to deploy several dbs services at one.) How should we address this issue? [1] https://wso2.org/jira/browse/DS-634 -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>* twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>* *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
