For Programmers: Free Programming Magazines  


Home > Archive > Java Help > May 2006 > About J2EE









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author About J2EE
dolpheen@gmail.com

2006-05-22, 7:12 pm

I want to do career in J2EE.

Recently I have downloaded the J2EE 1.4 Tutorial
for Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2.
I am also having Sun Java Studio Enterprise.

The tutorial explains the following technologies:

XML,JAXP,SAX, DOM, XSL, XSLT, XPath, JAX-RPC, SAAJ, JAXR,
Servlets,JSP,JSTL, JSF, EJB, EJBQL, JMS, HTTP

Do I need to excel in most of these technologies to be a good J2EE
developer?

Is it necessary to have a good command over XML to learn J2EE as it is
explained earlier in the tutorial?

Various J2EE Application Servers are available like Sun Java System
Application Server.
Some of them are IBM WebSphere, BEA WebLogic, JBoss, OC4J.
Which one should I choose?
Do I need to learn technologies specific to them like Oracle ADF?

Which GUI editor should I choose from:
Eclipse, IntelliJ IDEA,BEA Workshop,Sun Creator, Sun Java Studio
Enterprise, Oracle's Java Editor?

Please suggest a suitable newsgroup to post messages about J2EE.

I am a lot . Please help me.

SMC

2006-05-22, 7:12 pm

On Mon, 22 May 2006 11:42:09 -0700, dolpheen wrote:

> I want to do career in J2EE.
>
> Recently I have downloaded the J2EE 1.4 Tutorial
> for Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2.
> I am also having Sun Java Studio Enterprise.
>
> The tutorial explains the following technologies:
>
> XML,JAXP,SAX, DOM, XSL, XSLT, XPath, JAX-RPC, SAAJ, JAXR,
> Servlets,JSP,JSTL, JSF, EJB, EJBQL, JMS, HTTP
>
> Do I need to excel in most of these technologies to be a good J2EE
> developer?


Not really. Some are far more commonly and widely used than others.
Doesn't hurt to have an understanding of all of them, but the more common
ones you're likely to use are XML, SAX, DOM, Servlets/JSP, JSTL, EJB and
HTTP, so concentrate more effort on those. No one is expected to have a
dictionary like knowledge of all standards and technologies. In my
experience it's far better to have people who are good problem solvers who
can learn and apply appropriate technologies when needed rather than to
have someone who's memorised the fine details of every standard but can't
apply it in a sound practical way.

> Is it necessary to have a good command over XML to learn J2EE as it is
> explained earlier in the tutorial?


Doesn't hurt. XML is very widely used. XML isn't that hard, so learn the
basics and try to get some practical experience with it (i.e. write a few
programs or use and understand some example programs).

> Various J2EE Application Servers are available like Sun Java System
> Application Server.
> Some of them are IBM WebSphere, BEA WebLogic, JBoss, OC4J.
> Which one should I choose?


