Hi Dan, The ISIS-1698 issue description says the collection's view always defaults to "table", but in my case it always defaults to "hidden".
The latter case seems more of a showstopper, we can't expect a user to click on the "table" button of a collection for every single entity he is looking at to create the appropriate hints in his session. I'll try to see if the fix for ISIS-1698 makes the problem go away. If that is the case, would a bugfix release for 1.15.1 be reasonable? 1.16.0 seems to be quite far away still and I want to move away from 1.14.0 if possible. Cheers On Tue, Dec 26, 2017 at 3:25 PM, Dan Haywood <[email protected]> wrote: > Hi Martin, > > this is a known issue which is fixed [1] in the latest -SNAPSHOT. Perhaps > you could build from master to confirm that the issue is fixed there? > > thx > Dan > > [1] https://issues.apache.org/jira/browse/ISIS-1698 > > On Tue, 26 Dec 2017 at 07:50 Martin Hesse <[email protected]> wrote: > > > Hi, > > > > after I migrated an existing project from 1.14.0 to 1.15.1 all my > > collections which were previously rendered eagerly (defaultView="table" > in > > layout xml) are now hidden / lazy by default. > > > > The layout xml has not been changed. > > > > I also tried to set the default view to "table" directly in a > > CollectionLayout annotation and also tried the deprecated EAGERLY render > > type in the CollectionLayout, but it didn't change the behavior. > > > > Any advice on where I could continue looking? This is kind of a show > > stopper. > > > > Thanks and regards > > Martin > > >
