This is a textual representation of a lightning talk done on Feb 26th at Code4Lib 2008. When the video of the talk is up (thanks, Noel!) I’ll link it here, too. The video is now available, and that article includes an update on progress since the this article was posted.
I’ve been working to get JBoss Seam tied into Fedora, and along the way thought it would be wise to stop and document a core concept of this integration: the centrality of Fedora Disseminators in the the design of the Ohio Digital Resource Commons. Although there is nothing specific to JBoss Seam (a Java Enterprise Edition application framework) in these concepts, making an object “render itself” does make the Seam-based interface application easier to code and understand. A disseminator-centric architecture also allows us to put our code investment where it matters the most — in the repository framework — and exploit that investment in many places. So what does it mean to have a disseminator-centric architecture and have objects “render themselves”?
Also tagged asset actions, digital libraries, DRC, Fedora, java, seam
![[Creative Commons Logo]](http://i.creativecommons.org/l/by-nc-sa/3.0/us/88x31.png){kind=small}
This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/us/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.
Google Book Search Settlement: Introduction, Public Announcements:
Google Book Search Settlement: Reviewing the Notice of Settlement:
Google Book Search Settlement: Public Access Service:
Preliminary Court Approval of Google Book Settlement; Final Approval Hearing Set:
Is OCLC's Change of WorldCat Record Use/Transfer Policy Related to the Google Book Search Agreement?: