Thoughts on Software Development Trends, Enterprise Architecture, Design, Big Data, and Cloud Computing.
Sun had announced the open sourcing of more components of the Java platform under GPL2 License yesterday. Sun’s promise to open Java is well underway to being fulfilled. The components that are being released are the Java C Compiler, HotSpot VM (Virtual Machine), and the Java Helpdesk.
Technorati tags: Sun, Java, OpenSource
I happened to know about “Foxit Reader 2.0“; an incredibly small sized PDF reader from Mr.Vadivel’s blog. In his post he had explained about the reason of migration through some of the disadvantages of the commonly used Adobe PDF reader. And I decided just to test this new one. But WOW! For my surprise it took no time for the installation!!! One sec?? Naa.. 🙂
Its has some good features too. Lets check some of them taken from their official site.
Technorati tags: Foxit Reader, PDF reader
1. Spring Provides Better Leverage
2. Spring Enables POJO Programming
3. Dependency Injection Helps Testability
4. Inversion of Control Simplifies JDBC
5. Spring‘s Community Thrives
Read more on this here
Technorati tags: Spring FrameworkÂ
Spring is a powerful Java application framework, used in a wide range of Java applications. It provides enterprise services to Plain Old Java Objects (POJOs). Spring uses dependency injection to achieve simplification and increase testability.
1. Spring provides a very clean division between controllers, JavaBean models, and views.
2. Spring’s MVC is very flexible. Unlike Struts, which forces your Action and Form objects into concrete inheritance (thus taking away your single shot at concrete inheritance in Java), Spring MVC is entirely based on interfaces. Furthermore, just about every part of the Spring MVC framework is configurable via plugging in your own interface. Of course we also provide convenience classes as an implementation option.
3. Spring, like WebWork, provides interceptors as well as controllers, making it easy to factor out behavior common to the handling of many requests.
4. Spring MVC is truly view-agnostic. You don’t get pushed to use JSP if you don’t want to; you can use Velocity, XLST or other view technologies. If you want to use a custom view mechanism – for example, your own templating language – you can easily implement the Spring View interface to integrate it.
5. Spring Controllers are configured via IoC like any other objects. This makes them easy to test, and beautifully integrated with other objects managed by Spring.
6. Spring MVC web tiers are typically easier to test than Struts web tiers, due to the avoidance of forced concrete inheritance and explicit dependence of controllers on the dispatcher servlet.
7. The web tier becomes a thin layer on top of a business object layer. This encourages good practice. Struts and other dedicated web frameworks leave you on your own in implementing your business objects; Spring provides an integrated framework for all tiers of your application.
8. No ActionForms. Bind directly to domain objects
9. More testable code (validation has no dependency on Servlet API)
10. Struts imposes dependencies on your Controllers (they must extend a Struts class), Spring doesn’t force you to do this although there are convenience Controller implementations that you can choose to extend.
11. Spring has a well defined interface to business layer
12. Spring offers better integration with view technologies other than JSP (Velocity / XSLT / FreeMarker / XL etc.)
Reference: Here
Orange Slate 