WAP/WML Programming for App. Servers

More documents

Recommendations

Info

Server-side Application Architecture15Controller(Servlet)3ViewView(JSPs) View(JSPs) View(JSPs)(JSPs)View(JSP)2Model(Beans)4Use a servlet to dispatchrequests (1) Client request acceptedby the controller servlet (2) Data validated against theModel and updates are made (3) Control is passed to theView (JSP) (4) JSP retrieves the relevantdata from the Model (5) A fully formed response issent back to the clientConference Call: 888-311-9053International 908-228-9011
Back-end connectivity on the serverWAP applications require essential data Stocks, schedules, price, quantity, address…J2EE provides a variety of rich data access mechanisms JDBC – relational databases EJB – databases plus logic Connector API – ERP systems, non-relational databases SilverStream EDCs until Connectors are fully implementedConference Call: 888-311-9053International 908-228-9011
Page 1 and 2: WAP/WML Programming for App. Server
Page 3 and 4: Who is the target audience?Develope
Page 5 and 6: WAP/WMLfor J2EE developersConferenc
Page 7 and 8: WML overviewWelcome to SilverStream
Page 9: J2EE Patternsfor WAP/WMLConference
Page 13 and 14: Identifying the target platformUse
Page 15 and 16: XML/XSLT using JSP Custom tags (1)A
Page 17 and 18: Keeping state for WAP applicationsW
Page 19 and 20: WAP/WML Applicationsin a larger con
Page 21 and 22: PersonalizationPersonalization is K
Page 23 and 24: J2EE provides a solid framework for
Page 25: Inside J2EE Online Seminars - NextN

WAP/WML Programming for App. Servers

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?