[PJUG Javamail] CRUD for a javabean

[Chris Kessel/Lou Doherty]

Yep, straight JDBC would work.

For me, it depends a bit on the urgency and complexity. If this is urgent
and the POJO is simple, just write JDBC. If the POJO is a little more
complex, say holding references to other POJOs or lists, then I'd really
consider moving to a JPA system (of which Hibernate is the one I know).

Like most tools, Hibernate/JPA mapping has a learning curve. Using Hiberate
for a "quick" mapping isn't going to happen unless you're already familiar
with it. And if the POJO has interesting relationships, like a Map/Set of
associated objects, you'll want to make sure you understand if you want to
lazy-load or eager-load those associations. Both have value depending on the
context of how you're using the POJO.

Chris 

-----Original Message-----
From: javamail-bounces at pjug.org [mailto:javamail-bounces at pjug.org] On Behalf
Of Siraj Podikunju
Sent: Friday, April 24, 2009 12:19 PM
To: Vijay Balakrishnan
Cc: javamail at pjug.org
Subject: Re: [PJUG Javamail] CRUD for a javabean

I may be missing something here but is JDBC not an option?

Vijay Balakrishnan wrote:
> Hi,
>
> I have seen this requirement come up a few times.
>
> There is a POJO Javabean (Entities within a database). Now the 
> business user wants to do CRUD operations on the data in these 
> entities in the DB.This app is hosted on Websphere(JDK 1.4.2).
>
> What is the fastest way to do this in java ?
>
> Is it using MBeans (JMX) or using Grails or whatever else ? I have 
> seen a lot of fancy Ruby On rails stuff -so what is the equivalent
> (fastest) way to this in the Java, J2EE world ?
>
> TIA,
> Vijay

--
Siraj Podikunju
SP Consulting, Inc.
Tel: 360-600-6608
Fax: 360-260-3448
E-Mail: sirajp at spconsult.com

_______________________________________________
Web Site - http://www.pjug.org/
Javamail mailing list
Javamail at pjug.org
http://www.pjug.org/mailman/listinfo/javamail

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4034 (20090424) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com