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] > >
