Hi All, I'm working with Dharmesh and I thought I'd take a step back and ask a more general question.
First some background: we want to use domain driven design to create a set of entities and services that can be used by multiple applicaitons through the Restful Object interface. The problem is our requirements are all in screen flows that are using an inductive user interface style: http://msdn.microsoft.com/en-us/library/ms997506.aspx That is to say, it has a process based object that fills in the details for domain objects through a set of wizard like screens. For example, imagine you have a car insurance app. The domain object is a customer who has a vehicle, a bank account and an address history. There may also be a second driver. The UI screens first captures the customer detail and asks if there is a second driver. If there is, the next screen is the second driver details, otherwise it's the vehicle details. Then the address history one address at a time and finally the bank account. In the documentation it talks about creating "wizard-like process objects" that aggregate some state with respect to a certain process: http://isis.apache.org/applib-guide/how-tos/how-to-07-040-How-to-specify-that-an-object-should-not-be-persisted.html. I believe that is what we are trying to create. Now we are using Isis to prototype the system. We want to rapidly prototype the screens and then factor out the domain model. In the final application there will be a separate presentation layer with JSF forms that then call the Restful Objects services, but we want to avoid that work in the prototype. Has anybody prototyped this style of interface before? Do you have any advice to offer? As you can see from Dharmesh's post, our current approach is one object per form. Is that the right way to go about it? Anything you can share with us would be greatly appreciated. Regards, Ged On 2 January 2014 16:54, Chohan, Dharmesh <[email protected]> wrote: > Hi > > > > I have 2 domain objects objectA and object. I can persist objectA and > from objectA screen the control is returned to objectB domain screen. > > > > On objectB form, the screen displays the domain properties. However the > screen also displays the title/header as “General” and a “Edit” button. > > > > I have 2 issues. One is after editing the form of objectB, the form is not > persisted. The other thing is I want to replace the title of “General” and > the “Ok” button on the screen to some defined values. > > > > Please can anyone provide guidance on these issues. > > > > Thanks in advance. > > Dharmesh > > >
