使用 Java Web Start 远程部署项目
我正在尝试使用 Java Web Start 远程部署项目。这里它适用于单个 jar 文件。谁能告诉我如何为多个 jar 文件部署它,并且因为我使用的是 SQLite DB,它使用 sqlite-jni.dll
在 Windows 上执行?我需要将此文件包含在 JNLP 中。
任何形式的帮助将不胜感激。
提前致谢。
I am trying to deploy a project remotely using Java web start. Here it is working for a single jar file. Can anyone tell me how to deploy this for multiple jar files and as I am using SQLite DB which uses sqlite-jni.dll
for its execution on windows? I need to include this file to in the JNLP.
Any kind of help will be appreciated.
Thanks in advance.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
将本机放在签名 Jar 文件的根目录中,并将其添加到 JNLP 中的
nativelib
元素中。由于它是一个 DLL,因此请确保将其添加到 Windows 特定的resources
部分。有 Mac 版的原生软件吗?和*尼克斯?
EG
在此示例中,所有资源应位于
http://our.com/lib/
中。本机(在本例中为 DLL)应始终位于 Jar 文件的根目录中。
我还提供 JaNeLA 来检查 JNLP 文件和 JNLP 文件的有效性。对基于 JWS 的启动的许多其他方面执行健全性检查。
Put the native in the root of a signed Jar file and add it to a
nativelib
element in the JNLP. Since it is a DLL, make sure you add it to a Windows specificresources
section.Do you have natives for Mac. and *nix?
E.G.
In this example, all resources should be located in
http://our.com/lib/
.The native (in this case a DLL) should always be in the root of the Jar file.
I also offer JaNeLA which checks the validaty of JNLP files & performs sanity checks on many other aspects of JWS based launches.
在我们的例子中,我们在 jnlp 文件中指定了所需的所有文件(jar 和 zip)。我们使用了 .dll,但它们是与系统上已安装的程序一起打包的。我们通过我们的程序与该程序进行交互。我们所需要的只是确保在 Windows 路径变量中指定了 .dll 的路径。
在打包方面,我们将所有 jar 打包到 .war 文件中,然后将该 .war 放入 .ear 文件中(不是必需的,但我们这样做了)并将其部署到我们的应用程序服务器。当我们更新 war 中的 jar 版本时,我们还更新了 .jnlp 文件(以及我们使用的某些 version.xml 文件)中的 jar 版本号并重新部署。然后,当客户端启动时,他们会检查新的 .jnlp 文件并下载正确的 jar。
有帮助吗?我正确理解你的问题吗?
In our case, we specify all the files needed (jar and zip wise) in our jnlp file. We have used .dll's but they were packaged with a program that was already installed on the system. We interacted with this program via ours. All we needed was to make sure the path to the .dll's was specified in the Windows path variable.
In terms of packaging, we packaged all our jars into a .war file and then put that .war into an .ear file (not necessary, but we did) and deployed that to our application server. When we updated the jar versions in our war, we also updated the jar version numbers in our .jnlp file (as well as in some version.xml file we use) and redeploy it all. Then when the client's fire up, they check against the new .jnlp file and download the right jars.
Is that helpful? Did I understand your question correctly?