_posts/2012-02-10-sacrilege-a-rather-lousy-rant-on-java-for-the-web.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

---
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'
---
<p>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.</p>

<p>It's been an hour and a half since I've started reading the <a href="http://www.amazon.com/Apache-Struts-Web-Application-Development/dp/1847193390/ref=sr_1_1?ie=UTF8&amp;qid=1328904973&amp;sr=8-1">Apache Struts 2 Web Application Development</a> book and I'm going nuts. <em>I've dealt with more XML in this hour and a half than most of the time in my degree.</em></p>

<p>Story told short:</p>

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

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

<p>I don't care what people think about me comparing Java to Ruby at such an early stage in <em>trying to learn</em>. 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?</p>

<p>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.</p>