>I have looked at it a lot and all it illustrates is MVC and value object
>holders. I didn't even like the cataloging.
>
>I changed it a lot, I added category trees for Duke, where a product can
>have multiple categories, and categories can have multiple categories. It's
>at http://www.alcoawheelaccessories.com for example in production Duke
>example (heavily edited).
>
>But I need a real ecommerce flowchart. For example, which comes first, an
>Invoice or a Shipment in a typical Amazon object model? I would like to see
>an reference implementation of the whole enchilada.
>
I'd like to raise an issue here that has been bothering me. My reading of how
MVC ought to work is that the view and the model should never communicate
directly. Therefore, a JSP, for example, should never communicate directly with
an entity bean. The J2EE patterns in the Blueprints seem to suggest athat in an
MVC structure, a client (JSP, servelt, et al) could communicazte to both a
session bean controller and an entity bean model. I thinkt hat's problematic
from a performance view, as well as breaking my understanding of what MVC is
supposed to do. IF the view talks directly to the model, then you haven't
really accomplished anything by claiming to use a design pattern. YOu still
have the view and model tightly coupled, with the view having to do controler
work. Any comments on this issue? Thanks.
Ken
===========================================================================
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".