Any. As you move around jobs you'll find you'll get exposure to one or
more. You can choose to specialise in one, but wouldn't it be better to
have skills that are transferable? (ly some employers don't think so).
Most applications servers have a lot in common so knowing one helps the
learning curve for the others.

> Do I need to learn technologies specific to them like Oracle ADF?


Not unless the job you want specifically requires it.

> Which GUI editor should I choose from:
> Eclipse, IntelliJ IDEA,BEA Workshop,Sun Creator, Sun Java Studio
> Enterprise, Oracle's Java Editor?


Try them and pick your favourite. The best one is the one that is most
useful to you and makes you more efficient. Some workplaces will only use
one particular one- that's fine, I repeat my advice about transferable
skills.

> Please suggest a suitable newsgroup to post messages about J2EE.


Here is fine. People will politely tell you if your message is not
appropriate. Won't we everyone :-)

> I am a lot . Please help me.


One step at a time. Make sure you're comfortable with the Java language
before you dive into some of the more complicated applications of it (like
EJB for example).

--
Sean
Aki Laukkanen

2006-05-23, 4:13 am

SMC wrote:
> On Mon, 22 May 2006 11:42:09 -0700, dolpheen wrote:
>
>
> Try them and pick your favourite. The best one is the one that is most
> useful to you and makes you more efficient. Some workplaces will only use
> one particular one- that's fine, I repeat my advice about transferable
> skills.


I completely agree. After all, it doesn't take all that long to get used
to another IDE after learning ot use one.
Of course, you /could/ take a look at some of the current career ads and
see which IDEs and Application Servers are most commonly mentioned in
the "required skills" section. That's what I do. ;-)
(Though it really won't hurt to experiment with several different options.)

--
-Aki Laukkanen
TechBookReport

2006-05-23, 4:13 am

SMC wrote:
> On Mon, 22 May 2006 11:42:09 -0700, dolpheen wrote:
>
>
>
> Try them and pick your favourite. The best one is the one that is most
> useful to you and makes you more efficient. Some workplaces will only use
> one particular one- that's fine, I repeat my advice about transferable
> skills.
>


Note that the OP asked about GUI editor rather than IDE. Like you I
assume he/she was asking for an IDE, but just in case...

J2EE apps don't usually include GUI design. It's more back-end stuff.
The exception being JSP, which is sometimes included as part of the J2EE
stack. It's a way of dynamically populating web pages, something like
Microsoft's ASP, and is often used as the front-end on a J2EE
application. Not all Java IDEs support JSP out of the box, so you may
need to check-out what's required before you dive in to any of the IDEs
mentioned.

Finally, aside from making sure you know Java itself before diving in to
J2EE, I'd also recommend making sure you understand why J2EE is
necessary - what problems is it trying to solve over and above the core
Java language? Why do you need all of these complex frameworks and
scaffolding? Without a clear understanding of this the whole thing's
going to be impenetrable.

HTH

--
TechBookReport Java http://www.techbookreport.com/JavaIndex.html
Sameer

2006-05-23, 8:07 am

Thanks for your postings !

Please tell me your opinions about Core Java i.e. J2SE.

Now there is a boom of J2EE so I decided to learn it.
But is it worth to concentrate on Core Java only?

Core Java is also a big field with lot of API's like Sound, 3D
Graphics, Networking.
And with release of Java 5 it is also much interesting with features
like Generics etc.

J2SE do not need any application server. Just download the
corresponding API documentation and your are ready to use the classes
therein.

How much scope is there in the industry for Core Java? Please compare
the jobs avaialble for J2SE and J2EE.

Is it necessary to move to J2EE?

TechBookReport

2006-05-23, 8:07 am

Sameer wrote:
> Thanks for your postings !
>
> Please tell me your opinions about Core Java i.e. J2SE.
>
> Now there is a boom of J2EE so I decided to learn it.
> But is it worth to concentrate on Core Java only?
>
> Core Java is also a big field with lot of API's like Sound, 3D
> Graphics, Networking.
> And with release of Java 5 it is also much interesting with features
> like Generics etc.
>
> J2SE do not need any application server. Just download the
> corresponding API documentation and your are ready to use the classes
> therein.
>
> How much scope is there in the industry for Core Java? Please compare
> the jobs avaialble for J2SE and J2EE.
>
> Is it necessary to move to J2EE?
>

I would have said there's plenty of scope in J2ME as well. But all of
this depends on where you are. Your local jobs market may be very
different to what it is in the UK or US.

--
TechBookReport Java http://www.techbookreport.com/JavaIndex.html
SMC

2006-05-23, 7:08 pm

On Tue, 23 May 2006 03:28:54 -0700, Sameer wrote:

> Thanks for your postings !
>
> Please tell me your opinions about Core Java i.e. J2SE.
>
> Now there is a boom of J2EE so I decided to learn it.
> But is it worth to concentrate on Core Java only?


Would be easiest to familiarise yourself with Core Java first.

> Core Java is also a big field with lot of API's like Sound, 3D
> Graphics, Networking.
> And with release of Java 5 it is also much interesting with features
> like Generics etc.
>
> J2SE do not need any application server. Just download the
> corresponding API documentation and your are ready to use the classes
> therein.
>
> How much scope is there in the industry for Core Java? Please compare
> the jobs avaialble for J2SE and J2EE.
>
> Is it necessary to move to J2EE?


I've often found in our local job market (Australia) that the recruiters
often ask for J2EE when in fact most of the jobs involved just one
tiny aspect of J2EE, typically just JSP. Others just throw it up
because it's the buzzword they know and they can't distinguish
between J2SE and J2EE. "Core Java" is everywhere, and often what you'll
use most.

I think the post by TechBookReport stated it well- know the problems
you're trying to solve and why J2EE is the right solution for those
problems.

--
Sean

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com