> I do plan re-organising of login functionsCorrect. Mostly. Right now, for example, navigating to UMOEditServlet,
> this week, however.
> Access to the object is a totally different matter. Incorrect object
> modification request would throw the exception - and this generates an error
while not being logged in, displays edit form, along with the message, which
is not acceptable - it'll confuse 60% of users. They should get a
error page with a relevant info instead.
> Also, since any object manipulations are performed with controls,You realize that this isn't real control, and will also mess up any
> we can always limit the controls when generate a page. For instance, the
> 'Edit' button isn't shown or disabled if user can't edit the object.
web site testing procedures (or at least will make doing them right much
difficult). I'm not saying this is bad idea - in fact opposite. But it
isn't real solution
to the problem.
Authoright © Total Knowledge: 2001-2008