w*r
2 楼
start from sun's j2ee tutorial online and then read ibm redbook for websphere
【在 p***p 的大作中提到】
: 一直在搞Core Java，请问入门J2EE有什么捷径？
: 是不是来个
: JSF＋AJAX＋Hiberate＋EJB
【在 p***p 的大作中提到】
: 一直在搞Core Java，请问入门J2EE有什么捷径？
: 是不是来个
: JSF＋AJAX＋Hiberate＋EJB
o*g
3 楼
其实我觉得，光看书，没有机会做事情是没用地
websphere
【在 w*r 的大作中提到】
: start from sun's j2ee tutorial online and then read ibm redbook for websphere
websphere
【在 w*r 的大作中提到】
: start from sun's j2ee tutorial online and then read ibm redbook for websphere
c*t
4 楼
Create your own project ah...
【在 o***g 的大作中提到】
: 其实我觉得，光看书，没有机会做事情是没用地
:
: websphere
【在 o***g 的大作中提到】
: 其实我觉得，光看书，没有机会做事情是没用地
:
: websphere
c*m
5 楼
First you need to know the common and basic technologies and concepts about
JEE -- servlet, jsp, transaction control, JNDI, JMS, RMI, EJB, App server,
JDBC.
You don't need to know a lot about each, just reading through the tutorials on
Sun's website (the short individual tutorials, not the giagantic, 1500 pages
J2EE Tutorial) will get you started. You can put off those parts that you don'
t understand for later study. As long as you get the big picture, it is ready
to start.
Once you have a gras
JEE -- servlet, jsp, transaction control, JNDI, JMS, RMI, EJB, App server,
JDBC.
You don't need to know a lot about each, just reading through the tutorials on
Sun's website (the short individual tutorials, not the giagantic, 1500 pages
J2EE Tutorial) will get you started. You can put off those parts that you don'
t understand for later study. As long as you get the big picture, it is ready
to start.
Once you have a gras
f*e
6 楼
I also feel j2ee becomes a pain in the ass when these many debatings
are involved. You got CMP, people felt it's too heavy weight and verbose
and then someone comes up with Hibernate, JDO.
And now EJB3.0 is debating with JDO2.0. It looks like EJB3.0 will be like
Hibernate. And then you get debate between EJB3 and Spring.
Sometimes I feel the nice thing about J2SE is its monoply. Suns told you
to get rid of AWT and go for swing, plain and simple. Although IBM will
come up with SWT, for most of ja
are involved. You got CMP, people felt it's too heavy weight and verbose
and then someone comes up with Hibernate, JDO.
And now EJB3.0 is debating with JDO2.0. It looks like EJB3.0 will be like
Hibernate. And then you get debate between EJB3 and Spring.
Sometimes I feel the nice thing about J2SE is its monoply. Suns told you
to get rid of AWT and go for swing, plain and simple. Although IBM will
come up with SWT, for most of ja
g*y
7 楼
You are thinking in microsft way. In reality, there is no solution that can
solve all problems and fit everywhere. This is the origin of so many java open
source projects, and the discussion and comparation between projects/products
are actually the best way to make improvement. If you follow the trail of
several most famous projects/products, you will understand how this model
works. For example, a lot of EJB3.0 ideas actaully come from Hibernate(Gavin
King is actaully one of the member of the
【在 f******e 的大作中提到】
: I also feel j2ee becomes a pain in the ass when these many debatings
: are involved. You got CMP, people felt it's too heavy weight and verbose
: and then someone comes up with Hibernate, JDO.
: And now EJB3.0 is debating with JDO2.0. It looks like EJB3.0 will be like
: Hibernate. And then you get debate between EJB3 and Spring.
: Sometimes I feel the nice thing about J2SE is its monoply. Suns told you
: to get rid of AWT and go for swing, plain and simple. Although IBM will
: come up with SWT, for most of ja
solve all problems and fit everywhere. This is the origin of so many java open
source projects, and the discussion and comparation between projects/products
are actually the best way to make improvement. If you follow the trail of
several most famous projects/products, you will understand how this model
works. For example, a lot of EJB3.0 ideas actaully come from Hibernate(Gavin
King is actaully one of the member of the
【在 f******e 的大作中提到】
: I also feel j2ee becomes a pain in the ass when these many debatings
: are involved. You got CMP, people felt it's too heavy weight and verbose
: and then someone comes up with Hibernate, JDO.
: And now EJB3.0 is debating with JDO2.0. It looks like EJB3.0 will be like
: Hibernate. And then you get debate between EJB3 and Spring.
: Sometimes I feel the nice thing about J2SE is its monoply. Suns told you
: to get rid of AWT and go for swing, plain and simple. Although IBM will
: come up with SWT, for most of ja
f*e
8 楼
I also feel j2ee becomes a pain in the ass when these many debatings
are involved. You got CMP, people felt it's too heavy weight and verbose
and then someone comes up with Hibernate, JDO.
And now EJB3.0 is debating with JDO2.0. It looks like EJB3.0 will be like
Hibernate. And then you get debate between EJB3 and Spring.
Sometimes I feel the nice thing about J2SE is its monoply. Suns told you
to get rid of AWT and go for swing, plain and simple. Although IBM will
come up with SWT, for most of ja
are involved. You got CMP, people felt it's too heavy weight and verbose
and then someone comes up with Hibernate, JDO.
And now EJB3.0 is debating with JDO2.0. It looks like EJB3.0 will be like
Hibernate. And then you get debate between EJB3 and Spring.
Sometimes I feel the nice thing about J2SE is its monoply. Suns told you
to get rid of AWT and go for swing, plain and simple. Although IBM will
come up with SWT, for most of ja
c*m
9 楼
First you need to know the common and basic technologies and concepts about
JEE -- servlet, jsp, transaction control, JNDI, JMS, RMI, EJB, App server,
JDBC.
You don't need to know a lot about each, just reading through the tutorials on
Sun's website (the short individual tutorials, not the giagantic, 1500 pages
J2EE Tutorial) will get you started. You can put off those parts that you don'
t understand for later study. As long as you get the big picture, it is ready
to start.
Once you have a gras
JEE -- servlet, jsp, transaction control, JNDI, JMS, RMI, EJB, App server,
JDBC.
You don't need to know a lot about each, just reading through the tutorials on
Sun's website (the short individual tutorials, not the giagantic, 1500 pages
J2EE Tutorial) will get you started. You can put off those parts that you don'
t understand for later study. As long as you get the big picture, it is ready
to start.
Once you have a gras
p*p
10 楼
3ks for all reply
I have developed a servlet container, it is pure Core JAVA with out J2EE fancy
functions, JNDI,DB Pool ... somehow research, not exactly
I have developed a servlet container, it is pure Core JAVA with out J2EE fancy
functions, JNDI,DB Pool ... somehow research, not exactly
相关阅读
Re: a Stupid question.Re: 奇怪？？ import找不到packageRe: 网上哪里有JDBC的入门书呢Re: How can I call another program from Java?请教：使用javascript制作online database的方法Re: 和C++中STL对应的JAVA中的东东是甚来的？Re: FileDialog 的问题Top Ten Errors Java Programmers Make(7)EJB ServerRe: 问一个关于Java Native Interface的问题What are the transaction management benefits of tRe: help! how to make jar work?What are the key benefits of the EJB technology?Re: Want to take Java CertificationTop Ten Errors Java Programmers Make(4)Doesn't EJB technology compete with CORBA?Top Ten Errors Java Programmers Make(9)Re: help: how does the class Model$5.class come?Re: Need help with EJBTop Ten Errors Java Programmers Make(1)