Fixed.  My mistake:  I forgot that with deep linking that popup is created
from the different module,
so correct classes were not getting initialized.

Thank you,
Oleg.

On Mon, Aug 1, 2016 at 11:45 AM, Oleg Konovalov <[email protected]> wrote:

> Hi Clint,
>
> No, they are different types (different String's).
>
> The functional difference is that second event (type) is when user clicks
> on a link with UUID token (via deep linking) in his email,
> so it verifies if that UUID is not expired and if valid, brings up same
> popup.
> User fills is his password, and submits - that is event type2.
>
> The first type was straight user changing his password (old, new,
> confirmed - submit).
>
> Any guesses?
>
>
> Thank you,
> Oleg.
>
>
>
>
> On Mon, Aug 1, 2016 at 11:25 AM, Clint M <[email protected]> wrote:
>
>> Should work if you're using the same Event Class. (ChangePasswordEvent)
>> Is ChangePasswordEvent.type1 the same as ChangePasswordEvent.type2 ?
>>
>> On Mon, Aug 1, 2016 at 8:15 AM, Oleg Konovalov <[email protected]> wrote:
>>
>> > Hi,
>> >
>> > I am doing enhancements to existing Robotlegs2 web app.
>> > So my popup dispatches event of type1, which main app listens to,
>> > so on that event Command calls Service, which in calls remote Java
>> service,
>> > which calls DB via Spring JDBC template, and returns me status string
>> > (success or some Error).
>> > Now I am adding a second type - type2, and the rest is similar (except I
>> > pass extra params to Stored Proc 2).
>> >
>> > For some reason I see Event dispatched, but Commend for type2 is NOT
>> > getting executed.
>> > Is there a limitation that I can't do:
>> > moduleCommandMap.mapEvent(ChangePasswordEvent.type1,
>> > ChangePasswordRequestCommand, ChangePasswordEvent);
>> > moduleCommandMap.mapEvent(ChangePasswordEvent.type2,
>> > ChangePasswordRequestCommand, ChangePasswordEvent);
>> >
>> > What else might be missing or wrong?
>> >
>> > I am fairly new to Robotlegs2.
>> > Please help.
>> >
>> > TIA,
>> > Oleg.
>> >
>>
>
>
>
> --
> Thank you,
> Oleg.
>



-- 
Thank you,
Oleg.

Reply via email to