Re: How should we handle void and null results

2016-01-04 Thread Dan Haywood
>> >> >>>> My sample code is: >> >>>> >> >>>> @Action( >> >>>> domainEvent = CreateDomainEvent.class >> >>>> ) >> >>>> @MemberOrder(name = "deliverers",sequen

Re: How should we handle void and null results

2015-12-23 Thread Dan Haywood
tion") > >>>> BusinessLocation businessLocation, > >>>> final @ParameterLayout(named="Deliverer Id") String > >>>> delivererId, > >>>> final @ParameterLayout(named="First Name") String firstName, >

Re: How should we handle void and null results

2015-12-23 Thread Óscar Bou - GOVERTIS
;>>> final @ParameterLayout(named="Last Name") String lastName, >>>> final @ParameterLayout(named="Last Name 2") >>>> @Parameter(optionality = Optionality.OPTIONAL)String lastName2, >>>> final @ParameterLayout(nam

Re: How should we handle void and null results

2015-12-22 Thread Óscar Bou - GOVERTIS
od [mailto:d...@haywood-associates.co.uk] > Sent: Tuesday, December 22, 2015 6:02 AM > To: users > Subject: Re: How should we handle void and null results > > There was a related discussion a while back [1], revolving around whether the > Wicket viewer should always render the return

Re: How should we handle void and null results

2015-12-22 Thread Dan Haywood
ere, it's christmas :) . > > > > Cesar. > > > > -Original Message- > > From: Dan Haywood [mailto:d...@haywood-associates.co.uk] > > Sent: Tuesday, December 22, 2015 6:02 AM > > To: users > > Subject: Re: How should we handle void and null results >

Re: How should we handle void and null results

2015-12-22 Thread Dan Haywood
nowAsDateTime()); > container.persistIfNotAlready(obj); > return obj.getBusinessLocation(); > } > > If you choose to return the parent of the Person object being deleted, > make sure you get the parent before you Delete the person. Have fun! > > Cesar. > >

Re: How should we handle void and null results

2015-12-22 Thread Dan Haywood
obj.setDelivererId(delivererId); >> obj.setFirstName(firstName); >> obj.setMiddleName(middleName); >> obj.setLastName(lastName); >> obj.setLastName2(lastName2); >> obj.setContactPhone(contactPhone); >> obj.setD

RE: How should we handle void and null results

2015-12-22 Thread Cesar Lugo
ntegration with some BPM tool. Just thinking loud here, it's christmas :) . Cesar. -Original Message- From: Dan Haywood [mailto:d...@haywood-associates.co.uk] Sent: Tuesday, December 22, 2015 6:02 AM To: users Subject: Re: How should we handle void and null results There was a related

RE: How should we handle void and null results

2015-12-21 Thread Cesar Lugo
return obj.getBusinessLocation(); } If you choose to return the parent of the Person object being deleted, make sure you get the parent before you Delete the person. Have fun! Cesar. -Original Message- From: Y.R Tan [mailto:m...@yuritan.nl] Sent: Saturday, December 19, 2015 5:44 A

How should we handle void and null results

2015-12-19 Thread Y.R Tan
Hi everyone, When using a void action, let’s say a remove action, the user is redirected to a page "no results". When clicking the back button in the browser the user sees "Object not found" (since you’ve just deleted this object). Example: public class Person { public void

Re: How should we handle void and null results

2015-12-19 Thread Martin Grigorov
Hi, I'll let the DDD experts suggest proper solution but to me Person#delete() (i.e. a person domain object deletes itself) looks strange. Usually the repository deals with these matters. I'd expect to go back to the listing with the other domain objects from this type after the deletion. Martin