> > The first handler will get the form for the query. Then the second one, on > "processing error" (since the form was not filled in), will take the default > form and update the values and send it again. On response from that it > invokes a command, which fails as it did not send in a form, and then when > it gets the form that is filled in and submitted. > > That would be a more realistic sequence of things, and where each step can > be repeated, depending on how the flow goes. Note that there is no URL > building anywhere, just as you never modify URL's when you use a web > browser. You click on links and submit forms. > > > I like this! That really separates the things nicely: the server defines a url structure wherein all the use cases are implemented. The client implements the UI of these use cases agnostic about the actual url structure.
Do I understand correctly that the rel attribute is the name of the usecase? Regards, Mads _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
