Too (many?) Java technologies. Where to start?

[tokidoki]

Hi guys,

I've recently ventured into java programming (napul-an nako sa 7yrs nako sige dukdok sa php).

After going through the basics of Java and considering that I'm into web development I eventually ventured into J2EE. Even in this aspect of java the technologies involved are daunting.

In the barely 3yrs in using basic java and j2ee I came across these stuff:
Struts 1.3.x
Struts 2.x
JAVA EE 5
JSF
Hibernate
Spring
JMS
JMX
iBatis
Tapestry
...and those are just the few.

I already know "basically" what they are. My questions are more focused on necessity.

When should I use them?
Why should I use them?
What are the drawbacks if using them? I've come across some results in Google but are somewhat outdated and leaves others technologies aside.
What companies/employers use these technologies?

[spikes]

as of now I am working with JSF. JSF is really easy to learn. I don't have to worry much about javascripts for validations and etc. But there are also lots components you can choose for JSF you have myfaces, trinidad, and others..

you may check this link for more info

http://www.ibm.com/developerworks/java/library/j-jsf4/

[tokidoki]

Ah, my first production project was done on JSF. My first exposure to java web programming. It wasn't much but at least it gave me a taste. However, the drawback in JSF is that there's no functionality that handles GET methods. POST tanan. So meaning there's no JSF function that let's you handle database queries that can be bookmarked. So old school ka by then. I think this technology is more focused on user interface security rather than data retrieval. That's why it was ideal for my project considering it was an "INPUT ONLY" webpage that records entries.

[spikes]

Ah, my first production project was done on JSF. My first exposure to java web programming. It wasn't much but at least it gave me a taste. However, the drawback in JSF is that there's no functionality that handles GET methods. POST tanan. So meaning there's no JSF function that let's you handle database queries that can be bookmarked. So old school ka by then. I think this technology is more focused on user interface security rather than data retrieval. That's why it was ideal for my project considering it was an "INPUT ONLY" webpage that records entries.

JSF is for the presentation layer. you can use EJB's to handle your backend calls. Try to explore more in JSF. There are lot's of wonderful things that you can do with it. It depends on what kind of flavor you like. Try using Oracle ADF it is still based on JSF.. you will be amazed w/ it.. You can do lot's of things.. Actually before I was not into webdevelopment. Till the time I see JSF.. It really makes my life easier...

As of now I am using JSF w/ EJB's. Our EJB's uses webservices.. It's more complicated than directly calling to the database..

[spikes]

Ah, my first production project was done on JSF. My first exposure to java web programming. It wasn't much but at least it gave me a taste. However, the drawback in JSF is that there's no functionality that handles GET methods. POST tanan. So meaning there's no JSF function that let's you handle database queries that can be bookmarked. So old school ka by then. I think this technology is more focused on user interface security rather than data retrieval. That's why it was ideal for my project considering it was an "INPUT ONLY" webpage that records entries.

I think JSF is not an old school. Actually it's very young..

JSF 1.0 (2004-03-11) - the initial release of the JSF specification.
JSF 1.1 (2004-05-27) - bug fix release. There were no spec or HTML renderkit changes.
JSF 1.2 (2006-05-11) - latest release.

http://en.wikipedia.org/wiki/JavaServer_Faces

[spikes]

However, the drawback in JSF is that there's no functionality that handles GET methods.

I don't think so nga wla mo handle sa GET method.. It is the basics of web programming..

[tokidoki]

I don't think so nga wla mo handle sa GET method.. It is the basics of web programming..

wala bai. that's listed as the "cons" in using JSF. read it up sa mga independent java sites that evaluate frameworks.

but let's get back on topic. No one has answered my question in an unbiased manner. Those stuff I mentioned are there for a purpose. I want to know when each is ideal. That's basically the same lines as "no one design pattern to rule them all".

[tokidoki]

up

[maddox]

Hi guys,

I've recently ventured into java programming (napul-an nako sa 7yrs nako sige dukdok sa php).

After going through the basics of Java and considering that I'm into web development I eventually ventured into J2EE. Even in this aspect of java the technologies involved are daunting.

Java EE 5 is the overhauled version of J2EE resolving the latter's problems. Try to learn Java EE 5 instead and forget about J2EE.

In the barely 3yrs in using basic java and j2ee I came across these stuff:
Struts 1.3.x
Struts 2.x
JAVA EE 5
JSF
Hibernate
Spring
JMS
JMX
iBatis
Tapestry

Struts, JSF, and Tapestry are frameworks for development. More on the UI side.
Hibernate and iBatis are both Persistence engines/providers used by your 'Entities' to maintain persistence w/you db.
Spring is a framework for enterprise application developments in Java.
JMS is an API in Java Enterprise Edition.
JMX is a technology (specs - design patterns, APIs, architecture) for developing enterprise apps.

...and those are just the few.

Indeed. But you don't have to know all of them immediately.

I already know "basically" what they are. My questions are more focused on necessity.

When should I use them?

Depends on where you're assigned. If you're dealing with enterprise applications you'll either be assigned to UI or server-side development. Struts, JSF, Tapestry, etc... are basically for UI development. EJBs, JPA (Java Persistence API), persistence engines (Hibernate, TopLink, etc...) are on the server-side development.

Why should I use them?

First you have to choose w/c one to use. (eg. Hibernate vs. Toplink; Struts vs. JSF) Feedbacks from other people could be very helpful.

What are the drawbacks if using them? I've come across some results in Google but are somewhat outdated and leaves others technologies aside.

If you're referring to third party tools, each of them has some unique features from each other. Most are open-source, and some are not. Some are older than others eg. Struts has been around for awhile, while JSF is still new. JSF has some features better than the older Struts.

If you're referring to Java's platform versions eg. J2EE vs. Java EE 5, same factors mentioned above exist. Personally, I recommend Java EE 5. A lot of J2EE's weaknesses have been resolved in Java EE 5. An easier life for programmers.

What companies/employers use these technologies?

Mostly companies who develop enterprise applications for the vertical market. eg. HRIS, Payroll, Bank system apps, Gov't apps, transactional apps, etc... large apps in general. Applications that fit a specific industry or company in terms of needs.

Small projects can also be developed using these tools. Design lang maayo kay basig overkill na.

[tokidoki]

Thanks so much bai. you answered my questions and concerns very clearly.

In the stuff about EE 5, though, murag lisud man siguro irelate (especially if beginner ka reading THEIR docs) if wala ka initial background sa J2EE. J2EE documentation, for me, gives a very clear discussion on the basics of serlvets and jsp.

What does java ee 5 cover man diay bai? for the benefit of other readers lang. Just write a short bulleted list of differences. thanks kaayo.