--- layout: post title: ! 'Sacrilege: a rather lousy rant on Java for the web' tags: - Development - Loadacrap status: publish type: post published: true meta: _edit_last: '1' _sd_is_markdown: '1' ---

Let me start out saying I'm glad I never had to make web apps in Java. Boostrapping the crap out of a Maven + Struts archetype is insane. I honestly don't know what to feel for Java programmers.

It's been an hour and a half since I've started reading the Apache Struts 2 Web Application Development book and I'm going nuts. I've dealt with more XML in this hour and a half than most of the time in my degree.

Story told short:

  1. I've installed Netbeans and an Apache Tomcat 7 server.
  2. I've created a new Maven Web application.
  3. I've copied a struts routing example, along with the respective action POJO.
  4. Tried to reach the URL; no luck.
  5. Looked up for a web.xml example, in order to correctly load Struts.
  6. Project won't deploy. FML.

At an hour and a half, reading and typing, I could have done so much more in Rails or Sinatra. Sorry.

I don't care what people think about me comparing Java to Ruby at such an early stage in trying to learn. But hey, it's 2012, software ought to be easier to accomplish. Why does it have to be so difficult to understand how a simple controller is executed? Why is the Java way so convoluted?

I'll update this post when I can create a Struts action properly, perhaps with an interceptor. If I can make it to apply some TDD along the way, I pat myself in the back. Until then, I stay with the attitude.