Any thoughts about these two questions? I somewhat disagree with the answers.
30Baby Bell is a new local Telephony provider in Chicago, IL. It has a legacy application for the B2B transactions with Verizon, the Incumbent Local
Exchange Carrier (ILEC.) Baby Bell frequently purchases blocks of Telephone numbers from the ILEC using a CORBA RPC call. There numbers are then assigned to the customers in sequence. Sometimes customers request vanity numbers, in which case, a custom synchronous query is made on the ILEC's operational support system, to check for number's availability.
If Baby Bell were to rewrite its existing legacy code using newer
J2EE technology, what technology would you choose so that both the block purchase and the individual query might be accommodated?
AJava
Applet technology for the CORBA call and custom socket programming for vanity number requests.
BJava
Servlet API for the CORBA call and
JSP for the custom socket programming
CEntity EJBs for both
DSession EJBs for both
EJNDI for both
FMQ Series with a JMS based solution for both
31Julia Fractals Inc. is building a J2EE based application for Order Entry and management of their fractal software. Once the order is taken, it is submitted to a relational database. A provisioning system then queries data and makes appropriate calls to various subsystems using JMS on MQ Series. What design
pattern is JMS an example of here?
AObserver
BMediator
CAdapter
DBridge
EVisitor
