Originally posted by glkrr reddy:
there is no need to use any componenets for creating calendar functionality.sheduling and reminders are must and should use stored procedure concept.and calendar you can use logical program
Originally posted by Frank Carver:
On the one hand you seem to have made a lot of technical decisions (please explain how/why you have already chosen JSP, Tomcat, MySQL and NetBeans, for example).
On the other hand, you tell us nothing at all about what the application is actually supposed to do! For you or us to try and make any design decisions or offer advice without knowing what is being designed is a sure road to misunderstanding and probable failure.
All we know about the application so far is that it has a web interface. I'm guessing this means a HTTP interface, rather than applet(s). The only sensible way to "talk" HTTP from Java is using servlets, so your solution will likely involve one or more servlets.
How you produce your servlet(s) (hand written, or produced using code-generation tools such as JSP etc.), how you produce the HTML for the web pages (JSP, custom tags, templates, raw HTML in Java etc.), and how you manage the interaction between the HTML data and the "business logic" is still open.
I'm particularly worried that you seem to be leaping to potentially complex solutions (JSP, struts, XML, EJB etc.) with no evidence of need. I'm also having a hard time imagining a system that really has 70-100 entirely different kinds of pages and how you plan to make a usable, testable and maintainable application using this approach.
Please tell us more about why you have made the decisions you have so far, and some idea of what this application is for, in real customer terms. Thanks.