Joshua Davis wrote:
RE: the m:n problem, I imagine the design of the
backing beans and DAOs (and transfer objects, in my
case ;) ) would depend on the UI. When you say m:n,
you mean many-to-many, right? What would be a good
example UI design for managing a m:n relationship?
Well the best option I found so far was to set
the relation in a tabbed pane and use ajax with
a popup window for editing deleting and adding...
with a save in the end...
ajax for refreshing without having to go the roundtrip cycle...
optionally if you can bypass the validation you can do the same without
ajax with a normal refresh of the form
(the ajax helped me not to refresh the entire form just the subpanel)
another option if the program permits it is to set a link to the
relational data from a master view that way you can do the relational
data like you would do normal data...
the third option is to handle the relational data entirely in a popup
reachable from the master form.
