> I'm sorry. It's a kind of help desk in our intranet where the users can: > 1) Request technical assistance (input) > 2) Query the status of their previous requests > 3) Query a DB where any user can look at common problems/solutions > > We have 500 total users. I think there could be 10/20 users (max) using > the app simultaneously. We are not planning to use EJB, WS or LDAP. > We have been considering to use a relational DB (Oracle).
There are commercial applications for this very purpose, so I'm not sure why you're looking at building this yourself? However, given that you are, I'd guess you have no need for multiple language support, no need for eventually scaling the thing to support a lot of users, and no need for multiple browser support. As such, Cocoon is likely overkill. It's not even clear that you need much of a flexible controller structure (any dynamic work flow?), but Struts won't do you any harm. Otherwise this could just be a simple JSP site or just HTML with Servlets... If you have control over the browser you might want to look at DHTML or client side XML/XSLT with CSS just to keep presentation separated a little better. Personally, I'd likely go with a client side XML/XSLT and Servlet implementation, but I don't know if your shop can handle the XSLT authoring (it's a bit of a paradigm shift from Java coding)? I also don't know what other infrastructure I'd add to the mix without knowing the requirements better. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
