Annick BOEL

+ Follow
since Feb 09, 2004
Merit badge: grant badges
For More
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Annick BOEL

Sorry, no answer by still other questions concerning the same topic.
1/ What's your feeling about the need to return to the database or not for each page, or to get the entire resultset in one pass and to scroll to list only?
2/ What will be the kind of objects returned? In Petstore the objects returned are of type Page that are whether Category or Product or Item. In our case it won't be only flights but rather more complex objects, ie sequence of connecting flights from one city to another.
3/ How could the list be presented in the case of a round-trip and the necessity to display both outbound and return FlightSequence objects. How does'it it impact the design?
4/ Is there neccessity to deal with the relationship between city and the many airports that can serve a city, or should it be considered as something hidden by the searching mechanism used, ie the SQL request that will be performed by the DAO, which we don't have to deal with either.
5/ Transactional requirements for this search? In Petstore transcation attribute is required!!!
I'm scratching my head about those 5 points. What's your feeling?

If the FastLaneReader is a DAO accessed by a EJB, does it make sense to use a stateful EJB to save the list?
Congratulations Srikanth!
Did you follow the petstore approach to use local interfaces to communicate between the web tier and the EJB tier.
Thank you very much for your answer.

When I spoke of java client as a web client, I was thinking of a java client connecting the web tier and not the EJB tier. Does it make sense?

I try to understand all the information you gave me and will come later.
I have decided to support both a browser client for customers and a Java Swing application for travel agent and to put the business logic in the EJB tier.
Can anyone tell me how it is possible to support the 2 kind of clients. The browser client will obviously connect to the web tier but should the Java client be a web client too or should it connect to the EJB tier directly.

I have heard of designing one FrontController per client type. But in which layer is the FrontController supposed to be (web tier or EJB tier).
What is the relationship betwenn FrontController and BusinessDelegate?

1/ What about the fact the a customer could choose the round-trip option when changing a segment? I didn't see any comment about this? Have you seen a travel site where you can change only the departure or the return?

2/ I completely agree with the concept of logical flight, which means for me either the departure combination of segments or the return one, because it ensures a consitency of segments.

Any comments?

Hi, I'm back!

Thank you for your answers, but it's still not clear in my head, what the best choice is.
Could all of you argue a little more.

Hi all,

The Change Itinerary UC says :
"Customer selects the segment to change. In order to change, the segment is deleted and the Prepare Itinerary Use Case is executed"

Once more, it's important to clearly understand what a segment is really, because if we don't capture this concept the right way, the Use Case will be badly realized!.

- Option 1 :
I can consider without any risk on this assumption that an itinerary (either one-way or round-trip) has an outbound part and may be an inbound part too.

It makes also sense to think that a traveller would like to change either the departure or the return part of the itinerary or may be both!
But does it make sense that a traveller would like to change a simple part of his departure or a simple part of his return??? I don't think so.

So the granularity of this change would be :
Either departure or return, but not a piece of the departure, or a piece of the return.

So the concept of segments would mean either departure or return!
So the multiplicity of the BDOM would be irrelevant
BUT this way of thinking would be VERY consistent with the Prepare itineary use case.

-Option 2 :
If we consider that a segment is very fined-grained, for example on the outbound way A-B-C and change the AB segment.
How can we change AB without changing BC to, because of course BC would no more be consistent? For example:
Before change :
Take off A at 7, Land at B a 8. Take off at B at 9 ,Land at C at 10.
After Change of AB only :
Take off A a 9, Land at B at 10. Of course I won't be able any more to take off from B at 9.
So segments are inconsistent.

Any comments, about the granularity of a segment and the consistency of the segments after a change?

Did any one encountered difficulties with the concept of itinerary itself, according to the fact that an itinerary may have an outbound part and an inbound part if it is a round-trip?
Do we have only one itinerary, even if it is a round trip?

If we have only one itinerary even for a round trip, how is it possible to manage info about the outbound part and the inbound part?
Any comment?

Hi all,

I am Annick, started preparing for SCEA part II.
I have already read many interesting things on this forum and will soon for sure ask some questions to all of you.