|Persistent Java Class Data Base Storage? [message #382769]
||Tue, 21 October 2008 19:19
| Jim Crowell
Registered: July 2009
I am developing a Java Stand-Alone Form Centric Application kernel. The |
system provides a framework for the Application end user to perform data
entry into multiple forms and to create reports as a function of the
entered data. Each form is a Java Class. Currently, the kernel writes a
delimited String of each forms parameters to an individual HDD flat file
when the end user selects the save button or request a different form to
Ideally, I should change the kernel to write the Class object to a
persistent Data Base. I want the form Class to be updated in the DB each
time my End User enters a form field. I plan to change the save button to
a revert button so that the end user can reinstate the form to the load
state if desired.
Presently i am using Java 1.4.2, Swing and Eclipse 3.1.2 on a Windows XP
Pro sp2 PC.
I have selected the Apache Derby DB because it can be embedded nicely into
my Java Stand-alone App. Initially, I thought this would be a simple
transformation but to meet my data persistence requirement I realized that
is not the case.
I did considerable reading on Java Data Persistence on the web getting
introduced to Object-Relational Mapping (ORM), Java Data Objects (JDO),
Java Persistence API (JPA) and eventually your Eclipse Persistence
Services Project (EclipseLink).
As part of this analysis, I read about the Hibernate product and it's
integration with Apache Derby. I found a very good article on this
integration but it used NetBeans as the IDE and that turned me off. I then
Googled something like "JPA and Eclipse" and discovered EclipseLink.
All of the above methodologies seemed to meet my requirements in some way
but some may be overkill for my implementation. My quandary is what
technology should I pursue to meet the above objectives? Will EclipseLink
implementing JPA solve my problem and can I continue to use Apache Derby
as my DB? Or is there yet another methodology I should evaluate to solve
Also [perhaps not a question for this forum! If so, please ignore]
Before I realized I needed Class data persistence I was going to make a
Derby Table for each form. Each table column would be assigned to a form
Class parameter similar to my current delimited String flat file approach.
Now I believe my best approach would be to have the DB emulate a Java
TreeMap class where each key is the unique form name and each value is the
associated Class object. Is this concept true and can I implement it using
EclipseLink and the Apache derby DB?
Powered by FUDForum
. Page generated in 0.04625 seconds