Developing and running a Java EE Hello World application
wiki.jetbrains.net
Developing and running a Java EE Hello World application
1–10 of 84 posts
Re: Developing and running a Java EE Hello World application
#2I don't do web apps with java, so I honestly don't know if it's the proper way to do it, a satire, or if there is a more straightforward way.
Especially, I don't see why one has to write both the class HelloWorldServlet and HelloWorldBean; couldn't one just inherit from one class or implement one interface?
Re: Developing and running a Java EE Hello World application
#3Is the point of this saying that J2EE is bloated and that simple operations are made seemingly impossible?
Of course you wouldn't write an "hello world" in j2ee, what would be the point?
All that stuff makes it easier later to write more complex stuff, so I really don't see the point of this submission.
Re: Developing and running a Java EE Hello World application
#4I think the usual way would be to use JSF and CDI beans instead of using EJBs and Servlets though. The only thing that is quite annoying is creating the web.xml from scratch for the first time. The shown approach is rather bad for simple (and modern) Hello World.
Re: Developing and running a Java EE Hello World application
#5I don't think the point here is to get simple web apps up and running quickly. It is to build large scale systems that are stable. So yes, there will be overhead and lots of boiler plate stuff. Even projects like Django still have this overhead.
Re: Developing and running a Java EE Hello World application
#6Taking a cheap jab at Java EE just because their "Hello World" introduction article is a bit lengthy is bad form. Judging by the insulting "kids" reference in your title, Java EE has a completely different mindset than you are used to and the target audience doesn't include you.
That doesn't mean the millions of other developers and billions of other platforms running Java are inferior.
Re: Developing and running a Java EE Hello World application
#7And yes kids, enterprise applications at large companies are exactly as hard to maintain as you may have guessed (after this article).
Old legacy codebases in Java are one of the worst things I've ever seen. (spiked with old stuff nobody maintains anymore and also nobody pays you to upgrade, such fun times)
Re: Developing and running a Java EE Hello World application
#8Is the point of this saying that J2EE is bloated and that simple operations are made seemingly impossible? Of course you wouldn't write an "hello world" in j2ee, what would be the point? All that stuff makes it easier later to write more complex stuff, so I really don't see the point of this submission.
> All that stuff makes it easier later to write more complex stuff
I sincerely doubt that. I've seen E-Banking systems run on Jetty with JDBC directly. No fancy JSRs were needed.
Btw: J2EE was indeed even more bloated than JavaEE. I don't think that anyone would defend J2EE nowadays, not even the folks behind JavaEE
Re: Developing and running a Java EE Hello World application
#9Taking a cheap jab at Java EE just because their "Hello World" introduction article is a bit lengthy is bad form. Judging by the insulting "kids" reference in your title, Java EE has a completely different mindset than you are used to and the target audience doesn't include you. That doesn't mean the millions of other developers and billions of other platforms running Java are inferior.
At a previous employer, we've migrated a complex J2EE (with EJB 2.0 and such) E-Banking system to use only Jetty and JDBC directly. No one in operations noticed the difference.
But the developers did. Oh they were about 5x as productive afterwards. With no missing features.
Perhaps I'm not included in the target audience. But if E-Banking can do it, what remains of the "target audience" ?
Re: Developing and running a Java EE Hello World application
#10Next time, kids, we'll do the same without support from our fancy IDE! O wait, no. Let's _not_ do that.