Monday, December 15, 2003


One could learn the Java keywords with a poem


Abstract boolean, break the byte!
(break the scheme)
Case and catch and "char" with class!
(have your own style)
Const continue, default do.
(don't be like the others)
"double else" extendS final



(thinking twice make things harder (?))
(remember to pronounce the S here)

Finally, float for goto
if implementS import
(if you need a strong programming implement, rebel and try "goto" (this is ironic,of course. Pronounce the S here, don't forget))
instanceof int: interface
(talks for itself)
Long native? New package!
(Change old traditions for new technologies)

(now it comes the superhero saga part)
"Private Protected Public" return!!
(in part I, Private Java protected the public classes city. Now, the saga continues)
Short, static, strictfp
(a description of his braveness fp: firm precission (?) )
super switch synchronized this
(?)
throw, throws transient
(?)
try "void, volatile" while assert
(He can dissapear)

What do you think? No... please don't tell the truth.

Courtesy: JavaRanch

Sunday, December 14, 2003

http://java.sun.com

Good to see Gosling photo on Header and Navigation changes gives more accessibility to developers...

Seems Gosling has changed the UI :)

Sun is trying to reach developers... they kept the Developers Home Link.

Friday, December 12, 2003

http://today.java.net/pub/a/today/2003/12/11/mvc.html Beyond MVC: A New Look at the Servlet Infrastructure

Wednesday, December 10, 2003

http://www.moelholm.com/

This has Mock Exams, Exam Docs for SCEA, SCBCD.

JDJ SPECIAL - Answered: The J2EE Questions No One Else Dared to Ask


http://www.sys-con.com/story/?storyid=38149&page=2

There are some interesting answers for the questiosn asked.

Tuesday, December 09, 2003

Implement JSP custom tags in five easy steps: http://www-106.ibm.com/developerworks/java/library/j-pj2ee8/


A good article on creating JSP CTLs.

Monday, December 08, 2003

Top 20 Replies by Programmers when their programs don't work..:)

20. "That's weird...."
19. "It's never done that before..."
18. "It worked yesterday."
17. "How it that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it hasn't been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?"
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"

And the Number One Reply by Programmers when their program doesn't work:
1. "It works on my machine."

http://www.javarss.com A one-stop link to all Java News, Articles, Blogs.

Tuesday, December 02, 2003

In enterprise shops, Java and .NET is more like it


Excerpts from this Article
1. For smart clients, .NET rules.

2. Java is the way to go for large-scale, multiplatform integration at the back end.

3. In terms of development tools and ease of use, .NET is No.1.

4. As for security, Java running on Linux or Unix is a better bet than the .NET languages on Windows.

5. Apart from those I belive Time to Market.

A must read one article for all Developers who really fight Java Vs .NET.

Monday, December 01, 2003


Aggregate - Entity Bean Notes:

§ Entity beans represent the distributed persistent business objects.
§ We access Entity beans via remote interfaces.
§ Object granularity is very important what to implement as an Entity bean.
§ Entity-Beans should represent the coarse-grained objects.
§ Coarse-Grained objects will have the dependent objects.
§ Dependent Object: An object with no real world - meaning when this object is not associated with the        Independent/ Coarse-grained Parent Object.
§ Impact of Fine-Grained design
o Inter-Entity Bean relationship
o Impact on Manageability of Code, Classes that are generated
o Network Performance
o Database Schema Dependency
o Impact of Object Granularity
§ The solution to the above impacts are Aggregate Entity Bean
o This contains set inter-related persistent objects.
§ Persistent Object: An object that is stored in some type of data store. Multiple clients share persistent objects. There are two types of persistent objects
o Coarse-grained: This is self-sufficient, and has its own life cycle and manages the reference with other objects. So the Coarse - grained objects maintain the life -cycle of these objects, so these are called dependent objects.
o Dependent: A self-contained object, which may contain other dependent objects.
§ Two types of strategies to implement Aggregate Entity Bean
o Aggregate Entity bean holds the reference to the Coarse-Grained object.
o Aggregate Entity bean it self as a Coarse - Grained object.
o Lazy Loading of Dependent objects in ejbLoad()
o Aggregate value object strategy
§ Consider dependent Object as Enterprise Bean
o If the dependent object appears to be depending on two different parents
o If the dependent object is already exists as an entity bean/ imported from other application.
§ Don't use Entity-entity relationship, Instead of that start using session façade.


http://www.leocrawford.org.uk/work/jcea/part1/index.html#general A good link for SCEA

http://www.c2.com/cgi/wiki?EjbRoadmap
EJB Raod Map contains all EJB related stuff