stripes actionresolve (一)

rivate Map<String,Class<? extends ActionBean>> formBeans =
            new HashMap<String,Class<? extends ActionBean>>();
还记得AnnotatedClassActionResolver是可配置组件呸，应该想到这个formBeans应该在init(Configuration)中设了值。确定在AnnotatedClassActionResolver的init()设了值，但是细心的会问到：这个实例不是NameBasedActionResolver的，而且它也有init(Configuration)，先看NameBasedActionResolver的init()方法。
@Override
    public void init(Configuration configuration) throws Exception {
        super.init(configuration);
        addActionBean(DefaultViewActionBean.class);
}
它调用了AnnotatedClassActionResolver。之后增加了一个DefaultViewActionBean的bean。这个是为了找到与之对应的jsp页面而用的。不做分析。
public void init(Configuration configuration) throws Exception {
     is.configuration = configuration;
Set<Class<? extends ActionBean>> beans = findClasses(ActionBean.class);
    ActionClassCache.init(beans);
        for (Class<? extends ActionBean> clazz : beans) {
            addActionBean(clazz);       }
    }

protected <T> Set<Class<? extends T>> findClasses(Class<T> parentType) {
        ResolverUtil<T> resolver = new ResolverUtil<T>();
        resolver.setPackageFilters(getPackageFilters());
        resolver.setLocationFilters(getUrlFilters());

        if (!resolver.loadImplementationsFromContextClassloader(parentType)) {
            ServletContext context = this.configuration.getBootstrapPropertyResolver()
                    .getFilterConfig().getServletContext();

            resolver.loadImplementationsFromServletContext(parentType, context);
        }

        return resolver.getClasses();

这个功能是找到所有actionbean的子类。Stripes1.5有些变化。接下的缓存没有什么好看的，关键在于addActionBean(clazz);循环把每个actionbean及其对应的urlbinging和处理方法加入到this. formBeans中。

 protected void addActionBean(Class<? extends ActionBean> clazz) {
       //取得actionbean中如@ UrlBinding(“/user/register.action”)中的/user/register.action值
 String binding = getUrlBinding(clazz);
   // Only process the class if it's properly annotated
   if (binding != null) {
            this.formBeans.put(binding, clazz);
      // Construct the mapping of event->method for the class
    Map<String, Method> classMappings = new HashMap<String, Method>();
           processMethods(clazz, classMappings);
      // Put the event->method mapping for the class into the set of mappings
            this.eventMappings.put(clazz, classMappings);
            // Print out the event mappings nicely
    for (Map.Entry<String,Method> entry : classMappings.entrySet()) {
                String event   = entry.getKey();
                Method handler = entry.getValue();
                boolean isDefault = DEFAULT_HANDLER_KEY.equals(event);
                log.debug("Bound: ", clazz.getSimpleName(), ".", handler.getName(), "() ==> ",
                          binding, isDefault ? "" : "?" + event);
            }
        }
    }
在上在的代码中有两个属性： formBeans、eventMappings，formBeans保存urlbinging的路径和与之对应的actionbean关系。eventMappings保存actionbean类与它的所有的处理事件方法的关系。这样，我们就可以通过路径（urlbinging）找到类，再通过actionbean的类找到它的事件方法。Actionbean类通过分析类的@UrlBinding就可以找到，如果没有,因为actonresolver的实例是基于命名。所以String binding = getUrlBinding(clazz)中调用是子类的方法。
@Override
    public String getUrlBinding(Class<? extends ActionBean> clazz) {
        String binding = super.基于annotation的;
        // If there's no annotated binding, and the class is concrete
        if (binding == null && !Modifier.isAbstract(clazz.getModifiers())) {    binding = getUrlBinding(clazz.getName());       }
        return binding;    }
getUrlBinding先调用父类的getUrlBinding(clazz)方法。之后把actionbean的类名按一定的规则转为urlbing路径。getUrlBinding(String name)就是实现这个功能：

protected String getUrlBinding(String name) {
        // Chop off the packages up until (and including) any base package
        for (String base : getBasePackages()) {
            int i = name.indexOf("." + base + ".");
            if (i != -1) {
                name = name.substring(i + base.length() + 1);}
            else if (name.startsWith(base + ".")) {
                name = name.substring(base.length());}   }
        // If it ends in Action or Bean (or ActionBean) take that off
        if (name.endsWith("Bean")) {
            name = name.substring(0, name.length() - 4);     }
        if (name.endsWith("Action")) {
            name = name.substring(0, name.length() - 6);        }

        // Replace periods with slashes and make sure it starts with one
        name = name.replace('.', '/');
        if (!name.startsWith("/")) {
            name = "/" + name;        }

        // Lastly add the suffix
        name += getBindingSuffix();
        return name;
    }
getUrlBinding(String name)就是一些字符转换，它把如com.morik.action.RegisterAction或者RegisterActionBean,变成Register.action.

解决了路径和actionbean的映射问题。接下来的processMethods(clazz, classMappings);就是如何把actionbean和它的所有的事件方法对应起来。
  protected void processMethods(Class clazz, Map<String,Method> classMappings) {
        // Do the super class first if there is one
        Class superclass = clazz.getSuperclass();
        if (superclass != null) {
            processMethods(superclass, classMappings);
        }

        Method[] methods = clazz.getDeclaredMethods();
        for (Method method : methods) {
            if ( Modifier.isPublic(method.getModifiers()) ) {            
 String eventName = getHandledEvent(method);
                DefaultHandler defaultMapping = method.getAnnotation(DefaultHandler.class);
                if (eventName != null) {
                    classMappings.put(eventName, method);
                }
                if (defaultMapping != null) {
                    // Makes sure we catch the default handler
                    classMappings.put(DEFAULT_HANDLER_KEY, method);
                }
            }
        }
    }
这个一个递归方法，它实现了从actionbean所有父类开始找标识为@DefaultHandler和DefaultHandler的处理方法。对于基于命名的方法，
 public String getHandledEvent(Method handler) {
        String name = super.getHandledEvent(handler); 
        if ( name == null && !Modifier.isAbstract(handler.getModifiers())
          &&R esolution.class.isAssignableFrom(handler.getReturnType()) ) {            name = handler.getName();        }
        return name;    }