Pages

Thursday, November 28, 2013

Monday, November 18, 2013

Considerations on using thirty party libraries to build your application.

Have you ever thought twice when you use a third party java library to implement your system? Well you should. Some of the reasons are
  1. Is the community active.(fix bugs pitfalls, and other aspects)
  2. Licensing
  3. Using many number of libraries many cause increase in dependencies on third parties.
  4. Some bugs in your system may be because of a third party library.
  5. Updating resources in the system(OS, jre, etc...) may cause the system to break and then we will have to replace the library with the updated one if exists, replace the library with another third-party software, folk the software and fix it, or re-implement the functionality by our own.
Having said that we still do need third party libraries in almost all implementations. But keeping these dependencies to a minimum is very important because of the above said reasons.

Sunday, November 17, 2013

spring webflow Introduction

What issues does spring webflow help overcome?

  1. Visualizing the flow is very difficult.
  2. The application has a lot of code accessing the HTTP session.
  3. Enforcing controlled navigation is important but not possible.
  4. Proper browser back button support seems unattainable.
  5. Browser and server get out of sync with "Back" button use.
  6. Multiple browser tabs causes concurrency issues with HTTP session data.
When spring webflow?
  1. There is a clear start and an end point.
  2. The user must go through a set of screens in a specific order.
  3. The changes are not finalized until the last step.
  4. Once complete it shouldn't be possible to repeat a transaction accidentally

How to avoid N + 1 problem in hibernate?