Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Super unless doing a SOFEA style front-end, which basically gets rid of the Controller part in the above architecture.</p> <p>The front end is entirely contained on the client, which directly invokes REST or SOAP services returning JSON or XML. That seems to solve 100% of the problem with transforming domain objects for display!!!! </p> <p>Perhaps, some suggest, the reason there's no clean solution to the N-tier architecture described above is because it's just plain wrong.</p> <p>Links</p> <ol> <li><a href="http://raibledesigns.com/rd/entry/sofea_also_known_as_soui" rel="nofollow noreferrer">http://raibledesigns.com/rd/entry/sofea_also_known_as_soui</a></li> <li><a href="http://www.theserverside.com/news/thread.tss?thread_id=47213" rel="nofollow noreferrer">http://www.theserverside.com/news/thread.tss?thread_id=47213</a></li> <li><a href="http://wisdomofganesh.blogspot.com/2007/10/life-above-service-tier.html" rel="nofollow noreferrer">http://wisdomofganesh.blogspot.com/2007/10/life-above-service-tier.html</a></li> </ol> <p>My current project uses a somewhat outdated N-tier architecture with Data Transfer Objects. The DTOs are unnecessary because the application is not distributed and never will be. The one benefit (which is not worth it IMO) of using the DTOs is that it forces a clean interface for the business methods - the View components can traverse the object graph on the pseudo-models however they wish - no lazy-initialization exceptions can be thrown.</p> <p>One of the architectural pain-points I see in our architecture is that the business interfaces are two damned complicated. It seems as if we need a meta-business interface to encapsulate all of the little business interfaces. Indeed, this ends up happening where one service ends up calling three other services to do its work.</p> <p>The controllers (in our case, Struts 1.2 Action classes) end up calling any combination of these ultra-fine grained or coarse-grained business components. In most cases, sadly, developers unwittingly or lazily code a variety of what should be business logic in the controller classes. I scream every time I look at one of these three-hundred line Action methods!!!!</p> <p>The SOFEA approach seems to offer a much cleaner approach. AJAX allows even web applications running on browsers to have their front end coded using the proper MVC pattern, which is good for both users (by offering a more dynamic UI) and developers (allowing them to code proper MVC).</p> <p>The UI is completely decoupled from the reusable business logic. Is the GUI thick or thin? It really won't matter -they'll be coded in basically the same way.</p> <p>SOFEA / SOUI is new to me and I've never tried it, but I've been reading about it lately and I thought I'd share my thoughts.</p>
    singulars
    1. This table or related slice is empty.
    1. POWeb architecture: MVC, Lazy initialization, Data transfer Objects, Open Session In View, is there a consensus approach?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USles2
    1. USles2
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think this is the future, but it is hard to integrate on existing projects
      singulars
      1. PO
      1. USEran Medan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload