bala1405241511

Hi All, I am Bala, - Bala Loganathan. Joined Xisto today. I am a technical person in Java & J2EE.My strengths are Java & J2EE Technology ( no other technology) and design skills. I love reading and help people on technical issues. Please feel free to shoot a mail provided in my contact for design issues in Java & J2EE.Have a good day!Thanks & Regards,Bala

Most of the Decompiler will not give you 100% original code; method level variables are named newly. Use in connection with some good front end tools. I have been using one tool. FrontEnd Plus which uses JAD. Try this and let me know.

URL Link: JAD & FrontEnd Plus

Bala

I would like to know what are the most frequently used Gang of Four Design Patterns in Java world. Even though these patterns were quite popular for years, I could not visualize the usage beyond very common patterns like singleton, Factory, template, and composite. It would be more useful if you can share the context with the pattern usage in your projects.Thanks & Regards,Bala

Whenever you do a MVC-Based J2ee applicaton in 99% it looks like this:You have a Client UI (Web, FatClient, whatever...), you have some EJB's and a Database; Let's take - oh what surprise - an E-Bank application; now the Business Logic fits into the EJB, so when a client deposits 100 Bucks the EJB reads the actual amount and add's 100 bucks to it and updates the database...

Ups! I feel wrong here; What happends in a clustered environment with concurrent requests on the same account? What happends if in 5 years, if EJB's do not exists anymore?

I am not sure if you are talking about concurrency or two-phase commit. For concurrency you have transactional level control (transactional attributes +synchronization) which can be managed by the container. If it is two-phase commit, the answer is different. J2EE specification does not talk much about it and it assumes the delegation at each interfacing systems.

I would prefer that the business logic (what happends to an account if 100 bucks are deposited) is defined IN PROCEDURES ON THE DATABASE. ok, it still could be the EJB that invokes the procedure, but now the EJB does not know about the business logic; also, I think creating a JDBC - connection to a database is bad, the technology is slow and the approach to directly access datatables from a java program is dangerous;

Your idea is wrong.
You should not push business login into DB tier. The benefit is scalable system also we are not very successful in maintaining OO at DB tier.

Always OR mapping are the best.

Bala

Defiantly Java is an easy and smarter language.1. No pointer arithmetic like in C, C++ and Pascal2. Support in all platforms.3. Promotes open source community.Bala

I would add some design patterns java book but which one you can choose from below:

- head first design patterns

- design patterns  java workbook

1064310477[/snapback]

For me both are really good books.

 

Head first teaches in a different perspective.. Design principles are the key difference.

 

Work book explains and teaches from the basic. Hands on experience makes the difference.

 

I would love to have both.

 

Bala