Naming on JBoss, this article from informit explains JNDI and JBossNS Architecture nicely. It is a sample chapter from book JBoss 4.0- The Official Guide by Marc Fleury, Scott Stark.
It goes through the fundamentals of JNDI and uses JBossNS as an example to explain how to use it in the real world.
Thursday, December 22, 2005
Wednesday, December 14, 2005
Coupling and cohesion
Well a lot is a talk about loose coupling and high cohesion in Java world and OO Programming in general. So just for reference here is excerpts from tutorial "Coupling and Cohesion: The Two Cornerstones of OO Programming" (Link: http://javaboutique.internet.com/tutorials/coupcoh/). Tutorial discusses the matrices for measuring coupling and cohesion in OO Programs.
"Object-oriented programming has two main objectives: to build highly cohesive classes and to maintain loose coupling between those classes. High-cohesion means well-structured classes and loose coupling means more flexible, extensible software."
"Cohesive means that a certain class performs a set of closely related actions. A lack of cohesion, on the other hand, means that a class is performing several unrelated tasks. Though lack of cohesion may never have an impact on the overall functionality of a particular class or of the application itself the application software will eventually become unmanageable as more and more behaviours become scattered and end up in wrong places."
"Whenever one object interacts with another object, that is a coupling. In reality, what you need to try to minimise is coupling factors. Strong coupling means that one object is strongly coupled with the implementation details of another object. Strong coupling is discouraged because it results in less flexible, less scalable application software. However, coupling can be used so that it enables objects to talk to each other while also preserving the scalability and flexibility."
"In OO programming, coupling is unavoidable. Therefore, the goal is to reduce unnecessary dependencies and make necessary dependencies coherent."
"Object-oriented programming has two main objectives: to build highly cohesive classes and to maintain loose coupling between those classes. High-cohesion means well-structured classes and loose coupling means more flexible, extensible software."
"Cohesive means that a certain class performs a set of closely related actions. A lack of cohesion, on the other hand, means that a class is performing several unrelated tasks. Though lack of cohesion may never have an impact on the overall functionality of a particular class or of the application itself the application software will eventually become unmanageable as more and more behaviours become scattered and end up in wrong places."
"Whenever one object interacts with another object, that is a coupling. In reality, what you need to try to minimise is coupling factors. Strong coupling means that one object is strongly coupled with the implementation details of another object. Strong coupling is discouraged because it results in less flexible, less scalable application software. However, coupling can be used so that it enables objects to talk to each other while also preserving the scalability and flexibility."
"In OO programming, coupling is unavoidable. Therefore, the goal is to reduce unnecessary dependencies and make necessary dependencies coherent."
Friday, December 02, 2005
Book: JBoss at work
JBoss at work is fast and easy way to stat with JBoss and J2EE. I will highly recommend it for the beginners.
Reference:
1. http://www.xpressionsz.com/?p=717
2. http://www.jbossatwork.com/
Subscribe to:
Posts (Atom)
Posts
