Vishwa Bandhu

Greenhorn
+ Follow
since Jul 05, 2005
Merit badge: grant badges
For More
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 Vishwa Bandhu

Thanks very body.

I had about 15 classes and I showed all the business functionalities, including external interfaces as interfaces, that helped me to make the class diagram technology neutral.

1. Did you show the different JSPs in the Component diagram?

I showed a generic ui element and listed the individual jsps in the uml note attached

2. How did you show the link between the use cases in the sequence diagram? Like after prepare Itinerary is being called and the navigation goes to the Price Itinerary.

I showed any refernced use case as an Acton in the SD

3. TransMaster integration - would you be able to shed some lights on this?

I don't know how much we can discuss about specific's in this form. But I can tell to that I wouldn't go deep into the detailed implementation of any external interface. I will simply have the component developer deal with the details of the implementation. As an architect and designer of the system, just say what interface is required and what protocol to follow.

Wish you all good luck.
George,

I agree with you. I am almost ready to submit myne and I use the strategy for VLH. But again I do have the same confusion from the Core Design PAtterns.

I plan to save the VLH for the web users in the SFS but for the remote clients, the VLH is sent via serialization and as remote clients hanlde their session by themselves. My thinking is the size of this VLH won't be huge as these are returning flight search result for a small airline(limited no of flights)

I don't think at the architecture and design level we need to be specific how each method is implemented, meaning we don't have to specify how the search results are presented for connecting from city to city. What do you think?
When you say "an actual user or system as an actor...", think of the use case as a (Sub) System...

Makes sense?
Jose,
What do you mean by the following?
"In petstore actions are used to change the state of model or user's session but not to search. In this case action only return a Integer to the front controller in order to decide the next screen."

Each action in petstore returns a Response and the response can be any serializable java object? The response object is set in the request attribute and the can be used to display result to the user.

So I don't see any reason why one cannot use this for search results. In fact if you use the VLH and get results page by page also, I think it will be passed through the EventResponse. But you can use a ViewHelper Tag libraries to connect to the Business tier and then get the results too...
You can use a Actor to show the other use case and send a message to that actor indicating the execution of that use case
Congratulations!
Can we use interfaces in class diagram to capture the business service, to keep the class diagram platform independent? These are shown as Stateless session beans on the Component diagram.
What do you think about this aproach?

Thank you.
A swing application makes use of JFrames to implement User Interface Windows. So each web page can be thought of as a Frame. The Frame has controlls like buttons etc, which generate events (AWT events) There are event listeners that need to be implemented to handle the event.

I haven't seen a real MVC architecture refering the Swing implementation, like the petstore example. However I would seperate the view from the controll by having a control listen to the events from the GUI and the controll delegate to a custom Action to handle the event. The action can use a BD to connect to the Business Tier which can again use a SL etc...
To me Petstore is not the best solution to a problem but it only demonstrates J2EE capabilities (architectural possibilities?) with whatever design patterns at hand. Not necessary that the used pattern is required. It talks all about session facade and then exposes the customer entity bean through shoppincart statefull session bean. Their excuse is they all use local interfaces. While for a small application this is an overkill to use so many session facades and statefull session beans, for a large application this strong coupling between servlet container and the ejb container won't be a nice thing. But when you seperate them, then you deal with remote interfaces or end up redesining your application.
Together Architect is a very good tool, It comes with a 14 day licence for trial though.
I think, in a Java client connecting directly to the EJB, the Business delegate handles all the connections and the business tier details. This can very well do a client side caching as Java client can have the session handling locally. In this case Java client connects to a EJB through a Stateless session facade implementing remote interface.

For the web user, if you use plan to share JVM for the servlet container and the EJB container, same server, then the Servlet client can have a seperate BD that connects to the EJB via a statefull session bean,( session stored in the business tier). Clearly the BD for this scenario cannot be the same.

On the otherhand, if the client talks to the Business tier via a servlet front controller, then I don't see why one would need a seperate BD for two interfaces. I would rather use a HTTP proxy at the client tier and the BD would be the same for both the web client and the java client at the web tier.
I think the whole idea of VLH to use SFSB is that, VLH maintains the Value list and its state. So it makes sense to make use of SFSB. But when I looked at the PetStore example, they are using many SFSB, which I believe, is an overkill. If you already have a SFSB, I would use a serializable POJO for VLH and then cache the VLH in the existing SFSB, instead of making VLH itself a statefull session bean.
Congratulations!

I like your thoughts on the Segment - Flight. How did you represent the one way or two way?
My thought was from source to destination it is one segment and so a round trip itinerary has two segments, otherwise it is just one segment. But each segment can have one or many flights.

Also did you consider customer buying many tickets in a single itinerary? In such cases how to map the frequent flyer mile? Is it per customer or per passenger?

Thank you so much