The role of the BusinessObjectBeans, which conform to the javabean
specifications, is to contain the data needed by the JSP pages. So, when a
JSP page is about to construct an html page, it will ask the BOBean to
provide the required data. So, the BOBean are the way the Presentation layer
is communicating with the Business layer, or the model. The Presentation
layer only access the model through the BOBeans.
The BusinessObjects are private classes of the model, which are not intended
to be used by the JSP developer. While BusinessObjectBeans are pretty dumb,
the BusinessObjects host the business logic, or business rules. They know
how to calculate the information which will be stored into BOBeans for the
JSP's.
Any comment on this philosophy is welcomed.
Jean-Pierre
-----Original Message-----
From: Loelkes, Jochen [mailto:[EMAIL PROTECTED]]
Sent: jeudi, 2. novembre 2000 15:23
To: '[EMAIL PROTECTED]'
Subject: RE: UML Diagrams for Struts
Thanks for the UML diagram for Struts.
Is there any further description about the relations / differences between
BusinessObject and BusinessObjectBean.
How do you seperate them, what's in the Object, what in the ObjectBean ?
Maybe an example would be very helpful ...
Many thanks,
Jochen
> -----Original Message-----
> From: Jean-Pierre Schnyder [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, November 02, 2000 9:05 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: UML Diagrams for Struts
>
> Here's a class diagram I draw some days ago. Feel free to criticize it. I
> can provide you with the Visio 2000 file if you want.
>
> Jean-Pierre
>
>
>
> -----Original Message-----
> From: Hines, Bill [mailto:[EMAIL PROTECTED]]
> Sent: mardi, 31. octobre 2000 19:29
> To: '[EMAIL PROTECTED]'
> Subject: UML Diagrams for Struts
>
>
> Does anyone know of or have any UML type diagrams for the struts-type
> model
> 2 core behavior? I'm thinking in terms of sequence diagrams that show the
> general process of a request coming in and finding it's way through the
> servlet, action class, hash table, worker beans, etc.
>
> I'd like to structure our applications this way but I'm not quite ready to
> buy into a whole 'framework' for our apps, having been previously bitten
> by
> efforts like TurboVision, OWL, and the BDE framework from Borland. Plus,
> we
> don't have servlets 2.2 and JSP 1.1 yet, we're still at 2.1 and 1.0
> respectively.
> << File: STRUTS_architecture.pdf >>
