Paulo, I have used both Barracuda and Struts extensively. Here is what I think of both: Barracuda: Is true MVC and provides a clear separation of GUI and code. It treats an HTML page as an object (a DOM). Therefore the "view" in the MVC is passive, which is as it should be in a true MVC model. One group of developers can work on the "view" and another can work on the other, logic driven portions of the application. It is a bit harder to learn than Struts, though and doesn't have nearly the following or documentation that Struts has. Struts: Since it is JSP there must be code in the "view", even if it is hidden within taglibs. Struts is easier to learn, and has a lot of documentation. It is more popular that Barracuda mainly because it is part of the well-known Jakarta initiative. What I've seen of applications that use JSPs (whether with Struts or not) is that they end up having a lot of code in the JSP itself. Usually this results in duplicate code and maintenance problems. With JSP there is no way to enforce a true MVC model, or even a true object-oriented design for that matter. I can understand the controversy between you and your manager, although usually I've seen it the other way around: the manager wants to use Struts because it is well known and it is easier to find developers who know it. If I had to make a recommendation based on my technical knowledge of both though, the clear choice is Barracuda. Kevin
--------------------------------- Do You Yahoo!? HotJobs, a Yahoo! service - Search Thousands of New Jobs
