Sets not appearing in "show" views.

[Stefan Schmidt]

Ok, great! The Roo Jira is actually quite well known. There is also a sticky thread in this forum (also linked from the Roo start page) which provides all relevant links and info: http://forum.springsource.org/showth...ersion-details. If you try google it should also be the first hit. Any other places you can think of where we can make it more prominent?

[carlos.l.sanchez]

In some "immediate" locations like:

*** In the documentation, for example:
[STS install root]/spring-roo-1.1.5.RELEASE/docs

*** On the browser page automatically launched after installing STS.

*** In STS's Dashboard View.

Also, the presence of ROO as one of the available components when creating an STS ticket is confusing, as it seems to confirm that that's the correct location to create ROO tickets...

[carlos.l.sanchez]

Stefan,

I added a comment to
https://jira.springsource.org/browse/ROO-2603

to clarify that
"
the problem is in fact:

* not that Sets are displayed on the "list" views (although that is indeed not necessary), but

* that Sets are not displayed on the "show" views...

"

I want to make sure that you see the important comment even though you marked the ticket as Resolved / Fixed...

[Stefan Schmidt]

Carlos, with Roo 1.2.0 release you will see that these sets are not presented in either your show or list views any more.

[carlos.l.sanchez]

Stefan,

I was apparently not clear: Sets SHOULD be displayed on the "show" views!

[Stefan Schmidt]

Hi Carlos,

Currently one to many reference relationships are not displayed in show views for multiple reasons:

- What happens if domain objects which are part of your set have references to other entities - do you expect to see the details of those too? Where would you stop?
- What happens if domain objects which are part of your set have references to the containing entity (cyclic references)? You get a stack overflow error.
- What happens if the referenced set is very large? Would you be happy to see details of say 10000 referenced entities? Especially if they have 50 fields each?
- One could argue we could display the set size but that requires a DB query just to determine its size (potentially expensive).
- One could argue Roo could offer links to referenced entities but that requires the same expensive DB query, and also may be undesirable for very large sets.

This hopefully illustrates why displaying set contents this is not an optimal solution in most cases. '

However nobody holds you back from adjusting your tags to actually present the information you need.

[carlos.l.sanchez]

Stefan,

I think that only showing the single, versus collection, attributes is inconsistent. And also atypical. How else do you view an collection attribute? You need to, somehow...

As far as implementation, there is no need to show the whole tree, i.e. it is sufficient, and again typical, to only show the immediate items in the collection attribute.

As for exploring the composition of the items in the the collection (and, for that matter, single!) attributes, that's where the following request is valuable:
https://jira.springsource.org/browse/ROO-654

According to which, in 24/Feb/10 (when the ticket was created), "scaffolding engine generate[d] in show.jspx view of Owner plain text list of pets".

[carlos.l.sanchez]

Agreed, Stefan?