将 Oracle Forms 转换为 Apex - 是否值得考虑使用 Apex Forms 迁移工具？
朋友们，
我正在考虑将 Oracle Forms (10g) 应用程序迁移到 APEX (3.2.1)，并寻找使我能够达到在 APEX 中获得 Oracle Form 的“第一版”的选项。
通过阅读此 指南以及此 附录 并转换了几个示例表单（最终在修改 xml 文件以创建应用程序之后！）。转换的结果令人失望。通过在 Apex 中从头开始开发页面，我可以更快地获得更好的结果。
我很欣赏 Apex Forms 迁移工具还处于起步阶段，我正在使用第一个版本，但除了一些伪项目管理功能之外，我很难看到使用它的任何好处。
我错过了什么吗？有人能够使用这个工具获得可接受的结果吗？
提前致谢。
Friends,
I am looking at migrating a Oracle Forms (10g) application to APEX (3.2.1) and looking at options that would enable me to get to a stage where I can obtain a "first cut" of the Oracle Form within APEX.
Having got to grips with the Forms migration tool by reading this guide as well as this appendix and converted a couple of sample forms (eventually after making amendments to the xml file to create the application!). The results of the conversion were disappointing. I could have obtained better results a lot quicker by developing the page from scratch within Apex.
I appreciate that the Apex Forms migration tool is in it's infancy and I am working with the first release but other than some pseudo-project management abilities I am struggling to see any benefits of using it.
Am I missing something? Has anyone been able to use this tool to achieve an acceptable result?
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我没有任何迁移工具的经验，但我参与了一个大型 Forms 到 Apex 迁移项目。自从我们大约两年前开始以来，我们还无法使用迁移工具，所以我们构建了自己的工具。但转换确实很难自动化，除了简单的部分（基本上是屏幕布局和项目）。因此，我们有一种方法来生成第一个剪切的 Apex 页面，其中包含（或多或少）正确布局中的正确项目，但是我们仍然有一项艰巨的工作要做，检查表单触发器和库中的 PL/SQL 片段并找出答案如何处理它们（有些是多余的 Forms 特定代码，有些是我们需要用 Javascript 重写的客户端验证，有些是根本不应该出现在 UI 中的业务逻辑，需要移至包中） 。
我认为迁移工具相对于我们自己所做的主要优点可能是“伪项目管理”，因为它为您提供了需要手动转换的内容列表并跟踪您所做的事情。这对于像我们这样的大型项目来说会带来好处，但对于小型项目来说可能不会那么多。对于小型项目，我倾向于说“让我们回顾一下旧的 Forms 应用程序的功能，重新定义需求并在 Apex 中从头开始构建”。您并不真的希望您的 Apex 应用程序看起来像带有口红的 Forms 应用程序！
I don't have any experience with the migration tool, but I am involved in a large Forms to Apex migration project. Since we started about 2 years ago, the migration tool wasn't available to us and we kind of built our own. But conversion is really quite hard to automate, except for the easy bit which is basically screen layout and items. So we have a method to generate first cut Apex pages with the correct items in (more or less) the correct layout, but then we still have a big job to do inspecting the Forms triggers and libraries for fragments of PL/SQL and figuring out what to do with them (some are redundant Forms-specific code, some are client-side validations that we need to rewrite in Javascript, some are business logic that shouldn't be in the UI at all and need to be moved into packages).
I think the main advantage the migration tool has over what we did ourselves is probably the "pseudo-project management", in that it gives you a list of things that need hand-converting and tracks what you have done. This would pay dividends in a large project like ours, but maybe not so much in small projects. For small projects I'd be inclined to say "let's review what the old Forms app does, redefine the requirements and build from scratch in Apex". You don't really want your Apex apps to look like Forms apps with lipstick on them!