Reacties op: Java best practices

Door: Madhu

Madhu — Wed, 26 Mar 2008 11:18:10 +0000

very good article. which is very much help ful for me.thanks

Door: JAVA development en vacatures voor Java software specialisten » Java best practices 5 - Code to Interface, Access by name and Instance Data

Sun, 07 Oct 2007 18:17:27 +0000

[...] Java best practices 5 – Code to Interface, Access by name and Instance Data oktober 7, 2007 on 7:17 pm | In Java | [...]

Door: JAVA development en vacatures voor Java software specialisten » Java best practices 4 - Native Arrays and Not Using Java 5.

Mon, 03 Sep 2007 14:47:53 +0000

[...] Java best practices 4 – Native Arrays and Not Using Java 5. september 3, 2007 on 3:47 pm | In Java | [...]

Door: JAVA development en vacatures voor Java software specialisten » Java best practices 3 - Eating Exceptions and Mixing JSTL with JSF

Sun, 26 Aug 2007 22:35:17 +0000

[...] Java best practices 3 – Eating Exceptions and Mixing JSTL with JSF augustus 26, 2007 on 11:35 pm | In Java | [...]

Door: Over Java development en vacatures voor Java software specialisten » Java best practices 2 - Explicit cases

Wed, 15 Aug 2007 20:58:08 +0000

[...] Java best practices 2 – Explicit cases augustus 15, 2007 on 9:58 pm | In Java | [...]

Door: links for 2007-08-14 « My Weblog

links for 2007-08-14 « My Weblog — Tue, 14 Aug 2007 04:18:01 +0000

[...] Over Java development en vacatures voor Java software specialisten Â» Java best practices (tags: java) [...]

Door: arjan

arjan — Mon, 13 Aug 2007 17:32:55 +0000

Good point to mention Sam! It's indeed one of the things I look for when checking source code. A consistent coding style is often much easier on the eyes and more pleasant to use.

A consistent API is also much easier to learn for new people and often faster to debug.

Door: Sam

Sam — Mon, 13 Aug 2007 17:05:04 +0000

What annoys me is people not copying the style of existing code. So what if at your last job you put an I at the start of all your interfaces, its pretty easy to see thats not done here. Totally aside for the argument of if thats a good or bad idea, its always going to be a bad idea to have n styles of coding.

Door: arjan

arjan — Mon, 13 Aug 2007 16:11:59 +0000

Hazem, I absolutely agree with you. Just mixing JSTL and JSF is not a bad practice by itself. The emphasis however is on -sometimes-. Sometimes its ok, sometimes its not. In one of the next installments of this blog I’ll discuss a case where its not ok.

Door: Hazem Ahmed Saleh

Hazem Ahmed Saleh — Mon, 13 Aug 2007 11:20:02 +0000

Dude,
In some times, you may need to mix JSTL with JSF code.
Check JSF 1.2 specs.