[
https://issues.apache.org/jira/browse/WW-3871?focusedWorklogId=1032719&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1032719
]
ASF GitHub Bot logged work on WW-3871:
--------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jul/26 05:55
Start Date: 29/Jul/26 05:55
Worklog Time Spent: 10m
Work Description: lukaszlenart merged PR #1812:
URL: https://github.com/apache/struts/pull/1812
Issue Time Tracking
-------------------
Worklog Id: (was: 1032719)
Time Spent: 2h (was: 1h 50m)
> TypeConversion annotation support improvement
> ---------------------------------------------
>
> Key: WW-3871
> URL: https://issues.apache.org/jira/browse/WW-3871
> Project: Struts 2
> Issue Type: Improvement
> Components: Plugin - Convention
> Affects Versions: 2.3.4.1
> Reporter: Pavan Ananth
> Assignee: Lukasz Lenart
> Priority: Major
> Fix For: 7.3.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The annotation support for TypeConversion in Struts 2 is too literal an
> interpretation of the XML support. For instance, I am required to supply this
> if I have choose the CreateIfNull feature at a property level :
> @TypeConversion(key="CreateIfNull_users", rule=ConversionRule.CreateIfNull,
> value="true")
> List<User> users;
> Given that the rule is CreateIfNull, the key can be constructed implicitly
> using property name - why is it asked of an user to type in the full key.
> This holds good for the other supported ConversionRules as well
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
