Developing and running a Java EE Hello World application • Hacker News Board

Re: Developing and running a Java EE Hello World application

#81

Post by zero-g » Fri, Nov 28, 2014, 8:14 AM UTC

lennartcl wrote: post #61

Ahh Enterprise. Protip for anyone applying for an enterprise job: just copy-paste https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... when they do the mandatory fizzbuzz test in the job interview. And then complain in the github issue tracker if you didn't get the job.

There definitely should be some IoC container.

Re: Developing and running a Java EE Hello World application

#82

Post by [deleted] » Fri, Nov 28, 2014, 8:14 AM UTC

lennartcl wrote: post #61

Ahh Enterprise. Protip for anyone applying for an enterprise job: just copy-paste https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... when they do the mandatory fizzbuzz test in the job interview. And then complain in the github issue tracker if you didn't get the job.

[deleted]

Re: Developing and running a Java EE Hello World application

#83

Post by fddlr » Fri, Nov 28, 2014, 8:44 AM UTC

pacoverdi wrote: post #70

realusername wrote: post #34

I've also done some JEE quite a long time ago and I hated every second of it. I'm not sure however if my experience is representative of the the Java community. There is no problem with the language itself nor the VM which is also working quite fine (while taking a lot of RAM). But I really have a problem with the community, everything seems over-engineered and super complicated in Java, even with simple things. Noth…

I also tried some JEE in ~2000 and hated it. How could one accept to code in such a bloated ecosystem? I'll admit I filtered out a lot of candidates becaused they mentioned stuff like "J2EE Engineer" on their resume, which seemed to imply strong incompatibilities with our coding style... Fortunately not everyone in the Java community is modeled after JEE (or Maven, Spring, etc.).

Right now I work for a large European bank with Java EE and Wicket. I only touch an xml every 2 months or so. I'm not saying it's better than RoR for example in this regard, but Java EE has come a long way since people here used it, and even if it's still not your cup of tea, you should check out Play framework. I've had personal projects in .NET and I can say that there is a lot more boilerplate and spaghetti code there.

Re: Developing and running a Java EE Hello World application

#84

Post by coldtea » Sat, Nov 29, 2014, 2:58 PM UTC

smtddr wrote: post #41

coldtea wrote: post #17

Earlier quoted context omitted.

You could just have the servlet write "Hello World" directly. The Bean is not really useful in the example -- it's mean as a stand in, to know how to write one for your business logic needs, e.g user or product bean etc. (Btw, beans are just lightweight classes used mostly as structs, with getters and setters).

>>You could just have the servlet write "Hello World" directly. It's been years since I've had to write a Java webapp, but from what I remember using the servlet code to directly write the webpage output was considered bad. That was the job of the jsp file. e.g., "views" in bottlepy and Rails: http://guides.rubyonrails.org/layouts_and_rendering.html

Yes, it was considered bad style because of separation of concerns etc, but nothing necessitated JSP, you could just use servlets and any of tons of template libraries.

And for a hello world, a servlet would do just fine.