Slashdot Mirror
Geronimo! Part 1: The J2EE 1.4 Engine That Could
An anonymous reader writes "Java-based open source development has come a long way since the early days of developers sharing GUI libraries. Geronimo is a large-scale project attempting to create a certified J2EE 1.4 server based on existing open source components. Take a tour through the Geronimo maze with Sing Li as your guide. Gluecode Software CTO and principal Geronimo contributor Jeremy Boynes shares his perspective on Geronimo and go here to learn how to use the new Eclipse plug-in for Apache Geronimo."
What are you talking about? Using JSP is pretty close to PHP. If you're talking about using servlets .. well, best tool for the job. You don't use Servlets if your resulting page has a lot of pure HTML. Also, J2EE is a server suite with support for EJB's. If you haven't tried these, then you haven't really tried J2EE either.
What do you mean by the code "does not look intuitive"? It's Java, nothing more, nothing less.
Java 1.5 has been renamed to Java 5, and despite the name change, Java 5 is still part of Java 2. The change was marketing based.
None of these free JVMs would be anywhere without the fine work of the Classpath contributers. Any sufficiently motivated individual can make a JVM in a year. It may not run quickly - but it will run. Writing the Java libraries on the other hand is a monumentous undertaking requiring dozens of people and many years of work. This is where Classpath comes in.
Let's hear it for Classpath!
Hip hip hooray!
If you are copying-and-pasting code, then an object-oriented language is not the tool for you.
Come to think of it, if you copy-and-paste code, the only tool for you is a CS course.
You don't use Servlets if your resulting page has a lot of pure HTML.
Well now, that really depends on your architecture. For example, where I work our inhouse framework uses a single Dispatcher servlet to dispatch actions to the relevant Handler classes. Those classes do more or less processing, but the end result is *always* displayed by a JSP - we *never* use a Java class to output an entire page.
You can do the same with Servlets - just put anything the JSP needs into the request, then get a reference to the RequestDispatcher from the request and call its forward method, passing in the URI of the JSP.
It's official. Most of you are morons.
- a large user and developer base, which means better support. Your framework is only used by your company, so only you can support it.
- Struts is a popular framework, so you can hire developers who already know it instead of having to train them on the use of your own propietary one. This one is even a selling point to the PHB's, since they know that no training time means the newbies can start being productive sooner.
- It's open source, so if you ever leave your current job and go work somewhere else, you can take that knowledge with you, and use it anywhere else. The knowledge you have about this propietary framework will be useless since it's the company's property (yes, even if you wrote it, since it was on the company's time, unless you had a written agreement saying otherwise)
I'm not even a Struts advocate, I prefer Tapestry myself. But I once worked at a company where we (mostly I) developed a framework for web applications and guess what... I can't use it now that I don't work there. Oh and I had to keep training people on the use of the framework. And I was the only one giving support to the other developers. And these guys licensed said framework to every customer they had where it was used for their projects, and I got nothing for it besides my paycheck.If I had worked on improving Tapestry or Struts or something like that, instead of concocting a propietary framework, I would still have access to that work today, it wouldn't have gone to waste. That's yet another reason why Open Source is good and one of the reasons I like most (being a developer, I take advantage of a lot of open source frameworks that mainly benefit the developer and contribute back whenever I can, either by promoting said frameworks or sending patches, etc).
Oh and that propietary framework I wrote? I don't think anyone even uses it anymore. Few people really understood how it worked and most of them have also left that company, so now they're left with a useless product, they can't support or upgrade the projects written with that framework. I know that they have even contracted ex-employees for maintenance on projects they worked on while being there... so in the end it wasn't even a good thing for the company either. The use of an open framework would have meant they could hire anyone who knows it for upgrades, maintenance, bug fixes, etc.
Go hug some trees.