Originally posted by Samuel Pessorrusso:
My doubt is if it would be a good approach to mix these two things:
client -> SLSB -> SFSB (for confirming, pricing, etc...)
Originally posted by Samuel Pessorrusso:
client -> SFSB (just to set the selected Flights and Segments into the Shopping Cart)
Santiago Urrizola : La Plata - Argentina<br />SCEA (89%-92%)<br /><a href="http://gpitech.wordpress.com/" target="_blank" rel="nofollow">http://gpitech.wordpress.com/</a>
Why can't you just have
Client -->SLSB (for searching flights, getting price etc) and
Client ---> SFSB(for creating itinerary)
A session bean method acts as a business method of a workflow and I don't see any additional benefit in wrapping it up with SLSB.
Originally posted by Sarbur sar:
------------------------------
If we use the SLSB to manage the shopping cart session bean, then how shoppingcart session bean reference will be maintained in SLSB across multiple method calls such as search flight, price, alternative flight.
Originally posted by Sarbur sar:
-------------------------------
Instead of sending the handle each request, why dont we use the Stateful session bean to hold the reference of ShoppingCartSessionBean. I believe that Petstore uses the SFSB Facade to keep reference shoppingcart session bean.
Don't get me started about those stupid light bulbs. |