Learn some J2EE every week, make a point notes.
Objective: You can use WebSphere to develop J2EE development work.
Come on! Come on! ! Come on! ! !
Figure 3 J2EE Scenario
The three miles must be noted:
1, Tier Integration is The Center of the J2EE Programming Model. The central idea of J2EE programming mode is multi-layer integration.
2, users use Browser way: 1) Browser: Using HTML, HTTP, XML. Possible firewall 2) Web Container: Using JSP, Servelet, XML, JavaMail 3) EJB Container: Using Back-End Enterprise Beans, JMS, JTA, JDBC (OR Connectors) 4) Eis Resources
3, users use STAND-Alone Client way: 1) Stand-alone client Use J2SE HTML HTTP XML to access Web Container, access EJB Container via Web Container 2) Stand-Alone Client can directly access EJB Container; You can also directly access the EIS Resources 3) Stand-Alone Client May Be Written in Another Language. Stand-Alone Client is available in other languages. 4) Consider three types of stand-alone clients can be of three types of Stand-alone Client: ※ EJB client interacting directly with an EJB server EJB client directly with the EJB server interaction ※ Stand-alone Java application clients accessing enterprise information system (EIS Resources Directly (May Using JDBC OR Connectors) Stand-Alone Java Program Client directly accessing the Enterprise Information System (EIS), possible using JDBC and connectors ※ Visual Basic Clients Consuming Dynamic Web Content uses dynamic web content VB client ◎ in The form of XML Data Messages in the form of XML data
Figure 4 Centered on Web
The picture four miles should be noted:
1. Under the structure of Web, there is no EJB Container at this time.
2, browser can use technology and Figure three; but the Web Container uses three less than the picture. JavaMail
3, the web container can access the EIS directly using JDBC, and will also use the connector Connectors to access the EIS three times later.
Figure 5 Model-View-Controller Process
Summary summary:
