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.
That's both a complicated question and an easy one.
It's easy because Struts is primarily concerend with the server side and can co-exist beautifully with Ajax on the client. Whether a request is made to a Struts action or not is pretty irrelevant. The response will still be returned to the client which could care less what gyrations occured on the server in order to compose it.
Where things might get complicated is with the use of Struts custom tags on the pages. Knowing exactly what markup is getting generated from the tags is crucial to being able to manipulate the DOM created by that markup.
Sometimes, all it takes is a simple View Source from the browser to figure such things out.
Not being a fan of Struts, I'm not sure what other interaction issues might arise, but for the most part, I see no reason that Ajax and Struts cannot peacefully co-exist in a web application with just a little bit of care.