Hi,

*I am using the Isis Wicket viewer for a demo application.*

I have a scenario where I wish to create a new object with mandatory
properites, the simpleapp demo shows how to initialise an object via an
action on the repository which is done with one form, then when you access
the new object later on, its via another form, its 'own' bigger form

So its seems to me that all object creation requirest two forms one to
create an object and another to maintain it. This is fine untill the object
has many mandatory properties, all must appear in the create form or you
get an error when the repository tires to persist the new object, so the
creation form starts to become as complex as the maintenance form.

Given that the forms are generated this is not a big problem in terms of
effort to set up, its more the difference in behaviour of a Isis
application to what users are familiar with. Normally this would be the
same form with mandatory fields marked, you'd not be able to submit it to
create a new object without filling in all the mandatory fields.

Si I think I am wanting the repository class to create a transient object,
show that objects maitenance form to the user, and have them save it back
to the repository for persisting. Can this be done?

Perhaps I need to understand object lifecycle better?

Thanks
Steve Cameron

Reply via email to