On a side note, you might find it beneficial to do some research on the technology, as doing so would undoubtedly answer more questions than you even know you have at this point. One very good place to get started on your research is the Struts web site (http://jakarta.apache.org/struts). Check out the resources link (under community) - you'll find coverage that comes right out of the horses' mouthes. If you're looking for something bound to reference, you might consider checking out O'Reilly's selection of Servlet/JSP/Struts books (Java Servlet Programming/Java Server Pages are where I got my start - good beginner/intermediate books - good references for even advanced folks). There are getting to be several books about Struts too.
Another technology you might well be interested in is a thing call the Java Standard Tag Library (JSTL). You can find a reference implementation on Jakarta (http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html). Essentially, the JSTL is just what it says: a standard set of tags to cover many different needs. Some (probably more than I'm aware of - haven't checked lately) containers are already shipping an implementation of the JSTL with their servlet containers nowadays -- almost certain Resin does this. If yours doesn't, or you happen to like the Jakarta implementation better (I believe there is, if I recall correctly, some "wiggle room" in the spec for how certain things are to be implemented - I've heard of folks prefering the Jakarta JSTL over others and vice versa), then use that. It's not that huge of a thing (ok, well, it actually could conceivably be depending on where the wiggle room was at -- I'm not familiar enough with all the different implementations to be an expert on that. Hans Bergsten likely is though - and he frequents the taglibs-user list.)
... and Struts even has it's own JSTL-ized tags, called Struts-EL. Essentially, these tags were written to make use of the JSTL Expression Language (often referred to as "the EL" or just "EL") in Struts native tags. They're very handy; essential (IMHO) at times.
Peace and GL!
Eddie
Sri Sankaran wrote:
JavaServer Pages (JSPs) help build the HTML that will be rendered on the client (browser). Since one person's application server is not in another's lexicon, let me say that JSPs must reside in the environment of a servlet container (such as Tomcat).1)The question I have is where will the JSP's reside. will they be deployed on the web-server or the application server.
A plain web-server (such as IIS or Apache) wouldn't know that to do with them. A web-server deals only with HTML artifacts. JSPs on the other hand can be comprised of HTML tags, specialized tags and Java code. Everything get converted (I am glossing over the details here) into HTML before getting routed back to the client. Some servlet engines (such as Tomcat) serve dual roles -- as web-server and as a servlet engine.
Needs a servlet container.2)where will struts reside,I think anwser to the first question should answer this.
Thanks Gopi
-- Eddie Bush
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
