Re: Velocity
From: Nathan Hazout (nathan_at_nathanhazout.com)
Date: 10/02/04
- Next message: Jim Cochrane: "Re: About Heavy Weight Component"
- Previous message: jin zhang: "How to debug through Java code and JNI with native code in c or c++ ?"
- In reply to: Will Hartung: "Re: Velocity"
- Next in thread: Sudsy: "Re: Velocity"
- Reply: Sudsy: "Re: Velocity"
- Reply: Bryan Castillo: "Re: Velocity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 02 Oct 2004 02:00:48 GMT
Thanks to both of you,
Sudsy : I'm gonna go step by step, see what he wants me do to first,
time is not that important for him right now.
If he asks me to go deep into java, there is something I need to know.
I looked up for 'Java' books on the web, but I know that java is also
used to make 'applets'. I don't think that's what I need to learn right?
Would sound more like 'Servlet' I think.
How to know if it's going to be the right book? Is there a different
name for 'Java servlets' ?
Thank you
Will Hartung wrote:
> "Nathan Hazout" <nathan@nathanhazout.com> wrote in message
> news:uok7d.397921$8_6.205369@attbi_s04...
>
>>Thanks,
>>Little question:
>>When you type the address of the website, it seems to load a page called
>>"home.do", but I couldn't find any file with that name in that directory.
>>Is that normal? Is this Java stuff?
>>Also, if you'd have a book to recommend to me ...
>
>
> Yeah, that .do extenstion is most probably from Struts.
>
> Struts is a very popular framework used to build websites. This is actually
> a good thing for you (IMHO), as it gives you more resources to turn to, and
> a structure to leverage, which means less detail to learn right away.
>
> Here's a summary of the "things you need to know", based on what you've told
> us.
>
> Java
> JDBC (assuming there's a database involved, and there probably is)
> Java Servlets
> JSP (perhaps)
> Struts
> Velocity
> Ant (can't fathom somone using Stuts and not using Ant)
>
> It sounds like they're using Velocity instead of JSP for rendering, but they
> may not be 100% consistent with that and could very well have mixed
> technologies.
>
> I would most certainly try and get a book on Struts, if for nothing else
> than to explain the relationship between the code, struts-config.xml, and
> web.xml in your web app.
>
> I have the book "Struts in Action", and it's a pretty good book, others may
> have other suggestions.
>
> The things you need to figure out, in order, I think are:
>
> building the system (type ant -projecthelp to get a summary of the
> build.xml)
> deploying the system (it hopefully just creates a .WAR file for you to copy
> to the server [probably Tomcat]. Even better if it deploys automatically.)
> understanding how Struts ActionForms and Actions and JSP/Velocity interact
> (at a higher level)
> understand HttpServletRequest
> changing an existing ActionForm
> changing an existing action (home.do is a Struts action, and has a
> HomeAction.java class [I imagine] someplace managing its logic).
> changing an existing Velocity template
> adding a new ActionForm
> adding a new action
> adding a new Velocity template
>
> These are all pretty high level. You don't need an intimate understanding of
> any of these technologies to actually be productive, obviously it depends on
> what kind of work you need to do.
>
> Ant, Struts, Tomcat [if you're using this as your servlet container] and
> Velocity are all "documented" and available from apache.org. Start at
> jakarta.apache.org and go from there.
>
> I'm relying on the fact that you have a working system, that it was
> reasonably organized using most of the practices suggested for Struts
> development, and that you're not redoing the whole thing from scratch or
> adding any dramatic new functionality right away. The trick is to grok the
> vocabulary and rely on the in place code for examples and details. While
> what you have may not be "perfect best practices" (whatever they are), it's
> (apparently) functional and you should be able to use it as a bedrock for
> your incremental improvements without having to be expert in any of these
> new areas. If it worked for the previous coder, it will probably work for
> you. As you get better and more versed in the techniques and technologies,
> perhaps you can come back and replace anything you do now that "stinks
> later".
>
> Good Luck!
>
> Regards,
>
> Will Hartung
> (willh@msoft.com)
>
>
>
- Next message: Jim Cochrane: "Re: About Heavy Weight Component"
- Previous message: jin zhang: "How to debug through Java code and JNI with native code in c or c++ ?"
- In reply to: Will Hartung: "Re: Velocity"
- Next in thread: Sudsy: "Re: Velocity"
- Reply: Sudsy: "Re: Velocity"
- Reply: Bryan Castillo: "Re: Velocity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
