21–30 of 84 posts
Full JEE stack is terrible if you would like to write sad CRUD applications. But if you need something more than simple access to DB it is very good solution.
Setting up any web stack is a pain in the ass and probably just as long of a tutorial. For example, write out a tutorial which goes from base Ubuntu install to "hello world" on Rails, I bet it's just as long or longer. I suppose it depends on how much detail you want to include. There are just more "one click" install options for other stacks.
I beg to differ.
http://bottlepy.org/docs/dev/tutorial.html#quickstart-hello-...
http://howtonode.org/hello-node
(In fairness, I do note that the above examples don't actually have a element to click on before showing helloworld like the Java example)
Setting up any web stack is a pain in the ass and probably just as long of a tutorial. For example, write out a tutorial which goes from base Ubuntu install to "hello world" on Rails, I bet it's just as long or longer. I suppose it depends on how much detail you want to include. There are just more "one click" install options for other stacks.
Is 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.
Except that that's not just a "Hello Word" page. That's routing to the right page, transaction and session control, storing the text of the message in a separate class than the one that returns the response, and using a template to return the resulting HTML. Looking at the section with the actual example code in it, you could do it in about half that, if you wanted a simple version that just returned "Hello World". I…
Or rather, better put, Java EE devs always want "routing, templating, separation of concerns", because they consider it better, no matter the current problem at hand.
Is 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
If you need distributed transactions (and sure, most people who think they do don't), you use the fancy JSRs or you will go out of business. That stuff is hard and it's the reason JEE is so horrible, but it solves problems you can't solve any other way.