OLD FORUM - Use new one: https://www.CaptainCasa.online/forum

the server log contains many lines about each single request, but we are missing a line which tells what is actually being invoked. If I remember correctly such information was provided in earlier captain releases.

Currently we find one line containing
Code:

queueing new ActionEvent (invoke())

another line contains
Code:

executing ActionEvent (org.eclnt.jsfserver.elements.events.BaseActionEventInvoke)

which is not very helpful.

There are other types of events like rowexecute(0,1) which show that an element in a list has been doubleclicked, and since lists do not occur very often, this allows to identify what was clicked. But for standard button events nothing helpful is shown to identify the function. It would be really helpful if the string behind this event (e.g. #{d.d_123.Bean.method}

were logged as well. Similar output is provided for setting properties in the updateModelValues phase, although it only contains the last element of the access path which in our special case is also not really helpful since it mostly reads #value being a generic component, the complete path is e.g. #{d.d_123.Bean.wonderfulprop.value}, and we would be interested in 'wonderfulprop', also 'Bean', so why not log the whole path.
b.t.w. the same applies to the invoke problem, we also have a generic object here and the path reads #{d.d_123.Bean.coolmethod.clicked}, so the last element would always be "clicked".

regards
Manfred

...completely agree + no problem at all to add this as info message!

Is part of next update.

Thanks + regards! Björn