[
https://issues.apache.org/jira/browse/ISIS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-1487:
--------------------------------------
Fix Version/s: (was: 2.9.0)
2.0.0-M3
Summary: [WON'T FIX] Extend the framework's metamodel to be able to
render List<Map<String,Object>> (was: Extend the framework's metamodel to be
able to render List<Map<String,Object>>)
no business driver for this.
> [WON'T FIX] Extend the framework's metamodel to be able to render
> List<Map<String,Object>>
> ------------------------------------------------------------------------------------------
>
> Key: ISIS-1487
> URL: https://issues.apache.org/jira/browse/ISIS-1487
> Project: Isis
> Issue Type: New Feature
> Components: Isis Core
> Affects Versions: 1.13.0
> Reporter: Daniel Keir Haywood
> Priority: Minor
> Fix For: 2.0.0-M3
>
>
> To support this dynamic requirement, the framework (as currently architected)
> would need to build an ObjectSpecification based on the Map instances being
> rendered, whose structure is inferred from the members of that Map.
> I could imagine it would be possible to do, but would require some work
> within the SpecificationLoader. For example, perhaps the special-case
> handling here [2] could be extended to return a MapSpecification that handles
> the dynamic stuff... the issue though is that it would need to be told about
> a particular Map to look into. It would be hacky, but maybe putting the Map
> in question onto a ThreadLocal would suffice.
> [2]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/metamodel/specloader/SpecificationLoader.java#L401
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
