Hello devs. As you all know, best-practices for module development aren't always super-well documented, and as the platforms that we incorporate get smarter, that gives us opportunities to try new patterns, and lessons learned don't always propagate to the community, even if they're sitting in a module ticket, for example.
So, in this spirit, here's a small lesson learned: The current build of metadatasharing has a pretty liberal use of the @autowire annotation. What this does for us here in rwink is increase the load time of the metadatasharing module by a factor of maybe 10 or 15 (depending on how many other modules are installed at any given time). On a clean 1.6.3 installation, the 'regular' module load time is maybe 20 seconds on our test server (assuming that only the logic module is running, and i install htmlformentry, for example). Then, when I install metadatasharing, the load time jumps to 4+ minutes. And then increases for any other modules that i want to load on top of that. There was already a ticket for this, and future versions of metadatasharing won't have this problem. But i thought there was a best-practice point here: If you don't enjoy writing xml bean files, tough. Please don't @autowire. Its too slow. thanks, d _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
