Quick Table of Contents
  1. Table of Contents
  2. Preface
  3. Section 1: Application Design Concepts and Principles
  4. Section 2: Common Architectures
  5. Section 3: Integration and Messaging
  6. Section 4: Business Tiers Technologies
  7. Section 5: Web Tier Technologies
  8. Section 6: Applicability of Java EE Technology
  9. Section 7: Patterns
  10. Section 8: Security

Iterator

Description

A way to traverse the elements of an aggregated complex object, without knowing the underlying structure.

Scenario

Benefits

Drawbacks

Related patterns

Comments
Faizal - 15 April 2012To me, the whole argument on haanurign notation is like the following short story:A: Your code is awful!B: What?! How dare you!A: No, I meant that as a compliment! You see, awful means causes awe , and I think your code is so great as to cause awe in me. Therefore, I say it's awful. People have misunderstood the word awful for years.Some of the posts I read on haanurign notation can be simplified to Hungarian notation is the act of giving your variables good names. Who is against giving your variables good names? No one? See, you are all haanurign notation users! Why bother labelling people this way? If you want people to use a certain naming scheme for variables, just tell them to use that naming scheme. If people don't like being called haanurign notation users because of some emotional responce to the term haanurign notation , don't call them haanurign notation users. As long as we use a good naming scheme, who cares what that naming scheme is called?BTW, as a French speaker, Preuve par Neuf can be literally translated as Proof by nine .
Leave a comment


Name:*
Email:
Message:*
Security code:*
(type the code in the text field)