You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2007/05/20 06:41:43 UTC

[jira] Resolved: (WW-1810) Custom ObjectTypeDeterminer defined in struts.properties is not correctly set in XWorkConverter

     [ https://issues.apache.org/struts/browse/WW-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown resolved WW-1810.
---------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 2.0.8)

Since this is an XWork bug, closing as a duplicate

> Custom ObjectTypeDeterminer defined in struts.properties is not correctly set in XWorkConverter
> -----------------------------------------------------------------------------------------------
>
>                 Key: WW-1810
>                 URL: https://issues.apache.org/struts/browse/WW-1810
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.0.6
>         Environment: Tomcat 5.5.17
>            Reporter: Daniel Uribe
>         Assigned To: Rainer Hermanns
>
> When a custom ObjectTypeDeterminer is defined in the struts.properties file as follows, the instance of XWorkConverter (by default being AnnotationXWorkConverter) does not get its objectTypeDeterminer property set to an instance of the custom ObjectTypeDeterminer.
> struts.objectTypeDeterminer=CustomObjectTypeDeterminer
> What seems to be happening is that the injection and instantiation of AnnotationXWorkConverter is happening before the injection of the ObjectTypeDeterminer into the ObjectTypeDeterminerFactory. New instances of AnnotationXWorkConverter retrieve their instance of ObjectTypeDeterminer at initialization time by calling the ObjectTypeDeterminerFactory.getInstance() -- line 165 --, which at that moment doesn't have an instance of the custom ObjectTypeDeterminer. This effectively prevents the use of the custom ObjectTypeDeterminer with any operation done through OGNL, since it uses the instance that the AnnotationXWorkConverter has.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.