[
https://issues.apache.org/jira/browse/ISIS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440566#comment-16440566
]
Andi Huber edited comment on ISIS-898 at 4/17/18 8:44 AM:
----------------------------------------------------------
Status so far:
We are still working on the 'proof of concept'.
!tree.png!
A Wicket's tree component gets rendered, but the intended behavior of lazily
fetching child nodes on user interaction does not work yet:
{noformat}
09:58:05,861 [RequestListenerInterface http-nio-8080-exec-110 WARN ] behavior
not enabled; ignore call. Behavior
org.apache.wicket.ajax.markup.html.AjaxFallbackLink$1@ab811ce at component
[AjaxFallbackLink [Component id = junction]]
09:58:05,864 [RequestCycleExtra http-nio-8080-exec-110 WARN ]
********************************
09:58:05,865 [RequestCycleExtra http-nio-8080-exec-110 WARN ] Handling the
following exception
org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException:
Behavior rejected interface invocation. Component: [AjaxFallbackLink [Component
id = junction]] Behavior:
org.apache.wicket.ajax.markup.html.AjaxFallbackLink$1@ab811ce Listener:
[RequestListenerInterface name=IBehaviorListener, method=public abstract void
org.apache.wicket.behavior.IBehaviorListener.onRequest()]
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:237)
{noformat}
I do not understand the framework well enough yet, to fix this.
All the 'Isis to Wicket' adapting magic is happening here [1]:
[1]
[https://github.com/apache/isis/blob/dev/2.0.0/ISIS-898-treeview/core/viewer-wicket-ui/src/main/java/org/apache/isis/viewer/wicket/ui/components/tree/IsisToWicketTreeAdapter.java]
was (Author: hobrom):
Status so far:
We are still working on the 'proof of concept'.
!tree.png!
A Wicket's tree component gets rendered, but the intended behavior of lazily
fetching child nodes on user interaction does not work yet:
{noformat}
09:58:05,861 [RequestListenerInterface http-nio-8080-exec-110 WARN ] behavior
not enabled; ignore call. Behavior
org.apache.wicket.ajax.markup.html.AjaxFallbackLink$1@ab811ce at component
[AjaxFallbackLink [Component id = junction]]
09:58:05,864 [RequestCycleExtra http-nio-8080-exec-110 WARN ]
********************************
09:58:05,865 [RequestCycleExtra http-nio-8080-exec-110 WARN ] Handling the
following exception
org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException:
Behavior rejected interface invocation. Component: [AjaxFallbackLink [Component
id = junction]] Behavior:
org.apache.wicket.ajax.markup.html.AjaxFallbackLink$1@ab811ce Listener:
[RequestListenerInterface name=IBehaviorListener, method=public abstract void
org.apache.wicket.behavior.IBehaviorListener.onRequest()]
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:237)
{noformat}
I do not understand the framework well enough yet, to fix this.
> Add a table tree view to the Wicket viewer.
> -------------------------------------------
>
> Key: ISIS-898
> URL: https://issues.apache.org/jira/browse/ISIS-898
> Project: Isis
> Issue Type: New Feature
> Components: Core: Viewer: Wicket
> Affects Versions: viewer-wicket-1.6.0
> Reporter: Dan Haywood
> Assignee: Andi Huber
> Priority: Minor
> Fix For: 2.0.0-M2
>
> Attachments: tree.png
>
>
> see mailing list discussion [1]
> [1] http://markmail.org/message/vu3jqmlawrskplic
> ~~~
> some further thoughts:
> For example, in Estatio there are several hierarchies
> EstatioInstance ("global") /
> EstatioInstance ("italy") /
> EstatioInstance ("Roma shopping mall")
> or:
> Property/
> Floor/
> Unit
> We'd like to render these objects in a single tree/table collection.
> ~~~
> We should distinguish two cases:
> - where all the rows are of the same type (EstatioInstance, turtles all the
> way down).
> - where all the rows are of different types (Property/Floor/Unit)
> For the former, the columns to use are exactly those of the (single) class.
> For the latter, things are more complicated, as all the objects are of
> different class. It's not clear to me what (apart from an icon and a title)
> should be shown as columns. Perhaps just the intersection of those
> properties that are common across all types (eg name?) . Or perhaps there's
> metadata (in @PropertyLayout(...)) to specify that a particular property
> should always be shown in such tree/table collections, even if it is null for
> other rows for instances of some other class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
