[
https://issues.apache.org/struts/browse/WW-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeromy Evans resolved WW-2613.
------------------------------
Resolution: Fixed
Fix Version/s: 2.1.1
Assignee: Jeromy Evans
Done. It'll take some time to propagate.
Master copy: http://cwiki.apache.org/confluence/display/WW/Type+Conversion
You can also add comments directly to the page or improve the documentation
yourself:
http://struts.apache.org/2.x/docs/editing-the-documentation.html
> Type Conversion Guide doesn't describe where to put Class Name specific
> property files
> --------------------------------------------------------------------------------------
>
> Key: WW-2613
> URL: https://issues.apache.org/struts/browse/WW-2613
> Project: Struts 2
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 2.0.11.1
> Reporter: Steve Akins
> Assignee: Jeromy Evans
> Priority: Minor
> Fix For: 2.1.1
>
>
> In the Type Conversion Guide page
> (http://struts.apache.org/2.x/docs/type-conversion.html) it doesn't make it
> clear where to put a Class specific property file.
> It looks like what is there is a copy of the javadocs from
> com.opensymphony.xwork2.util.XWorkConverter.
> This is what's on the XWork Wiki
> (http://www.opensymphony.com/xwork/wikidocs/XWork%20Conversion.html) :
> To create an action-level conversion, create a file called
> 'ActionClassName-conversion.properties' in the same location at the classpath
> where the Action class itself resides. Eg. if the action class name is
> MyAction, the action-level convertion properties file should be named
> 'MyAction-conversion.properties'.
> This is a little better but I would make it clearer by adding something like
> this:
> Eg. If the Action class is 'com.myapp.actions.MyAction' then the
> action-level conversion properties file should be named
> 'MyAction-conversion.properties' and put in com/myapp/actions.
> This would help new people struggling to make sense of where all the various
> configuration files should go.
> I hope that this is the right forum to post documentation suggestions. If
> not, happy to post elsewhere.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
