应用程序客户端和独立客户端之间的区别 [英] Difference between an application client and a stand-alone client

问题描述

根据我所了解的，应用程序客户端在某些应用程序客户端中执行有能力与玻璃鱼谈话。但是，对于注释来说，这似乎存在限制。

1. 有人可以给我举一个例子，说明连接到glassfish应用程序服务器来自两种不同的应用程序类型？

Java EE？ 在任何情况下连接到应用程序服务器都不是那么困难......但它覆盖在不同的文档中。




这些是有关如何从独立Java应用程序访问EJB的说明。





以下是使用应用程序客户端从具有GlassFish v3的Java EE 6 Application Client访问EJB的说明：http://docs.sun.com/app/ docs / doc / 820-7695 / beakt？l = en& a = view



通过从应用程序客户端访问EJB，您可以自动访问更多Java EE服务'比如果你直接使用EJB'。您可以在独立案例中凑齐访问这些服务的一部分，但负担转移到应用程序开发人员/部署人员，使访问工作。





创建一个在短期内，访问EJB的独立应用程序看起来很容易，许多人将投资于该策略。如果他们将客户端应用程序部署到大量机器上，那么与拼凑在一起的服务访问策略相关的负担将成为一种负担。



部署使用应用程序客户端容器也不是免费的。如果您使用的是GlassFish（v2.1，v2.1.1或v3），那么您的应用程序服务器供应商将支持您解决部署问题。

），您还可以利用Java Web Start支持，这可以大大简化客户端应用程序的部署。



As the title suggests, this is in relation to Java EE and Glassfish in particular.

From what i've learned the application client is executed in some application client that has the ability to talk to glassfish. But there seems to be limitations to this regarding annotations.

1. Can someone give me an example of the difference in connecting to a glassfish application server from the two different application types?

2. What is the benefit of the application client approach, and what approach is the most commonly used when developing application clients for Java EE?

解决方案

The code (work you need to do) associated with connecting to the app server in either case is not really all that hard... but it is covered in different docs.

These are the instructions on how to access an EJB from a stand-alone java application.

These are the instructions for using an app client to access an EJB from a Java EE 6 Application Client with GlassFish v3: http://docs.sun.com/app/docs/doc/820-7695/beakt?l=en&a=view

Accessing an EJB from an application client gives you access to more of Java EE services 'automagically' than if you were working with the EJB 'directly'. You can cobble together access to some of these services in the stand-alone case, but the burden shifts onto the application developer/deployer to make that access work.

Creating a stand-alone application that accesses an EJB will seem easy, in the short term, and many folks will invest in that strategy. If they deploy their client application onto a large number of machines, the burden associated with a cobbled together service access strategy can become a burden.

Deploying an application client that uses the application client container is not free either. The advantage is the fact that you have the support of your app server vendor to overcome deployment issues.

If you are using GlassFish (v2.1,v2.1.1 or v3), you can also take advantage of Java Web Start support, which simplifies client application deployment a lot.

这篇关于应用程序客户端和独立客户端之间的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！