Rich Veress

Greenhorn
+ Follow
since Dec 26, 2006
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Rich Veress

Folks,
I have a bunch of questions related to my diagrams. Once I have the answers I'm ready to submit within days and will let you know how it goes:

- should I represent domain objects in component diagram? Since these are also TOs, lots of components are dependent on them and I'm afraid the diagram will look like a spider web!!!

- can anyone point me to a SWING MVC documentation for comp/seq diagram. For simplicity, all my sequence diagrams only show a "Presentation" component, and I created a web reference seq diagram, but need a swing one as well (or do I?)

- I grouped my components in the comp diagram in 4 "logical" packages (presentation, business tier, integration tier, and resource tier. I placed the coponents inside these "big" package rectangles. How does this sound? Do you have any other recommendation? I ended up having 40+ components, even without the domain objects

- In component diagram I have "usage" relations, just like Cade does. Can you suggest any good stereotypes I can use? I still have the "uses" stereotype, which is the default, but want to make it more meaningful
- component interfaces (lolipops) are only present in my resource tier. Any suggestions where else can these be used?

thank you!!
R
Ricardo is correct. In addition to this, you save memory by having a single instance of the object intead of having multiple copies for each individual client. Entity beans have their own role...
yes, if you have multiple clients using same data
Jay,
Dan answered the question.

This is just one of the many approaches you may take. In case you don't feel confortable with it you can go with the petstore design. Bottom line is that you have to keep session in business tier somehow.
BTW, there are tons of postings about this on this forum. In my view it's one of the most crucial design decisions for the project...

Hope it helps.

Rich
Ricardo,
There is no contradiction here, if you read carefully my post. Your point is perfectly valid.

thanks,
Rich
Cameron,
To be more concrete, I'm talking here about an architecture where I have 1 SFSB as session facade talking to business services implemented as SLSBs that in turn manage functions, such as login, account management, orders, etc. respectively.
The SFSB Session Facade holds the session data and passes it on to the SLSBs, which in turn operate of entity beans. It is a general architecture, and in certain cases, such as logon management, these slsb-s are acting on a single entity bean.
Do you still think it's a bad idea?

Ricardo,
Just to make it clear, in my design all ejb-s except session facade are local...

thanks,
/R
[ December 28, 2006: Message edited by: Rich Veress ]
Hello Ranchers,
How does it sound wrapping entity beans such as Customer with stateless session beans to return TOs to session facade?

thanks in advance.
Rich
Anirudh,
Congratulations, great result indeed!
In BDM how should I draw the dependencies between the Controller class and say Customer composite, for instance? Technically the controller would be dependent on all subcomponents of Customer composite!

thanks,
/R