Skip to main content
Springer Nature Link
Log in

Towards Automatic Integration of Persistency Requirements in Enterprise-Systems – The Persistent-to-Persistent Patterns

  • Conference paper
Next Generation Information Technologies and Systems (NGITS 2006)

Part of the book series: Lecture Notes in Computer Science ((LNISA,volume 4032))

  • 485 Accesses

Abstract

Nowadays, implementing the Business-Data layers interaction is assisted by industry tools that provide abstraction on top of concrete database systems, but still requires writing a large amount of annoying bug-infected code. Full automation of the Business-Data layers interaction will provide a great improvement in complex systems development.

We claim that automatic integration of the Business-Data layers requires careful analysis of navigational structures that involve persistency concerns in the Business layer. Therefore, our approach consists of a set of independent Data Access Patterns, each applying to a specific navigational structure. Moreover, the patterns are Business layer transparent, i.e., the Data layer interaction leaves the Business layer intact.

In this paper we introduce two Data Access Patterns termed Persistent-to-Persistent patterns that handle navigational structures between classes that are both marked as persistent. The patterns are notable for their handling of Persistent-to-Persistent interaction, where all data is persistently stored. All patterns are based on a core Proxy Data-Mapper pattern, that is shortly described.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

References

  1. Miller, J., Mukerji, J.: MDA Guide Version 1.0.1. OMG (2003)

    Google Scholar 

  2. Ezzio, D.: Using and Understanding Java Data Objects. Apress (2003)

    Google Scholar 

  3. Russell, C.: JSR 12: JavaTM Data Objects (JDO) Specification. Sun Microsystems, Inc. (2004)

    Google Scholar 

  4. Hapner, M., Shannon, B.: JSR 151: JavaTM 2 Platform, Enterprise Edition 1.4 (J2EE 1.4) Specification. Sun Microsystems, Inc. (2003)

    Google Scholar 

  5. Richard, S.: Java Persistence for Relational Databases. Apress (2003)

    Google Scholar 

  6. Thatten, S.M.: Report on the object-oriented database workshop: Implementation aspects. In: Object-Oriented Programming Systems, Languages and Applications. ACM Press, New York (1987)

    Google Scholar 

  7. Saake, G., Conrad, S., Schmitt, I., Turker, C.: Object oriented database design: What is the difference with relational database design? In: ObjectWorld, Frankfurt (1995)

    Google Scholar 

  8. Joseph, W., Ralph, E., Quince, D.: Connecting business objects to relational databases. In: Proceedings of the 5th Conference on the Pattern Languages of Programs, Monticello-IL-EUA (1998)

    Google Scholar 

  9. Ramanatha, C.: Providing object-oriented access to a relational database. Technical report, Mississippi State University, Department of Computer Science (1995)

    Google Scholar 

  10. Hakimpour, F., Geppert, A.: Resolution of semantic heterogeneity in database schema integration using formal ontologies. Information Technology and Management (2005)

    Google Scholar 

  11. Blaha, M., Premerlani, W.: Object-Oriented Modeling and Design for Database Applications. Prentice-Hall, Englewood Cliffs (1998)

    Google Scholar 

  12. Keller, W.: Mapping object to tables, a pattern language. Technical report, Siemens, Wien, Austria (1998)

    Google Scholar 

  13. Andersson, M.: Extracting an entity relationship schema from a relational database through reverse engineering. In: Proceedings of the13th International Conference on the Entity-Relationship Approach (1994)

    Google Scholar 

  14. Fowler, M.: Patterns of Enterprise Application Architecture. Addison-Wesley, Reading (2003)

    Google Scholar 

  15. Nock, C.: Data Access Patterns: Database Interactions in Object-Oriented Applications. Addison-Wesley, Reading (2003)

    Google Scholar 

  16. Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns, Elements of Reusable Object-Oriented Software. Addison-Wesley, Reading (1994)

    Google Scholar 

  17. Limonad, L.: Automatic generation of data-access layer. Master’s thesis (2006)

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Computer Science Department,  

    Mira Balaban

  2. Information Systems Engineering Department, Ben-Gurion University of the Negev, Beer-Sheva, 84105, ISRAEL

    Lior Limonad

Authors
  1. Mira Balaban
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Lior Limonad
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. IBM Haifa Research Lab, 31905, Mount Carmel, Haifa, Israel

    Opher Etzion

  2. University of Haifa, Haifa, Israel

    Tsvi Kuflik

  3. Information and Software Engineering Department, George Mason University, VA 22030, Fairfax, USA

    Amihai Motro

Rights and permissions

Reprints and permissions

Copyright information

© 2006 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Balaban, M., Limonad, L. (2006). Towards Automatic Integration of Persistency Requirements in Enterprise-Systems – The Persistent-to-Persistent Patterns. In: Etzion, O., Kuflik, T., Motro, A. (eds) Next Generation Information Technologies and Systems. NGITS 2006. Lecture Notes in Computer Science, vol 4032. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11780991_6

Download citation

  • DOI: https://doi.org/10.1007/11780991_6

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-35472-7

  • Online ISBN: 978-3-540-35473-4

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics