Our action classes have their life cycle managed by spring, and they are /request/ scoped. When the convention plugin initializes the struts configuration it tries to initialize the spring beans. This does work because "request" scope does not exist at the time the struts config is created.
The enclosed patch simply removes the eager-loading since it is only done as an optimization (and maybe eager early consistency check). It would be possible to make this a flag although I really think the default should be "off"; the "off" behavior is consistent with behavior of "older" struts technologies in this respectearlier struts versions..