Support Forums: Message List - Welcome to the Jumble - J2EE best practices

Welcome to the Jumble - J2EE best practices

Wed, 02 Jun 2004 02:24:24 -0400

# Use JSP for the presentation Layer

I completely DISAGREE with this best pratice. Gone are the days when the presentation layer is simply a dumb layer doing no processing/ minimal processing(Writing JavaScript for vallidations!!!!)....Have...

Bes Practice Redefined

Fri, 28 May 2004 09:51:41 -0400

I agree,

Very often, project teams decided upon the technology, (or have it imposed) before they analyse the system requirements. Best practice is solving your problem using the most "apppropriate" technology. The Agile development...

distributing for security, why not

Fri, 28 May 2004 03:59:32 -0400

Actually my post was a little bit on another subject, namely distributed (XA) transactions, whose entire purpose is to orchestrate simultaneous updates on more than one physical resource (e.g. JDBC database(s) and JMS provider(s)). In other words, as JMS...

the network.. don't forget the network

Thu, 27 May 2004 20:33:29 -0400

I would say that one of the most important rules in J2EE is:

Dont forget the network: always use coarse grained remote API calls to minimise network chatter. This includes things from UI design, web to business tier, database...

JSP and web frameworks

Thu, 27 May 2004 11:11:42 -0400

JSP is not a framework like tapestry.

JSP can be horrific to work with if done badly, which has to be said is usually the case. But if implemented properly there is nothing wrong with using JSP in your J2EE project as long as it is the best option...

Why a Session bean as facade?

Thu, 27 May 2004 09:17:02 -0400

...I use classes (Called 'accessors') that are serializable as facades...

Why do you want to serialize your façades?
At the end of the day, if they do the same thing, façade or accessor, then the name doesn't matter...

to distribute or not to distribute

Thu, 27 May 2004 09:11:59 -0400

Timur,

I like the subject of your post and I'd like to pull its cover a little bit more toward the business component layer away from the database.

Distributing the business objects.

Currently, we're facing a requirement on...

Welcome to the Jumble - J2EE best practices

Thu, 27 May 2004 08:55:53 -0400

The purpose is to promote best practices for those who chosed J2EE as a framework for their project.

I think the definition isn't correct: "J2EE being a framework".

J2EE is not only EJB spec. My Struts...

Reality check

Thu, 27 May 2004 06:42:27 -0400

A few comments, based on my (sometimes painfully gained) experience:

The number one thing of all projects, and especially in J2EE, I think, is to establish a working runtime and development environment, that is:

* Development platform and...

to distribute or not to distribute

Thu, 27 May 2004 03:22:02 -0400

5. Always use Session Facades whenever you use EJB components.Also read as "Don't use EJB unless you have a distributed transaction."

I have had very odd experience with distributed transactions. I mean, you should never...

Why a Session bean as facade?

Thu, 27 May 2004 03:06:45 -0400

#5 Always use Session Facades whenever you use EJB components.

I use classes (Called 'accessors') that are serializable as facades. Why should I prefer session beans as a facade?

Welcome to the Jumble - J2EE best practices

Thu, 27 May 2004 02:52:32 -0400

My personal rules:

1. Only use session beans when you need to provide remotely accessible services. You may find you only need a servlet engine.

2. Use an ORM tool -- JDO or Hibernate for instance, instead of entity beans. This performs...

J2EE still isn't EJB

Wed, 26 May 2004 20:12:35 -0400

I certainly know that J2EE is not EJB. That's why I think that if you choose to code JSP-servlets, you decided to choose J2EE and then all 10 best practices applies. For small sites I would consider either PHP which provides a lot more then...

Why a top 10 list?

Wed, 26 May 2004 18:11:35 -0400

I certainly know that J2EE is not EJB. That's why I think that if you choose to code JSP-servlets, you decided to choose J2EE and then all 10 best practices applies. For small sites I would consider either PHP which provides a lot more then JSP for...

Why a top 10 list?

Wed, 26 May 2004 17:59:24 -0400

Again, the question now is not if J2EE is relevant or not for your project but 10 best pratices to put in place for a project that fits J2EE. I agree that for small project, J2EE is often not the best framework to use, but it is not in...