简化了企业级软件开发中复杂的对象管理事务； • 克服了 C++ 语言等内存泄漏缺陷； • 减轻软件开发人员的负担。 图 15.2 Java EE 容器 15.3.1 客户端应用容器 • 客户端应用容器（Application Client Container）即是普通 Java SE 的 JVM，管理 和运行客户 JavaBean 组件，与一般的 Java 类没有区别。 • Java EE 规范将客户端应用 中国海洋大学信息学院计算机系 第 204 页 / 共 306 页 15.4. JAVA EE 组件 � 15 � 图 15.3 Java EE 组件 15.4.2 Java EE 组件列表 1. Application Client Component 2. Applet Component 3. Web Component * • Servlet • JSP 4. EJB Component * destroy() { 2 try { 3 cn.close (); 4 } catch (Exception e) { 5 application.Log(”登录处理关闭数据库错误” + e.getMessage()); 6 } 7 } 代码中 application 为 Web 应用的上下文环境对象。 16.4 Servlet 生命周期 16.4.1 Servlet 的运行过程 1.

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add:

0 码力 | 458 页 | 5.91 MB | 1 年前

3

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: application. API's like JMS are not normally rich enough to expose all the extra features that most messaging