Printable View
I've got an application context created by using the contextConfigLocation servlet of spring and I can get to the context in an action.
However, I want to use a bean that is create via the constructor of an ActionForm. What is the best practice for getting an applicationContext in a Struts form. I can use ClasspathXmlAppContect or XmlBeanFactory, but is there a way to get the context similarly to the setServlet of the Struts Action?
Thanks!
AFAIK, Struts ActionForms should be /must be exclusively/ used to gather user input. No particular processing should go inside ActionForms.
IMHO, your Action should get the bean from the Context then inject the indeed data into your ActionForm.
is called on ActionForms. You should be able to retrive the application context out of that in an identical way you do in the Action class.Code:void setServlet(ActionServlet actionServlet)
Mike
Mike,
Do you think it is a good design to bind ActionForms to Spring Framewok?
I'm not processing. What does occur is that I use a form as a wrapper to a bean that does hold the data collected by the form. In addition, this bean has a DataValidator interface which in turn has a BaseErrors generic error object similar to a Struts ActionErrors. I use Spring to create this bean which gets inject by the DataValidator which gets injected by the BaseErrors.Quote:
Originally Posted by irbouho
My form's validate method delegates validation to this valueObject(in essence) which delegates to this DataValidator.
Now, my validation is decouple completely from Struts. Later, in my Action, I pull this bean out of the form and pass it to my middle tier where it becomes the data in a businessobject(also created by Spring).
Currently, in the form constructor, I call the XmlBeanFactory to create this object, but I was wondering if there was a better way.
I actually tried that, but unfortunately, this method wasn't called by the Struts framework the way the Action's setServlet is.Quote:
Originally Posted by futang
irbouho,
No I wouldn't suggest it, but the feature is there and it's certainly possible there is some benefit (i.e. this isn't life or death, giving people enough rope to hang themselves is ok with me). On the other hand now that I've used SpringMVC and Webwork2, Struts ActionForms make me cry.
Mike
jominor,
could you expand on what's happening? I haven't used this feature and was operating based on the javadoc. After reading your last post I checked the source (CVS HEAD) and it looks like the ActionServlet should be set before processing occurs. The following is from FormBeanConfig and is called to create the ActionForm instance.
Code:public ActionForm createActionForm(ActionServlet servlet)
throws IllegalAccessException, InstantiationException {
Object obj = null;
// Create a new form bean instance
if (getDynamic()) {
obj = getDynaActionFormClass().newInstance();
} else {
obj = formBeanClass().newInstance();
}
ActionForm form = null;
if (obj instanceof ActionForm) {
form = (ActionForm)obj;
} else {
form = new BeanValidatorForm(obj);
}
form.setServlet(servlet);
if (form instanceof DynaBean &&
((DynaBean)form).getDynaClass() instanceof MutableDynaClass) {
DynaBean dynaBean = (DynaBean)form;
MutableDynaClass dynaClass = (MutableDynaClass)dynaBean.getDynaClass();
// Add properties
dynaClass.setRestricted(false);
FormPropertyConfig props[] = findFormPropertyConfigs();
for (int i = 0; i < props.length; i++) {
dynaClass.add(props[i].getName(), props[i].getTypeClass());
dynaBean.set(props[i].getName(), props[i].initial());
}
dynaClass.setRestricted(isRestricted());
}
return form;
}
I'm afraid I misspoke. It wasn't that setServlet wasn't called, I just need(or at least want) the context at form creation time. Ultimately, I want my bean created after the form is created, but before someone would do something with the form.Quote:
Originally Posted by futang
The XmlBeanFactory does work in the constructor, but I want to make sure that I wasn't overlooking anything. Ultimately, what I'm doing is the results of taking advantage of Spring. Pre-Spring, I still had data objects that were used to hold data with form getter/setters passing data directly into this object. I also had the DataValidator and other stuff I mentioned in a previous post. My goal is Struts decoupling and reuse of both valueobject and validation in presentation and middle-tiers. This is a goal I've pretty much realized, but Spring influences have made me realized that with some small refactoring, I can take advantage of Spring to handle creating some of the things, I was doing by hand.
I'm pleased with the results, but it seems that the beanfactory will give me the results I desire.
jominor,
1. If you want to access Spring Context from within your Struts Actions please, take a look at org.springframework.web.struts.ActionSupport and org.springframework.web.struts.DispatchActionSuppo rt.
All you need to do, is make your Struts Action/DispatchAction extend Spring classes respectively instead of Struts' one. To extract beans form your Context, you can use:
2. As for accessing Spring Context from within your Struts ActionForms, Spring provides no support for that, but you can implement it yourself (some copy/past from Spring ActionSupport.java). Spring Implementation for Struts Actions Support is (as usually) very clean. Just stick to it, and it will reponses 100% to the needs you expressed in this thread.Code:getWebApplicationContext().getBean("beanName");
3. Using ActionSupport, DispatchActionSupport (and perhaps ActionFormSupport / ValidatorFormSupport :wink:) to access the ApplicationConext is far more cleaner and performant than going the hard way with XMLBeanFactory.
Please let me know if you need more help to create ActionFormSupport / ValidatorFormSupport.