Hi Erik, Short answer is that we don't really (properly) support this. And we should.
I agree that @NotPersistable is confusing and its not clear what to use; the right solution would be to implement a view model (currently: implement the ViewModel interface), and then - optionally - write a custom ComponentFactory for the Wicket viewer to render the wizard appropriately. But the snag even with the above is that (currently) view models are immutable; they support actions but their properties cannot be edited. I can see the way forward on this; I don't think it's difficult, but it will require a change in core and probably the wicket viewer also. If you want then raise a ticket for this requirement, and sketch how you'd like it to work. Cheers Dan On 6 June 2014 17:40, Erik de Hair <[email protected]> wrote: > Ok, I've found the @NotPersistable annotation but don't know how to use > this. I get an error message saying the object is not persistent. Extended > my entity from AbstractDomainObject later, but that doesn't help. > > Erik > > On 06/06/2014 04:07 PM, Erik de Hair wrote: > > Hi, > > Is it in some way possible to create a wizard like form or open an action > with an action? I tried to return a not yet persisted object from an action > and hoped I could edit some properties and add some elements to collections > of the object before persisting it to the database... > > Thanks, > Erik > > > >
