今天想做整合，将Flex整合到SSH框架中来，由于之前已经将Flex与Java的通信调通，本以为这并不是一件复杂的事。没想到还是搞了两个小时。
我的想法是：Flex调用某个Java文件中的方法，然后我想在我的java方法中，调用Service层的业务逻辑方法。
在编写过程中，发现第一步没有问题，可以成功调用到Java文件中的方法，但第二步就出现问题了，因为Java文件中的Service对象始终为空，可我明明已经注入了。
后来加断点，看过程，发现在服务启动时，成功注入了Service层的方法，但是在调用的时候，还是空的。
这样，出现的问题可能是：Flex通过BlazeDS方式调用的那个Java实例并非Spring管理的，而是自己生成的，这样，自然也就没有被注入其他对象了。
找了好久，也试了一些方法，最后总算能实现了：
步骤：
1.自己写一个SpringFactory.java，放在哪无所谓。
import org.springframework.context.ApplicationContext;
import org.springframework.web.context.support.WebApplicationContextUtils;
import org.springframework.beans.BeansException;
import org.springframework.beans.factory.NoSuchBeanDefinitionException;
import flex.messaging.FactoryInstance;
import flex.messaging.FlexFactory;
import flex.messaging.config.ConfigMap;
import flex.messaging.services.ServiceException;
public class SpringFactory implements FlexFactory {
private static final String SOURCE = "source";
/**
* This method can be used to initialize the factory itself. It is called with configuration
* parameters from the factory tag which defines the id of the factory.
*/
public void initialize(String id,ConfigMap configMap) {
}
/**
* This method is called when we initialize the definition of an instance which will be looked
* up by this factory. It should validate that the properties supplied are valid to define an
* instance. Any valid properties used for this configuration must be accessed to avoid warnings
* about unused configuration elements. If your factory is only used for application scoped
* components,this method can simply return a factory instance which delegates the creation of
* the component to the FactoryInstance's lookup method.
*/
public FactoryInstance createFactoryInstance(String id,ConfigMap properties) {
SpringFactoryInstance instance = new SpringFactoryInstance(this,id,properties);
instance.setSource(properties.getPropertyAsString(SOURCE,instance.getId()));
return instance;
} // end method createFactoryInstance()
/**
* Returns the instance specified by the source and properties arguments. For the factory,this
* may mean constructing a new instance,optionally registering it in some other name space such
* as the session or JNDI,and then returning it or it may mean creating a new instance and
* returning it. This method is called for each request to operate on the given item by the
* system so it should be relatively efficient.
* <p>
* If your factory does not support the scope property,it report an error if scope is supplied
* in the properties for this instance.
*/
public Object lookup(FactoryInstance inst) {
SpringFactoryInstance factoryInstance = (SpringFactoryInstance) inst;
return factoryInstance.lookup();
}
static class SpringFactoryInstance extends FactoryInstance {
SpringFactoryInstance(SpringFactory factory,String id,ConfigMap properties) {
super(factory,properties);
}
public String toString() {
return "SpringFactory instance for id=" + getId() + " source=" + getSource()
+ " scope=" + getScope();
}
public Object lookup() {
ApplicationContext appContext = WebApplicationContextUtils
.getWebApplicationContext(flex.messaging.FlexContext.getServletConfig()
.getServletContext());
String beanName = getSource();
try {
return appContext.getBean(beanName);
} catch (NoSuchBeanDefinitionException nexc) {
ServiceException e = new ServiceException();
String msg = "Spring service named '" + beanName + "' does not exist.";
e.setMessage(msg);
e.setRootCause(nexc);
e.setDetails(msg);
e.setCode("Server.Processing");
throw e;
} catch (BeansException bexc) {
ServiceException e = new ServiceException();
String msg = "Unable to create Spring service named '" + beanName + "' ";
e.setMessage(msg);
e.setRootCause(bexc);
e.setDetails(msg);
e.setCode("Server.Processing");
throw e;
}
}
}
}
2.在services-config.xml中，在<services-config>中加上，class指向SpringFactory.java的位置
<factories> ?
? ? ? ? <factory id="spring" class="com.sq.factory.SpringFactory"/> ??
</factories>
3.在remote-config.xml中，加上factory节点。其名字即是factory 中的id
另要注意，此时source中不能再写java类的路径及名字，要写bean的名字
<destination id="helloWorld"> <properties> <factory>spring</factory> <source>dealFlex</source> <scope>application</scope> </properties> </destination>
