Archive for January, 2009
Making applications work together in Eclipse
Eclipse as we know is a great implementation of plugin-architecture.
We decouple different components of a system into bundles.
plugin-architecture is very simplistic in nature, highly extensible and modular at the cost of a tricky class-loading policy.
Actually Eclipse is a story of several class-loaders.
It iniataites a chain of class loaders to load the plug-ins lazily as specified in component-specific manifest.mf files.
If we understand its class-loading policy and learn some tricks, then we can make different third-party jars talk to each other and avoid infamous ‘ClassNotFound Exception’.
Agile QA- ideal for Product testing
A meticulous QA release plan, even more carefully designed test cases down to the minutest detail and all geared up QA engineers to execute the QA phase—-what more could a QA lead ask for? The icing on the cake of course is “A four month long dedicated QA phase” begins with almost nothing working in [...]