ou know John what my big problem is? the big problem is that for example after what u said i go for the appfuse (for the backbone) and Struts or Spring for learning, the first tutorial i face i find out there many concepts i have no idea about, then i feel badly frustrated. for example right now i have opened this page: http://struts.apache.org/2.x/docs/tutorials.html there are plenty of terms i have just heard of them but not worked with them, if i want to go and learn them it will take a long time, may be im not right but the terms like maven, xml properties, ...beans, CRUD and...are bothering me, thats why i give it up and ... do u have any idea over this problem ? you may say go and learn one by one, i would say sure i will, BUT..from where i need to start? which one of those topics i need to go first for ? hibernate ? beans? controllers ? mvc ?..i have ead so many things about these terms but still have not felt them by my own, i have not done any real world project with them. would you put them all in steps for me and the tell me the priorities ?
John Kwon wrote: > > It's good to continue to use any and all of them as long as the need > arises. > > You're going to be doing more than one project in your life - probably > more > than one in the next couple of years. Some start a project nearly every > month. So AppFuse is handy to use. > > Struts and Spring are both good to know - and it's easier to set up one of > those using AppFuse than trying to do it manually. > > And, like all things software development related, things are changing > fast. Pick a direction and keep learning as rapidly as possible, because > everything changes. > > Look at the history of the original Struts, and what it's become now - or > AppFuse - it's older versions differ substantially from the current > version. > > Core concepts don't change - how we wrap them, architect them, and > implement > them changes every day. > > One might argue that J2EE (as diagrammed by Sun on their original J2EE > documentation) was nothing more than a grand implementation of CICS. > Transactional page interaction with persistence transactions back on the > server. We might see web services as the modern implementation of CICS > transactions. While the implementation has radically changed, the core > concept of interfacing with transactions has not changed in decades. > > Learn all you can, don't be afraid to learn something new or extra, and > keep > the core concepts close to you. > > On 9/29/07, meisam4910 <[EMAIL PROTECTED]> wrote: >> >> >> is it good to continue using appfuse or isn`t better to learn about >> Struts >> or >> Spring ? I mean to learn them fully and build our projects based on them >> ? >> or can we count on appfuse forever and use appfuse always ? >> -- >> View this message in context: >> http://www.nabble.com/AppFuse-or-Spring-MVC-or-Struts---tf4539082s2369.html#a12954659 >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/AppFuse-or-Spring-MVC-or-Struts---tf4539082s2369.html#a12954971 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
