.war 文件中需要包含哪些内容才能部署 Flex 应用程序?

发布于 2024-07-09 08:50:04 字数 508 浏览 7 评论 0原文

我一直在使用 Flex Builder 3 创建 Flex 应用程序,这些应用程序是使用 LiveCycle Data Services 的大型 Flex / Java 项目的一部分。 Flex Builder 创建并部署 .war 文件,这对于开发周期来说很方便,但我不明白 .war 文件必须包含什么才能部署和运行。

通过反复试验,我发现更改 Flex 项目的某些属性(即上下文根)可能会破坏或修复应用程序,并且以某种方式将这些设置放入 .war 文件中。

我需要在 Ant 下实现整个构建过程,更重要的是,我需要了解项目的 Flex 部分依赖于什么。 然而,我还没有找到任何描述 .war 文件必须包含哪些内容才能部署 Flex / Java 应用程序的文档。

例如,Flex Builder 创建一个 web.xml 文件并使用正确的标签填充它。 但如果我添加其他功能,是否需要在 web.xml 中添加其他标签?

有谁知道在哪里可以找到有关 Flex / Java 项目的 .war 文件内容的文档?

I've been using Flex Builder 3 to create Flex applications that are part of larger Flex / Java project using LiveCycle Data Services. Flex Builder creates and deploys the .war file, which is convenient for the development cycle, but I don't understand what the .war file has to contain in order to deploy and run.

I've found through trial and error that changing certain properties of the Flex Project (i.e. the Context Root) can break or fix the application, and somehow those settings make it into the .war file.

I need to get the entire build process implemented under Ant, and more importantly, I need to understand what the Flex part of the project depends on. I haven't been able to find any documentation that describes what a .war file has to include to deploy a Flex / Java application, however.

For example, Flex Builder creates a web.xml file and populates it with the correct tags. but if I add other features do I need additional tags in web.xml?

Does anyone know where I can find documentation on the .war file contents for a Flex / Java project?

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

扫码二维码加入Web技术交流群

发布评论

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

评论(2

濫情▎り 2024-07-16 08:50:04

在此处查看示例应用程序:

http ://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=build_apps_3.html

这些应用程序会让您了解 WAR 中需要做什么。 简而言之,标准 WAR 中有四个重要位置,使用 LCDS 或 Blaze DS 的 WAR 中有一个附加重要位置:

myapp.war/
  WEB-INF/    <-- not accessible via the browser over HTTP
    classes/  <-- compiled classes and configuration files (this is where your .class files and jdbc.properties would go)
    flex/     <-- LCDS XML config files (services-config.xml)
    lib/      <-- web application libraries (.jar files, for LCDS and other tools you might be using)
    web.xml   <-- web application configuration

Flex 应用程序本身可能位于 myapp.war 的根目录中,或者位于您选择的任何子目录中(WEB 除外)信息。

但是,如果您研究示例应用程序并让 Ant 脚本构建与您在此处看到的结构相同的结构,那么您应该不会遇到太多问题。

Check out the sample applications here:

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=build_apps_3.html

Those apps will give you some idea of what needs to go in the WAR. In a nutshell there are four significant locations in a standard WAR and one additional significant location in WAR using LCDS or Blaze DS:

myapp.war/
  WEB-INF/    <-- not accessible via the browser over HTTP
    classes/  <-- compiled classes and configuration files (this is where your .class files and jdbc.properties would go)
    flex/     <-- LCDS XML config files (services-config.xml)
    lib/      <-- web application libraries (.jar files, for LCDS and other tools you might be using)
    web.xml   <-- web application configuration

The Flex application itself will likely sit in the root of myapp.war or in any subdirectory of your choosing except for WEB-INF.

However if you study the sample apps and get your Ant script building the same structure that you see there you shouldn't have too many problems.

黑色毁心梦 2024-07-16 08:50:04

我对 LiveCycle Data Services 一无所知,所以这可能是一个问题。 但是,我有一个与 java 服务器交互的 Flex 应用程序,除了对其他静态内容执行的操作之外,我实际上不需要为 Flex 执行任何特殊操作。

具体来说,我将 Flex 项目属性 ~ Flex Build Path ~ Output 文件夹设置为 java webapp 中的 /flash 文件夹,ant 处理其他所有事情(编译 java 文件、组装类文件、添加 web.xml 以及将文件陷入战争)。

另一种方法,取决于 adobe 如何处理生命周期,是让 ant 只调用 Flex 构建器执行的任何命令来输出战争。

I don't know anything about LiveCycle Data Services, so that may be an issue. However, I have a flex app that interacts with a java server, and I didn't really have to do anything special for flex apart from what you would do for other static content.

Specifically, I have my flex projects properties ~ Flex Build Path ~ Output folder set to the /flash folder within a java webapp, and ant handles everything else (compiling java files, assembling the class files, adding the web.xml, and turning the files into a war).

Another approach, depending on how adobe handles livecycle, would be to have ant just invoke whatever command flex builder goes through to output a war.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文