Java Web企业应用程序“客户端”

发布于 2024-11-11 04:37:02 字数 1049 浏览 3 评论 0原文

在我目前的工作中，我们正在重新设计整个核心应用程序，基本上是 springMVC、ejb3、SpringF、AJAX等等。

我们的客户大约有 60 岁，根据所获得的许可证使用相同的应用程序。

我们正在考虑开发一个可以简单地安装在本地的应用程序。

类似于：setup.exe，它将安装应用程序服务器、安装 EAR 并使用轻量级数据库，例如 Derby。

我有几个问题：

你做过类似的事情吗？你的应用程序运行得怎么样？
您使用哪个应用程序服务器？
您是如何编写自动更新服务的代码的？
还有许可证？

此外，我们还计划通过相同的应用程序客户端提供“模块”，该客户端将有一些 JSP 和 Web 服务消费者。例如：

当获取传输模块时，Web 服务将提供如下内容：

<module>
  <name>Transfer</name>
  <parameters>
    <parameter type="text">Name</parameter>
    <parameter type="number">account</parameter>
    <parameter type="currency">DO</parameter>
    <parameter type="number">To Account</parameter>
    <parameter type="text">Description</parameter>
  </parameters>
</module>

首先将呈现动态 JSP 页面，并基于该页面进行验证，然后发送到 Web 服务。

这看起来是一份不错的工作吗？或者给你练习？

原文

At my current work, we are redesigning the entire core application which is basically springMVC, ejb3, SpringF, AJAX, etc.

Our clients are like 60, that uses the same application depending on the acquired license.

We are thinking to develop an application that can be simply installed locally on their places.

Something like: setup.exe which will install the Application Server, install the EAR and use a light weight database, something like Derby.

I have few questions:

Have you done something like that? how is your app working?
Which application server did you use?
How did you coded the auto update service?
And Licenses?

Also we are planning to provide "modules" via the same application client, that will have some JSP and WebServices consumer. For example:

When acquired the Transfer Module, the webservice will provide something like:

<module>
  <name>Transfer</name>
  <parameters>
    <parameter type="text">Name</parameter>
    <parameter type="number">account</parameter>
    <parameter type="currency">DO</parameter>
    <parameter type="number">To Account</parameter>
    <parameter type="text">Description</parameter>
  </parameters>
</module>

That will render, first a dynamic JSP page, and base on that validated and then sent to a webservice.

That looks like a good job? or practice for you?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

沙沙粒小 2024-11-18 04:37:02

我能想到很多不这样做的理由。但我相信你已经分析了你的需求并提出了这样的需求。

有几个问题：

你做过类似的事情吗？
没有
您的应用运行如何？
```
 我们确实有类似的东西，但不是在每个客户端计算机上
```
首先是因为系统硬件要求，但它更像是客户端服务器。就像带有服务器与主银行服务器通信的 ATM 机一样。
您使用哪个应用程序服务器？
- 最好是 JBOSS 应用服务器或轻配置的 Tomcat。
  您是如何编写自动更新服务的代码的？
在服务器启动时，您始终可以下载 jar 并将其复制到需要的地方。
还有许可证？
多种策略，包括下载预建的耳朵或特定的许可证密钥。

I can think of so many reasons to not to do this. But I am sure you have analyzed your requirements and have come up with such a need.

have few questions:

Have you done something like that?
NO
how is your app working?
```
     We did have something similar, but not on an per client machine
```
basis because of system hardware requirements in the first place but it was more like a client server. Like an ATM machine with a server to talk to the main banking server.
Which application server did you use?
- Preferably JBOSS application server or Tomcat with light configuration.
  How did you coded the auto update service?
On server startup you could always download the jar and copy it to a place if needed.
And Licenses?
Several strategies including downloading pre-built ears or specific license keys.