Path: csiph.com!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: markspace <-@.>
Newsgroups: comp.lang.java.programmer
Subject: Re: Apache JDBC utils
Date: Thu, 03 May 2012 07:51:44 -0700
Organization: A noiseless patient Spider
Lines: 30
Message-ID: <jnu623$ud4$1@dont-email.me>
References: <jnn1pc$33c$1@dont-email.me> <3265763.6.1335834184189.JavaMail.geo-discussion-forums@pbph1> <jnnhmf$kd2$1@dont-email.me> <hzRnr.32$go4.1@newsfe14.iad> <jnp15c$uni$1@dont-email.me> <17910424.2120.1335982613195.JavaMail.geo-discussion-forums@pbcoq1>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 3 May 2012 14:51:48 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="zgW2MA4sFrKxp4jMohs6RQ"; logging-data="31140"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+2Z61HCcnVfj6vkgnXWqIYY/frr4HRYbo="
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
In-Reply-To: <17910424.2120.1335982613195.JavaMail.geo-discussion-forums@pbcoq1>
Cancel-Lock: sha1:XO0rmaqtm8uCCY0sTnJHsH0QnvM=
Xref: csiph.com comp.lang.java.programmer:14185

On 5/2/2012 11:16 AM, Lew wrote:
>
> The "M" in "ORM" stands for "mapping" or "mapper".


I always thought it was "management" but I don't see anything on the web 
to support my recollection, so I guess not.


> Using a
> single 'EntityManager' to handle many things for a long time is
> monolithic, and causes persistence sessions to fill and get slow.
> Funneling everything through a single data-access construct suffers
> from the "God object" complex.


OK, I guess it never occurred to me that someone would do something like 
that.  I'll have to keep an eye out for that little anti-pattern.


> "Non-monolithic" means, for example, a separate data-access class for
> each module that needs access. So your "FooOrder" module will have a
> data-access object with its own 'EntityManager', "BazHistoryMarker"
> will have another, and so on.


This is the way DAOs always naturally decompose for me.  I can't see how 
someone would come up with a different idea.

Thanks for taking the time to describe those terms.