My opinion is to not waste your time. Struts is going to start a major shift here soon if not already. "Shale" is going to have a JSF front with a Struts like backend but it still won't be the same as what you are doing right now.
Struts by itself is still a major standard in web frameworks. But I think you'd be wasting your time dealing with bugs (another
thread of yours ring a bell?).
With that being said I would also like to point out how well JSF has worked for me all by itself. The only time I'd see a reason to mesh JSF and Struts together right now is if you wanted the JSF components but didn't want to change all your actions to JSF managed beans. However, I'd still seriously consider the pros and cons of just biting the bullet and conerting it all. Technically if you built your application the right way moving your Actions over to Managed Beans shouldn't really be that big of a deal. It's all just data collection and navigation. All the real work should be in seperate classes anyway, right?