Nalazite se na CroRIS probnoj okolini. Ovdje evidentirani podaci neće biti pohranjeni u Informacijskom sustavu znanosti RH. Ako je ovo greška, CroRIS produkcijskoj okolini moguće je pristupi putem poveznice www.croris.hr
izvor podataka: crosbi !

Dynamic Data Access Object Design Pattern (CROSBI ID 598243)

Prilog sa skupa u zborniku | izvorni znanstveni rad | međunarodna recenzija

Roško, Zdravko ; Konecki, Mario Dynamic Data Access Object Design Pattern // Proceedings of the 19th Central European Conference on Information and Intelligent Systems / Auerer, Boris ; Bača, Miroslav (ur.). Varaždin: Fakultet organizacije i informatike Sveučilišta u Zagrebu, 2008. str. 615-620

Podaci o odgovornosti

Roško, Zdravko ; Konecki, Mario

engleski

Dynamic Data Access Object Design Pattern

Business logic application layer accessing data from any data source (databases, web services, legacy systems, flat files, ERPs, EJBs, CORBA services, and so forth) uses the Dynamic Data Access Object which implements the Strategy[1] design pattern and hides most of the complexity away from an application programmer by encapsulating its dynamic behavior in the base data access class. By using the data source meta data, it automates most of the functionality it handles within the application. Application programmer needs only to implement specific „finder“ functions, while other functions such as „create, store, remove, find, removeAll, storeAll, createAll, findAll“ are implemented by the Dynamic Data Access Object base class for a specific data source type.. Currently there are many Object Relational Mapping products such as Hibernate, iBatis, EJB CMP containers, TopLink, which are used to bridge objects and relational database. Most of the time this approach (Object Relational Mapping) makes one more unnecessary layer of the complexity. Dynamic Data Access Object helps application programmers to avoid the usage of the Object Relational Mapping when there is no benefit of using it. Dynamic Data Access Object is an implementation of „pass through“ instead of Object Relational Mapping application behavior at the data access layer.

Strategy; Data Access Object; Sovereign Value Object; EJB; Value List Handler; Result Set; Object Relational Mapping; Caching; Meta Data; Transaction; Connection; Business Object; Facade

nije evidentirano

nije evidentirano

nije evidentirano

nije evidentirano

nije evidentirano

nije evidentirano

Podaci o prilogu

615-620.

2008.

objavljeno

Podaci o matičnoj publikaciji

Proceedings of the 19th Central European Conference on Information and Intelligent Systems

Auerer, Boris ; Bača, Miroslav

Varaždin: Fakultet organizacije i informatike Sveučilišta u Zagrebu

Podaci o skupu

Central European Conference on Information and Intelligent Systems

predavanje

24.09.2008-26.09.2008

Varaždin, Hrvatska

Povezanost rada

Informacijske i komunikacijske znanosti

Poveznice