这个算法是O（1）吗？(Is this algorithm O(1)?)

 首先，我建议您探索Struts 2 Spring集成，而不是尝试将spring集成到struts 2中。 这种集成由Strut 2 Spring插件提供。 你应该检查一下; 它允许您轻松地将bean注入struts 2操作，更不用说框架创建的所有其他对象。 这是一个链接 。 
 
 但是，即使基于您在代码片段中的内容，我也可以提供一些Spring基础知识的清晰度。 setter定义的bean属性必须与bean属性名称匹配。 没有这个，财产注入将无法运作。 但是，听起来你改变了字段本身的名称以匹配; 这将是现场注入。 完全不同的机制。 我建议你真的需要理解属性注入，场注入和构造函数注入的概念，以及自动布线的概念。 对不起，如果我误认为你没有拨打这个东西; 看起来你不喜欢。 
 
 但是，我建议你有更大的问题。 bean中存在依赖循环。 考虑这两个： 
 
  <bean id="insertUserProfile" class="lotmovement.business.crud.InsertUserProfile">
        <property name="registeraction" ref="registeraction"/>
        <property name="entitystart" ref="entitystart"/>
        <property name="userprofile" ref="userprofile"/>

    </bean>

    <bean id="registeraction"  class="lotmovement.action.RegisterAction">
        <property name="insertUserProfile" ref="insertUserProfile"/>
        <property name="entitystart" ref="entitystart"/>
        <property name="recordexistuserprofile" ref="recordexistuserprofile"/>
    </bean>  
 
 我不确定春天是否允许这样做，但是如果它确实如此，则必须做出一些关于注射如何下降的任意决定，因为它根本不可能以正常方式满足循环，我想。 

First of all, I would suggest that you explore the Struts 2 Spring integration instead of trying to integrate spring into struts 2 yourself. The integration is provided by the Strut 2 Spring plugin. You should check it out; it allows you to easily inject beans into your struts 2 actions, not to mention all other objects created by the framework. Here's a link.
 
But, even based upon what you have in your code snippets, I can provide some clarity on a couple of Spring fundamentals. The bean property as defined by the setter must match the bean property name. Without this, property injection wouldn't work. However, it sounds like you changed the name of the field itself to match; this would be field injection. Completely different mechanisms. I suggest that you really need to understand the concepts of property injection, field injection and constructor injection, as well as the concept of auto-wiring. Sorry, if I'm misassuming that you don't have this stuff dialed; seems like you don't though. 
 
HOWEVER, I suggest you have a bigger problem though. There is a dependency cycle in your beans. Consider these two:
 
  <bean id="insertUserProfile" class="lotmovement.business.crud.InsertUserProfile">
        <property name="registeraction" ref="registeraction"/>
        <property name="entitystart" ref="entitystart"/>
        <property name="userprofile" ref="userprofile"/>

    </bean>

    <bean id="registeraction"  class="lotmovement.action.RegisterAction">
        <property name="insertUserProfile" ref="insertUserProfile"/>
        <property name="entitystart" ref="entitystart"/>
        <property name="recordexistuserprofile" ref="recordexistuserprofile"/>
    </bean>  
 
I don't know for sure whether spring allows this, but if it did it would have to make some arbitrary decision about how the injections go down as it's simply not possible satisfy a cycle in a normal fashion, I think.