I also have noticed some classloading issues with the j4 distro.  In my
case, WebSphere 6.0 is not able to load a retrotranslated version of the
sitemesh plugin.  I think in your case, the preferred method of
integrating Spring is to put the following line in struts.properties
(this file is searched for as a resource in the classpath, e.g.
/WEB-INF/classes/struts.properties):

struts.objectFactory=spring

You should not need to put a constant element in web.xml if you do that
instead.  I'm actually not entirely sure that is needed either, as I
remember seeing somewhere that Spring is already the default IoC
container for Webwork 2, and that may apply to Struts 2 as well.  If it
is working, you should see a line in your SystemOut.log about
"initializing Spring integration."  Hope all that helps.


>>> "Ádamo Azambuja" <[EMAIL PROTECTED]> 10/18/07 11:51 AM >>>
When i use this configuration on my web.xml:
<constant name="struts.objectFactory" value="
org.apache.struts2.spring.StrutsSpringObjectFactory" />
i have the struts2-spring-plugin-2.0.9.jar in my classpath.

i have this error:
14:46:50,246  INFO XmlConfigurationProvider:140 - Parsing configuration
file
[struts-plugin.xml]
StandardContext[/strutsBlank]Exception starting filter struts2
Unable to load bean: type:com.opensymphony.xwork2.ObjectFactory class:
org.apache.struts2.spring.StrutsSpringObjectFactory - bean -
jar:file:/C:/projetos/struts2-blank-2.0.9/WebContent/WEB-INF/lib/struts2-
spring-plugin-2.0.9.jar!/struts-plugin.xml:8:132
    at
com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.register(
XmlConfigurationProvider.java:208)
    at
org.apache.struts2.config.StrutsXmlConfigurationProvider.register(
StrutsXmlConfigurationProvider.java:101)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to