TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

My Java Experience

11 点作者 rayvega超过 15 年前

4 条评论

patio11超过 15 年前
<i>They came out of sheer self defense out of the amount of toil &#38; trouble that you have to go through using what the bare bones Java EE gave you.</i><p>This describes an awful lot of enterprise Java. My most recent discovery was RestEasy, which a) took a week to get working and b) was at least ten times less painful than our previous web services implementation, to the point where I am tempted to delete the wiki, nuke the repository, and cover up any evidence of ever using SOAP or XML-RPC for fear that an incautious code archeologist in the future might open the jar and release the horror upon the world again.
brown9-2超过 15 年前
I think this article would be better titled "My J2EE Experience".<p>I've been working with Java professionally for 5.5 years in enterprise environments and I've never used EJB, nor do I know anyone who has.<p>The sad thing about marketing-type speak that ends up calling J2EE "a platform" is that it becomes very easy to misinterpret the nastiness of these APIs - that's what EE really is, just a set of APIs - as somehow reflecting on the state of the entire ecosystem/community.
ShabbyDoo超过 15 年前
I've been doing mostly Java for over a decade. For me, the session bean is the most useful part of the somewhat artificial amalgam that is JEE/J2EE/whatever. Need declarative XA transaction management? "Required" is your friend. Want to remote to a service but also use it locally? Yup. Need to control the number of concurrent invocations of a service? Just configure your thread pools.<p>Don't need any of that stuff? Then, you probably don't need J2EE. I've never used a stateful session bean on a project and haven't heard too many good use cases to justify them. Pre-3.0 EJBs were a disaster, and everybody just used Hibernate. And EJB3 is basically Hibernate anyway.<p>For lighter-weight Java, the Spring Framework along with annotations takes away a lot of the misery the author discusses.
va_coder超过 15 年前
Use Groovy/Grails if you must develop a Web app on the JVM or reuse existing Java code.<p>J2EE was a disaster (I have 6+ years experience with it). So much wasted talent and time.