Re: Issues with beaneditform component

2014-11-27 Thread Thiago H de Paula Figueiredo
On Wed, 26 Nov 2014 23:44:58 -0200, Name Surname wrote: @CommitAfter public String OnSuccess() { logic.editUser(user); return "ListClassesPage"; } I'm not sure it matters, but try onSuccess(), without capitalizing the first letter. Now after I press Save, it

RE: Issues with beaneditform component

2014-11-27 Thread Name Surname
Nope. Implementation is fair OK to me. Checked console and there is nothing and I mean nothing on screen when I press Submit. It's like I didn't press anything??? > Date: Thu, 27 Nov 2014 22:48:14 +1100 > Subject: RE: Issues with beaneditform component > From: ch...@openc

RE: Issues with beaneditform component

2014-11-27 Thread Chris Mylonas
Dunno - I use the param user in onActivate instead of setData. Also just int. During @setupRender stage, fetch from logic the orig. At save time, my logic sets it all from form object. Make sense?

RE: Issues with beaneditform component

2014-11-26 Thread Name Surname
Hello Chris! Well the thing is I used @persist just for that purpose, to save me from using the stale user object. There is some other issue around here which at this stage I can't figure out. :/ > Date: Thu, 27 Nov 2014 13:04:56 +1100 > Subject: Re: Issues with beaneditform compo

Re: Issues with beaneditform component

2014-11-26 Thread Chris Mylonas
On permission page I dont think u need @persist, you are setting the user already. The reason: I think its because when it goes to save it is using the stale user object discarding the form submission changes. On 27/11/2014 12:45 pm, "Name Surname" wrote: > I have one very odd situation here and

Issues with beaneditform component

2014-11-26 Thread Name Surname
I have one very odd situation here and it regards beaneditform. I have implemented following code: public class ListUsers { @Inject private Logic logic; @InjectPage private PermissionsPage permissionsPage; @Property private User user; /**