Jay Walters wrote:
> <snip>
> In the petstore 1.1.2 they use the AccountModel class within their Account
> entity bean to hold the state and they also send it out to the webtier.
> After closer inspection they appear to not use Facade at all. They use
> something they call MVC where the client (object within webtier) asks the
> controller (session bean) for the entity bean and then the client
> interrogates the entity bean for it's contents - the AccountModel object for
> example.
>
> So they are still strongly coupled client tier to data tier.
That is one big problem with the MVC architecture. I prefer to keep each MVC set
confined to one tier. Extend it across tiers only when there are minimal effects
of changes to the model in other tiers. Of course, there is always some effect
to changes in the model. The point is to keep the ripple effects to a minimum.
>
>
> What is the story with the pet store application people? Do they read the
> Java Center patterns at all? I am a bit confused about the Sun vision for
> building J2EE applications.
>
> Comments?
Good questions. I think they're still working it out :) But like all design,
there are compromises. Everyone has to decide when using a particular pattern
whether the compromises are acceptable in the given application.
>
>
> Cheers
> Jay
Happy coding,
--Victor
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
