[MGNLUI-1075] Consider using complete Vaadin Form management cycle. Created: 09/Apr/13  Updated: 28/Jul/14  Resolved: 05/Feb/14

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Obsolete Votes: 0
Labels: actions, form, form-refactoring
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

We do not ever commit our forms in a Vaadin way relying on the consistency of JcrNodeAdapter. Though we do validate forms in commit-actions. What we could do is to introduce an interface (advancement to FormValidator) that would actually commit the Vaadin form. This brings us the possibility to play with properties in many ways - creating custom properties, utilizing Transactional properties, deferring access to JCR. Validation would be an initial step of the commiting process.


Generated at Mon Feb 12 08:43:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.