Hi Brian,
On Thu, 23 Oct 2003 20:51:21 -0400, [EMAIL PROTECTED]
wrote:
> (snipped)
>
>1) A Cache implementation that only provides java object identity ( = )
>within a single transaction boundary. I am not sure how this would work, may
>have to hack around some. Cache might clone the object and
Quoting Shane Mingins <[EMAIL PROTECTED]>:
> ... have been reading Core J2EE Patterns and Patterns of Enterprise
> Application Architecture.
>
btw - if you find those books useful I must highly reccomend _Domain-
Drive_Design_ by Eric Evans. It is another annoying-expensive hardback
design books
Quoting Shane Mingins <[EMAIL PROTECTED]>:
>
> Yes it does :-) And answered more. Thanks. I am currently developing a
> Struts/OJB app and have not yet nutted out the architectural issues/design
> ... have been reading Core J2EE Patterns and Patterns of Enterprise
> Application Architecture.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 11:45 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Design question with Struts
>
> Shane,
>
> In this particular application, yes that is exactly wh
Shane,
In this particular application, yes that is exactly what it does. I don't
need any modifications that span multiple requests in this particular app.
The client application (ie, the web application) isn't allowed to hold onto
"live" domain objects. If need be it can hold onto a transactio
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 10:54 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Design question with Struts
>
> The Command is designed so that any object in the domain model that it
>
I just did an OJB+Struts app.
I have a Command interface (not java interface, layer type interface) top
model object which knows about the persistence mechanism. Individual
commands are *not* dependent upon struts at all, but happen to have
properties populated that match nicely to the FormBea
I would recommend creating a services layer for your business logic.
With this pattern, your Actions would simply call your services. Your services will
contain your business logic. You could still have factories to create the bean's but
rather than keeping that logic in the factory, I would m
Hi,
I am using OJB in a struts Web application. I am trying to separate the
business Logic from the controler.
My question is : is it a good design to make a Factory for each bean and in
the actions call only methods on the factories ?
Regards,
Yassine
--
