Stefan Huehner

Hello, i'm extending my question a bit to also cover "Immediate display of calculated properties / @Calculation in editable Tab" is also not possible ? From a brief look at the code that looks like to be also tied to missing a View while being in a editing Tab context? Is maybe the restriction in this section i mentioned above "Be careful! because the save action of the module is not executed to save the value, nor are the @OnChange actions executed. That is, validations at the model level (annotations,...

Hello, i'm extending my question a bit to also cover "Immediate display of calculated properties in editable Tab" is also not possible ? From a brief look at the code that looks like to be also tied to missing a View while being in a editing Tab context? Is maybe the restriction in this section i mentioned above "Be careful! because the save action of the module is not executed to save the value, nor are the @OnChange actions executed. That is, validations at the model level (annotations, setters,...

Hello, i was trying to use a @DefaultValueCalculator like this @DefaultValueCalculator(value = DurationCalculator.class, properties = { @PropertyValue(name = "startDate"), @PropertyValue(name = "startTime"), @PropertyValue(name = "endDate"), @PropertyValue(name = "endTime") }) @ReadOnly Integer durationMin; to calculated value of durationMin which works just fine when creating new record in a View or editing existing record in a view. However when editing a record in the Tab where have the 4 referenced...

Hi Jörn, not directly an answer to your question but maybe still useful. a.) Mandatory fields are already marked by default But it's a bit hard to see (slightly different border around the fields). It's a bit easier to see cycling through the various skins. b.) There's an open Issue for openxava version 8.0 to change that to the more typical (*) marker https://openxava.org/xavaprojects/o/OpenXava/m/Issue?detail=ff8080818e41f752018e42216d980003 With version 8.x planned to come out around September...

Hi, I'm not sure where to report this behavior or what it will be (just developer error, feature request for new warning or a bug) so starting here. when having a single wrongly named property like String BadName; // uppercase B instead of String badName; // lowercase b which doesn't follow java naming conventions that causes 3 problems (all seen in crud list view) a.) The whole view sorting is broken (it just ignores all filters without any warning or error message on why) Technically this line...