Originally posted by aparna chintalapati:
-I had one session bean for each module. I had one stateful session bean for making reservations.
-I extended the itinerary class to store that information.
-yes, I did.
Originally posted by Ramon Gill:
How about cutting WAF to the bone by showing a single component in the Web tier (for customer), and a single component in the Client tier (for travel agent), and use comments to describe all the classes and patterns they use (i.e. front controller, etc, for customer, MVC, etc for Client). The EJB tier could have more components, such as Session Facades, etc.
These would then be Cade-like.
What do you think?
Originally posted by Yanqu Zhou:
One more question about Rose 2000:
Does it support Composition relationship(The solid diamond) is class diagram? Thanks.
Originally posted by Parag Doshi:
From what I understand, there are atleast 2 choices to connect from the Swing client to the business tier:
1. Swing client connecting to the web tier by making a HTTPRequest (hence the use of URLConnection) to a different controller (possibly SwingController) on the web tier, thereby, using a common web tier.
2. The Swing client acts as a EJB CLient and has a BusinessDelegate (a POJO) which uses a ServiceLocator to connect to the business tier using RMI-IIOP, thereby, bypassing the web tier.
In both the instances the BusinessDelegate either lives on the ejb client tier (for swing) or the web tier (for webapp) and communicates via a SL with the business tier (which could have EJBActions, EJBController, SessionFacades etc etc).
Originally posted by Dhiren Joshi:
Mark how would u control client authentication if there is no controller between the Biz delegate and client .?
Even if u had method level authentication how would u pass your principal?
Please give your suggestions.