Raj Nerurkar

Greenhorn
+ Follow
since Jul 24, 2004
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 Raj Nerurkar

You asked..
-------------------------------------------------------------------------
Ok, but what about the Price itinerary precondition (user logged in) ? That is not according to the Prepare Itinerary Use Case (user needs to be logged in just before confirming the itinerary).
-------------------------------------------------------------------------

Answer..
If you asssume that Prepare Itinerary ends before Pay for Itinerary begins then then in the Prepare Itinerary use case you just need to check if the user is logged in before you send the user to the ConfirmItinerary Page.

Once the user logs in (if not already) and the system displays the Confirm Itinerary page then the Pay for Itinerary use case begins. On the Confirm Itinerary Page when the user clicks on Confirm, the Pay for Itinerary use case is realized.

Hope this helps.
Hi Ram,
Congrat Ram! 92 is a great score. I wanted to know if you used CMP or BMP?
Regards
Raj
David,

Actually I see the confusion you have. Its a valid confusion when you analyze the use cases and the use case model. However I think we need to make certain logical assumptions based on our experience.

This is what I have assumed.
1. Prepare Itinerary does not include Pay for Itinerary and therefore the Post Condition of Prepare Itinerary now becomes valid with this assumption.

2. Since Prepare Itinerary does not include Pay for Itinerary, the use case model become valid when a direct connection is shown from the customer to the Pay for Itinerary use case since the customer pays for itinerary once it is confirmed which is what I have assumed as the outcome of Prepare Itinerary.


With few such assumptions, everything starts falling in place .
Regards
Raj
In my assumptions I am clearly mentioning that designing such an algorithm is outside the scope of this assignment and that the design will only allow a flight search engine which can be either homegrown or through a 3rd party provider to be pluged-in.
Hello,
I am in a delimma whether to model the BOM using Coarse grained
Entity Beans using BMP and DAO pattern or to model using CMP and
justify performance using the good features available of EJB
containers that comply to EJB 2.0 specification. Some of the
features I would list as a justification to going for CMP are
1. FINDERS_LOAD_BEAN
2. RELATIONSHIP_CACHING
3. INHERENT LAZY LOADING
4. OPTIMISTIC CONCURRENCY coupled with CACHE_BETWEEN_TRANSACTIONS
etc.

However I am concerned that this appraoch will make my solution
container dependent and will need considerable amount of
effort while porting to another container.

If Coarse-grained BMP solution is used then I would like to justify
that solution by listing the following design mechanisms I would
employ.

1. Lazy Loading, i.e do not load all dependent Java Objects that are
hanging out of the Coarse grained entity in ejbLoad() but load it
only when a get<<Dependent>>() method is called.

2. Dirty Marker- Moreover, make a JDBC call to load the dependent
POJOs only if they are marked as Dirty.

What do you guys think? Which approach is more justifiable for the
FBN application?

Regards
Raj
Hello,
I am in a delimma whether to model the BOM using Coarse grained
Entoty Beans using BMP and DAO pattern or to model using CMP and
justify performance using the good features available of EJB
containers that comply to EJB 2.0 specification. Some of the
features I would list as a justification to going for CMP are
1. FINDERS_LOAD_BEAN
2. RELATIONSHIP_CACHING
3. INHERENT LAZY LOADING
4. OPTIMISTIC CONCURRENCY coupled with CACHE_BETWEEN_TRANSACTIONS
etc.

However I am worried that this appraoch will make my solution
depending on the container and will need considerably amount of
effort while porting to another container.

If Coarse-grained BMP solution is used then I would like to justify
that solution by listing the following design mechanisms I would
employ.

1. Lazy Loading, i.e do not load all dependent Java Objects that are
hanging out of the Coarse grained entity in ejbLoad() but load it
only when a get<<Dependent>>() method is called.

2. Dirty Marker- Moreover, make a JDBC call to load the dependent
POJOs only if they are marked as Dirty.

What do you guys think? Which approach is more justifiable for the
FBN application?

Regards
Raj