[
https://issues.apache.org/jira/browse/ISIS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-992:
-----------------------------
Summary: [WON'T FIX] Extend Isis metamodel and Wicket viewer so that a
"delete" action can be automatically provided for deleteable objects. (was:
Extend Isis metamodel and Wicket viewer so that a "delete" action can be
automatically provided for deleteable objects.)
> [WON'T FIX] Extend Isis metamodel and Wicket viewer so that a "delete" action
> can be automatically provided for deleteable objects.
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-992
> URL: https://issues.apache.org/jira/browse/ISIS-992
> Project: Isis
> Issue Type: New Feature
> Components: Core, Core: Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Priority: Major
> Fix For: 3.0.0
>
>
> per [1],
> @DomainObject(
> deleteable=true
> ...
> )
> public class MyClass { .. }
> could be used to automatically generate a delete() action:
> public void delete(Entity entity) {
> this.getContainer().remove(entity);
> this.getContainer().flush();
> }
> ~~~~
> However, there are some things that need to be thought through here. For an
> explicitly coded action there would be all the annotations/metadata in
> @Action and @ActionLayout. Where would that information be specified if the
> action is synthesized on the fly? Would the @DomainObject annotation need to
> be extended instead as, for example:
> @DomainObject(
> deleteAction=@Action(...),
> ...
> )
> I'm not completely convinced the extra complexity is worth it to save four
> lines of code.
> [1] http://isis.markmail.org/thread/jdylmfxrzdryhrlq
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
