[
https://issues.apache.org/jira/browse/ISIS-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315450#comment-15315450
]
ASF subversion and git services commented on ISIS-1425:
-------------------------------------------------------
Commit 33b75cb070a9b158a0affba3c17359f20151dfb4 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=33b75cb ]
ISIS-1425: refactored so that if fail to dereference regular action/mixin (to
get to mixedin action/target) then indicate optionally by returning null rather
than failing fast with an exception. Allows less ugly code to fallback to
original behaviour.
> Fix support for publishing of wrapper calling programmatically instantiated
> mixin.
> ----------------------------------------------------------------------------------
>
> Key: ISIS-1425
> URL: https://issues.apache.org/jira/browse/ISIS-1425
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.12.1
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.0
>
>
> suppose we have a mixin:
> Touchable_touch
> whose action "$$" is published.
> What already works is that this will be published as an action "touch" on the
> mixed-in domain object.
> However, if we try to do this programmatically via the WrapperFactory, ie
> {code}
> wrapperFactory.wrap(factoryService.mixin(Touchable_touch.class,
> touchable)).$$();
> {code}
> then the target that is published is the (transient) mixin object itself,
> rather than the domain object.
> ~~~
> The fix is therefore to make the wrapper factory's wrapper proxy more
> intelligent, by invoking on the mixed-in action on the mixed-in domain
> object, rather than simply on the regular default action of the mixin
> (transient) object.
> If this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
