I agree with Vikram. If you don't have the basics of http (as it pertains to requesting documents) and how request and response typically work (in either ASP or Java), then your struggle will be long and frustrating.
Also, as someone mentioned in the last thread. You should have a firm grasp of html so if someone asks you: <digressing> why <input type="textarea".... doesn't display in a web browser? or whether cascading style sheets are rendered on the server side or the client side (LOL, that actually happened at my last job as the Company's software was being re-written in Java (Struts) from ASP) I won't mention any names because at least one of those persons monitors this list <smirk> </digressing> then you will be able answer with a resounding ...... "I think so" JM > -----Original Message----- > From: Vikram Goyal01 [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 29, 2002 10:54 PM > To: Struts Users Mailing List > Subject: RE: few questions > > > Looking at the questions I would say that your (or any newcomer's > for that matter) path of learning should have been.. > JAVA -> Web Development (How the web works) -> Servlets/JSPs -> Struts > > It is pointless trying to learn Struts if your basics are not correct. > > Rgs > Vikram > > > > -----Original Message----- > From: reshma deshpande [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 30, 2002 1:23 AM > To: [EMAIL PROTECTED] > Subject: few questions > > > > Hi All, > > Its me again .. remember the "some help... " mail this friday! I > studied 120 pages of JSP (from Web Development using Java Server > Pages, Manning) since i had that book (i would finish it soon), > and also read a couple of tutorials on Struts. Heres what I > understand .. plz correct me if I am wrong, and also plz ans my questions: > > Following are the main components that build the Struts framework: > > - struts-config.xml : where we specify the action mappings (local > or global forwards that are defined by the Action class). [Q# 1: > what exactly do we need to code in this file] > > - ActionForm Beans: these are specific to each form and mainly > have getters and setters, along with validation methods handled > by ActionErrors. [Q# 2: are there any other methods that might be > performed in the form beans] [Q# 3: what exactly is the > ActionErrors object?] > > - ApplicationResources.properties file: defined in the web.xml > file, and is used for displaying error messages etc.. > > - Action classes: the main method here is the perform( ). [Q# 4: > I didnt understand what exactly is done by these classes, since > the example I referred to showed some real complex code.. I got > lost here ..] > > - JSP pages: these would have code using the Struts tag library > to access html elements such as forms etc [Q# 5: would i have to > learn the syntax of this library before starting .. I am not much > conversant with custom taglibs in JSP] > > - Action Servlet: the main controller servlet > > - web.xml [Q# 6: do i have to make any changes in this ?] > > As you might have noticed .. I kind of have the gist of these > pieces, but cant put them up together.... to summarize all my > Questions, I would put it this way.. > > ** 1 ** what are all the components in the Struts framework > (apart from the ones mentioned above .. anything missing ??) > > ** 2 ** in which of these components do we need to make changes > (actual coding) and how complex is it ? I mean, if you are > separating out Java content from the presentation layer, and > restricting it to EJBs and stuff, how much of actual Java code > would be written in a Struts application (especially in the > Action classes) > > ** 3 ** apart from the configuration and deploying issues how > complex is Struts ? > > Could anybody plz ans my questions .. especially Q# 2 and Q# 4. > > Thankyou for your time .. and plz note that I am very new to the > Struts environment .. I mite (rather must) have asked all silly > questions .. :-) > > ~ Reshma > > > > > > > > --------------------------------- > Do You Yahoo!? > Yahoo! Tax Center - online filing with TurboTax > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
