geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: How to determine in which container code is running?
Date Mon, 31 Dec 2012 16:55:35 GMT
I'm not familiar with this particular way of describing UOW or data mapper, but you might consider
whether they are irrelevant with ee facilities.  The whole purpose of EJBs is to provide declarative
transaction management, which is what UOW usually means.  A tiny bit of googling of data mapper
makes me ask why you wouldn't use jpa.  I haven't read Fowler's books for many years, I thought
his refactoring book was really good, but the design patterns ones seemed to me to be reinventing
the wheel as far as ee goes.

david jencks

On Dec 31, 2012, at 8:18 AM, Markku Saarela wrote:

> My use case is to implement Martin Fowler's Domain Model enterprise design pattern with
Unit Of Work and  Data Mapper.
> This UOW does not work with ThreadLocal in every app server due to thread pooling.
> So only solution to use different UOW storing mechanism in different layers;
> session persistence in web container and pass UOW instance to the EJB container and store
it to TransactionSynchronizationRegistry. Of course standalone Java client could use TrhreadLocal
> In UOW static methods to manipulate current UOW instance (getCurrent(), newCurrent()
etc,) must some how decide which implementation to use.
> Markku
> On 12/31/2012 06:06 PM, David Jencks wrote:
>> On Dec 31, 2012, at 7:57 AM, Markku Saarela wrote:
>>> Hi,
>>> Has Java EE spec any API to determine is code running in EJB or WEB container?
>> no.
>>> Or is there any better way than examine stacktrace?
>> I'm imagining that you have some library or perhaps CDI code that is called from
both a servlet and an ejb?  Why do you care?  Just to figure out why something is working
the way it is, or do you need to take different action depending on what calls this code?
 You could pass appropriate context information to the code in question from the caller.
>> david jencks
>>> Rgds,
>>> Markku

View raw message