Logged In: YES
user_id=1118698

it seems that mavnet fill class' all public properties which
match incoming http parameters (input field (expanded) ->
frmUserAdd:adduser:txtUserName; class property name ->
TxtUserName).

we have done a patch to standard edition of mavnet to do 2
things:
1) all incoming http parameters to extract last occourance of
`:' symbol -> therefore action handler will get `txtUserName'
parameter instead of `frmUserAdd:adduser:txtUserName'.
2) we have also ceated mapping mechanism like ->
`frmUserAdd:adduser:txtUserName' parameter maps really to
`TxtUserName' property (something like action handler http
parameter population).

is it clear ?