Oracle ADF 组件体验
我刚刚看到有关 Oracle ADF Rich 组件的精彩小演示：http://download .oracle.com/otn_hosted_doc/jdeveloper/11gdemos/adffaces/adffaces.html。 看起来真的很酷、漂亮、简单，但当然它只是一个演示:)。我想问是否有人真正将它用于生产应用程序，它们与流行的开源替代品（如 RichFaces 或 IceFaces 等）相比如何。 部署到与 weblogic 不同的服务器怎么样？
I just saw nice little demo about Oracle ADF Rich components: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/adffaces/adffaces.html.
Looks really cool, nice and easy but of course its just a demo :). I would like to ask if someone actually uses it for a production app, how they compare to popular open source alternatives like RichFaces or IceFaces etc.
How about a deployment to a different server than weblogic?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们使用 ADF Faces。这是相当不错的。它们具有所有基本组件（输入文本、输出文本、输入文件、日期选择器、表格等）和一些高级组件（图形、树、树表等）。布局组件也很好，足以满足大多数用例。
但与任何 JSF 组件一样，ADF Faces 组件很难修改。例如，如果您想在输入文本上添加占位符文本，那么您需要诉诸脆弱的黑客技术。
我建议将 ADF Faces 用于企业应用程序，在这些应用程序中，更改和微调 UI 组件的能力并不像快速且低成本的开发那么重要。
此外，ADF Faces 不仅仅是一个组件框架。它是一个完整的 ViewController 框架。查看他们的任务流程，您会感到惊讶。
We use ADF Faces. It is quite good. They have all the basic components(input text, output text, input file, date pickers, tables, etc) and some advanced components(graphs, tree,tree tables, etc). The layout components are also good and will suffice for most use cases.
But as with any JSF component, ADF Faces Components are hard to modify. For instance, if you want to add, say, a placeholder text, on an input text then you need to resort to fragile hacks.
I would recommend ADF Faces for enterprise apps where the ability to alter and fine tune UI components is not as important as fast and low cost development.
Also, ADF Faces isn't just a component framework. It is a full ViewController framework. Check out their Task Flows and you will be amazed.
我们还在当前产品中使用 ADF 框架，将现有的基于表单的产品迁移到新框架。
我想指出 ADF 的主要好处是它们促进声明式编程的方式。我不得不承认，作为一名强大的java开发人员，我倾向于添加自己的编程处理，但对于习惯了表单的人来说，他们会发现学习基础知识很容易。
我还想指出的一个强大功能是他们明确定义 MVC 架构的方式。模型 = BC，控制器 = 任务流，视图 = 嗯，这一点是显而易见的。向 ADF 设计任务流的方式致敬，因为您可以获得视觉表示，或者更好地说，您的设计和逻辑的故事。
我不确定是否要使用不同的服务器，因为 ADF 和 JDeveloper 提供了相当多的功能，这些功能允许您直接配置到服务器并能够在集成服务器上进行测试，我的意思是在安全方面更多以及它的认证部分。因此，即使您能够迁移所需的所有库，您可能仍然会错过一些可以轻松与 weblogic 服务器集成的其他技术。 （如webcenter、soa等）
We also use ADF Framework for our current product where we migrate our existing form based product to the new framework.
The major benefit that I'd like to point out in ADF is the way they promote declarative programming. I have to admit being a strong java developer, I have the tendency to go and add my own programmatic handling, but for someone who is used to forms, they will find it easy to learn the basics.
A strong feature that I also like to point is the way they clearly defined the MVC architecture. Model = BC, Controller = TaskFlow, View = well this one is obvious. Kudos to ADF the way they designed the taskflows as you get to have a visual representation or better put, a story of your design as well as your logic.
I am not sure about using a different server as ADF along with JDeveloper gives quite a load of features which allows you to configure directly to your server and be able to test on your intergrated server as well, with this I mean more on the security side as well as authentication piece of it. So even if you are able to migrate all the libraries needed, you might still be missing out in some of the other technologies that can be easily integrated with a weblogic server. (such as webcenter, soa etc.)