I thought about that, however, there are two advantages to keeping
everything in struts-default.xml:
1. Default implementations for extension points can be named "struts"
universally. Otherwise, we'd have to allow two, xwork and struts, or
choose a third option.
2. Easier for a new developer to see how struts configures itself.
Since we publicize the struts-default, struts-plugin, struts.xml load
order, it is less confusing to not have the additional hidden
xwork-default.xml
I'm open to changing this if there are other good options on the table.
Don
tm jee wrote:
Hi guys,
Shouldn't we have the xwork stuff in xwork-default.xml? In struts-default.xml,
There's some common beans like
<bean class="com.opensymphony.xwork2.ObjectFactory" name="xwork" />
<bean type="com.opensymphony.xwork2.ObjectFactory" name="struts"
class="org.apache.struts2.impl.StrutsObjectFactory" />
<bean type="com.opensymphony.xwork2.ActionProxyFactory" name="xwork" class="com.opensymphony.xwork2.DefaultActionProxyFactory"/>
<bean type="com.opensymphony.xwork2.ActionProxyFactory" name="struts"
class="org.apache.struts2.impl.StrutsActionProxyFactory"/>
...
<bean type="com.opensymphony.xwork2.util.ObjectTypeDeterminer" name="tiger"
class="com.opensymphony.xwork2.util.GenericsObjectTypeDeterminer"/>
<bean type="com.opensymphony.xwork2.util.ObjectTypeDeterminer" name="notiger"
class="com.opensymphony.xwork2.util.DefaultObjectTypeDeterminer"/>
<bean type="com.opensymphony.xwork2.util.ObjectTypeDeterminer" name="struts"
class="com.opensymphony.xwork2.util.DefaultObjectTypeDeterminer"/>
..
<bean class="com.opensymphony.xwork2.util.OgnlValueStack" static="true" />
that might be better if moved to xwork-default.xml Am I missing somthing?
rgds
Send instant messages to your online friends http://uk.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
