This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
Any hints for what would be suitable as a set of standards (they must be well accepted) to set when defining an approach to delivering small applications based on JSP/Servlet technology and BEA/Oracle as the container and persistence combination. So far we have established struts as one standard but would be interested to hear opinions around Velocity, Tiles and anything else we should be thinking of (web services and SOA may come into the picture as well...)
I would vote for: -Struts, to handle common framework services -JSTL, to handle presentation in JSPs. It's enough simple as Velocity (not SO simple, to be honest), but a lot more powerful and extensible. -A good persistence mechanism (yes, Hibernate is a good one, but also JDO). Forget EJBs in a small application, even if you're already under BEA or Oracle. They would be an overkill. [ March 17, 2004: Message edited by: Fabrizio Gianneschi ]
Fabrizio Gianneschi<br />SCPJ2, SCWCD, SCBCD
Watchya got in that poodle gun? Anything for me? Or this tiny ad?