I am implementing the Flight Search Service using the Value List Handler pattern. I have a FlightIteratorEJB as a Stateful Session Bean and this EJB uses a DAO to search for flights. The reason of using SFSB as the Value List Handler is that the SFSB can cache the search results for each client and help in pagination.
But since we have several users that would perform searching for flights, I am debating if creating a SFSB for each client would be a good idea.
Anyone implemented the flight search as a SFSB? How would you justify this design to be scalable?
Any other design ideas on this would be helpful. Thanks.
one more question-> For swing clients, where could the handle to the SFSB be stored. can it be in the Buisness Delegate in some static variable?
The handle will be stored in the sfsb, then convert the handle in a string, encapsule it and pass this string to client. so if the client have to use again (indirectly) the handle it will pass back that string to the sfsb.
it's more simple to design it than explain
GiUsEpPe (SCJP, SCWCD, SCBCD, IBM OOAD, SCEA/OCMJEA 5)
We're pleased to have you here with us here on the ranch, but there are a few rules that need to be followed. One, as John has mentioned, is that proper names are required. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.
In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious. Initials are OK for the first and middle names but not the last. You can change it here
I didn't use the SFSB in my project. I chose a architecture that divided the "control" task between the type of clients. I preferred to remove the load of session user control in application server and swing client machines.
Andrew Thomas Betencourt<br />SCJP, SCJA, SCWCD, SCBCD, SCEA 2<br />Fujitsu Brazil
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop