Specialization  -  Specialized in Coffee. Need not worry what is
happening inside to make worth coffee cup

Interface – Always the same interface, ask for a coffee at counter, pay the
amount and get the coffee

Reliability - Whether in US, Europe, India the taste is the same

And Liferay too does in the similar fashion, same services with almost any
Operating System, Application server and database combination.

Few other sessions are covered by Binil on his blog post JAX India 2007:
Day 4 report

Well in all JAX India, though looked promising with the
Buzzy catchy title, the overall feeling was that it didn’t meet what
was expected out if it. I was really surprised at the Oracle counter,
where I asked info about their new Web Center suite and the answer I got back
is to fill a feedback form and get the CDs which has all the information.
If that is the case, I am better of searching over Internet

Also, in terms of arrangement, there was a lot of confusion about which
session happening in which Hall. It was a complete mess and people were just
running around to catch up with the sessions. I was in Hall B for a session
and the next which I wanted to attend was in Hall A. So after session I sent
to Hall A to get a surprise that the session I want to attend has been shifted
to Hall B. The time I reached there, all the seats were full and there was
hardly any space to stand. A better organization is required.

Anyways Thanks SDA India for hosting such event and looking forward to a
better organized and more targeted sessions next time. A Big thanks to all the
speakers who cam all the way to share their experience and knowledge.

More reading at  Hits and Misses: JAX India 2007

Introduction to JSF for Struts Developers – Craig McClanahan

The session was targeted to cover an overview about Java Server Faces. The agenda includes:

Origin of Struts

Craig started with giving an overview of how Struts came into existence.
The main reasons was

• Multiple language support

• Available on the web

• Separate responsibilities into layers etc.

In the Mean Time…

As the time went on, Standardization started taking up the market with lots of new Standards, like componenting for interoperatability, target for drag and drop etc.

JSF Key Concepts

Craig stretched on the key concept of Components which brought JSF in existence.

In all the session did touch upon the high level fundamentals of JSF but my expectations were different. I would have preferred a sandpit project like Hello World demo which would have given a better understanding. Anyways this is my thought.

The second session was an interesting presentation on IDEs future.
Java IDE(s) – Then, Now and Eventually – David Intersimone

The session was around 20 minutes but the content of the presentation was really good. Few key things from the presentation:

Future of IDEs

• Support for Rich Internet Applications

• Support for Ajax

• Collaborative features within IDE

The next session that I attended was Increase Project Success with Java Architecture Management – Alexander Von Zizewitz.  The presentation was really cool !!! He depicted dragon as the Complex Java Project with a small man with sword and shield in his hand as us trying to overcome the dragon Here are few interesting points from his presentation:

Known project problems

• Time Pressure

• Skills not meeting system requirements

• Unwanted dependencies

• Complexity growing

And if we fall in the pitfall of the above problems, we start just making it work and then start the real problem like:

• Increase in testing time

• Problems with deployment

• Making changes become increasingly difficult

So what are the ways to control Java Projects that Dragon doesn’t rule the world:

• Avoid Package cycles by using jdepend

• Code Reviews specially peer-to- peer

• Check Style and FindBugs Tools usage

• Checking key metrics on regular basis

• Define architecture of the system at high level of abstraction
  • Cut horizontal into layers to represent different layers like
    User Interface, Business Layer, Data layer

  • Cut vertically into slices to represent actors

  • Define allowed usage for each actor
• Define useful matrix threshhold

So once your system is divided into horizontal layers and vertical slices, start mapping code to logical diagram on the following lines:

• Each package mapped to exactly one sub system

• Good naming convention

• Subsystem should have well defined interfaces

• Work independently
  • Start with layering

  • Add vertical slices

  • Define subsystem interface

  • Fine tune rules of engagement on subsystem level

Once you are done with this, measure the overall coupling at system level, sub system level, package level etc. using Component Dependency technique.

5 Golden Rules to ensure technical Quality

• Create cycle free logical architecture
• Avoid package cycle
• Keep Average Component Dependency low
• Keep size of Java files ( < 700 LoC)
• Define threshhold for complexity

 In all the presentation was interesting and provoke at looking more into SonarJ tool which Hello2omorrow has come up with to solve such issues.

Apart from these I attended Best practices for inter-operable Web Services – Thilo Frotscher, the details of the session are already covered by Amit in this blog.

In all the sessions are not too much impressive may be due to limited time allotted for each session. Looking forward to Day 3 at Jax India 2007.