3 then 2. I started learning struts then realized I needed more experience with Servlets and JSP. Stopped Struts, got versed in Servlets/JSP then came back to Struts. For the record however, I am not currently using Struts on any projects.
3...I learned Struts, JSP and Servlets all at the same time. I reckon you end up blurring the concepts of each pretty heavily in learning this way - I'm going to go over Servlets and JSP separately as soon as I find a spare few hours
Learning all 3 at the same time is like learning the 'practice' without the 'theory' in any area...I can make stuff work, but I don't really know how it all ties together. Not a nice feeling, I reckon.
2 or 3.. As i have gone through lots of examples and worked with struts and my compnent developed was utilized by the team actually implimenting there solutions using struts so i have little expossure.
Also i have gone through examples and read a lot but still need to review and do more examples. I have not given certification.
But I like struts and would like to share my views and code with you guys
Dream!!! Set Vision !! Transform Vision to Mission by Actions on Deadlines!.
3. I jumped right into J2EE with Struts. However, prior to that, I was already familiar with J2SE and I had a few years experience writing small-to-medium webapps using PHP3 and PHP4. I was up to speed with the web container very quickly.
Also, in writing PHP I previously had invented the front-controller design pattern on my own, so Struts wasn't all that alien to me. I knew which problems it's designed to solve, having previously solved them on my own in much the same way. Most of the problems I ran into while learning Struts and J2EE had to do with the Tiles framework and attribute scoping therein. [ July 24, 2005: Message edited by: Barend Garvelink ]