I need an effective suggestion
west timothy
Greenhorn
Posts: 6
posted 11 years ago
Hi all,
i have already posted my topic in the following mannner:
we have been assigned a project on designing a Job Portal(which is very much similar to Monster.com)
Could u please provide some links to some predefined templates that would guide us in choosing a proper Technology.
For the above topic i got the following replies from JAVARANCH
1.To use JSF.
But, we are not that aware of JSF because we are novice programmers and this is our first project.
we planned to implement using
1.JSP ,SERVLETS and JAVA BEANS with MySql as database
2. How about using STRUTS?.
Please suggest some workaround as early as possible to start our project.
with regards,
PAVAN
i have already posted my topic in the following mannner:
we have been assigned a project on designing a Job Portal(which is very much similar to Monster.com)
Could u please provide some links to some predefined templates that would guide us in choosing a proper Technology.
For the above topic i got the following replies from JAVARANCH
1.To use JSF.
But, we are not that aware of JSF because we are novice programmers and this is our first project.
we planned to implement using
1.JSP ,SERVLETS and JAVA BEANS with MySql as database
2. How about using STRUTS?.
Please suggest some workaround as early as possible to start our project.
with regards,
PAVAN
Roger Chung-Wee
Ranch Hand
Posts: 1683
posted 11 years ago
Struts is not essential and will add to your steep learning curve. Just focus on doing a clean design: keep Java code out of your JSPs, know when to use custom tags and JavaBeans, put all your business logic in your JavaBeans, write thread-safe code.
Ideally, design a three-layer architecture, with your JSPs, tags and servlets in a Presentation layer, your JavaBeans in a Business Logic layer, your DB code in a Data Storage layer, and with interfaces which clearly define the boundaries of the layers. If you can ensure that your JavaBeans can work with any client and with any persistant data store, you will be on the right path.
Ideally, design a three-layer architecture, with your JSPs, tags and servlets in a Presentation layer, your JavaBeans in a Business Logic layer, your DB code in a Data Storage layer, and with interfaces which clearly define the boundaries of the layers. If you can ensure that your JavaBeans can work with any client and with any persistant data store, you will be on the right path.
SCJP 1.4, SCWCD 1.3, SCBCD 1.3
Scott Duncan
Ranch Hand
Posts: 365
posted 11 years ago
Yes...Yes. To Roger Chung-Wee you listen.
Ahh I mean Roger is correct. Struts, arguably adds more complexity than JSF along with a higher learning curve (in my opinion). What he is describing is the MVC pattern (Model View Control). You would be wise to do a search on this and forget about frameworks for the time being. You'll have enough on your plate as it is.
Ahh I mean Roger is correct. Struts, arguably adds more complexity than JSF along with a higher learning curve (in my opinion). What he is describing is the MVC pattern (Model View Control). You would be wise to do a search on this and forget about frameworks for the time being. You'll have enough on your plate as it is.
No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
|