This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
It seems like a valid question for this forum. I have two general comments on this. First off, I would not recommend implementing design patterns just for the sake of implementing design patterns. Certain patterns, such as the DAO pattern, are useful in a number of situations but you should let your technology, architecture and requirements drive the patterns that you use.
As far as "implementation of these patterns with Struts", Struts is a presentation layer framework. You mention the DAO and VO patterns. These patterns are more data and business layers patterns. While they can be used in architecture along side Struts, they are not related to Struts and you would not implement them with Struts. Struts is generally viewed as an implementation of the MVC pattern.
There's nothing special to know about using J2EE patterns in a Struts applications. Struts assumes you will write your own model classes, and it's entirely up to you how you write them. Once you have written your model classes, it is your Action class that will instantiate them and call methods on them to do the actual work of the application.
So, for example, if you know how to create an object that follows the Data Access Object (DAO) pattern, go ahead and create one. Then instantiate it in your Action class and use it to do the work of your application.