Yes, I'd avoid portal for now, and if you can avoid it maybe even later. Portals have both advantages and disadvantages - and whether it makes sense for you would be a long discussion, better tackled a year or so from now (after some solid J2EE experience).
bruno -----Original Message----- From: Phil_M [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 12:37 PM To: user@struts.apache.org Subject: RE: Newbie Lost in the Apache Jungle Bruno: Thanks for your excellent reply -- if I understand right, you're suggesting a java servlets based architecture (tomcat & underlying) for the application to provide the interactive user client, struts for the framework, and hibernate for DBE independence. Since I'll be the only author until at least an alpha release is ready, I can defer CVS for the moment -- as you said, we need to avoid overrunning our brain's buffers. Would you recommend avoiding portal architectures for the first version? Many of the potential customers are government agencies, and they're big into the portal models -- helps them avoid having to coordinate the work of many different contractors. Thanks Again, --Phil Bruno Melloni-2 wrote: > > You'll have to pick different tools for different needs, then put them > together. Here are some ideas based on open source: > > - JDK 1.5 > - An IDE. Netbeans and Eclipse are good. Eclipse usually requires > picking and installing plug-ins, but nowadays there are distributions > you can get, or you can use MyEclipse (which does much of the stuff > for you). If you want something easier and don't mind spending money, > check out Exadel studio. > - A J2EE server. Start with Tomcat, then later you can graduate to > jBoss. > - Struts 2.0.x (not yet General Availability, but it will likely be by > the time you are done - and you wouldn't want to refactor) > - Hibernate for database access. And any database you like - > hibernate supports most of them. MySQL if you want open source. > - If you are not yet using version control, use CVS to keep your > source code. All IDEs support it or have plug-ins for it. > > - Don't bother with using EJBs at this time. Encapsulate your code > into well thought-out packages instead. > - Spring is nice, but wait until you have more practice with Java... > The brain can accept only so much new stuff at one time. > - Similarly, don't bother with much Javascript yet. Do that in your > second version. > > That should be a good start. It is probably overwhelming, but it is > all pretty much needed. > > Bruno -- View this message in context: http://www.nabble.com/Newbie-Lost-in-the-Apache-Jungle-tf2953416.html#a8 263493 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
