使用 LiveCycle Data Services 进行模型驱动开发的最佳实践
您对在开发企业应用程序时使用模型驱动开发有何建议？ Adobe 的 LiveCycle 数据服务看起来非常有前途，我发现了许多教程/视频，它们展示了通过自动生成方法/函数可以多快地构建应用程序。
最佳实践是什么，使用这些自动生成的方法是好是坏，它们确实可以节省大量时间。
欢迎所有建议，如果您知道一些现有的博客/讨论，请告诉我。
What are your advises on using model driven development in developing enterprise applications. Adobe's LiveCycle Data Services looks very promising, I have found numerous tutorials/videos that shows how fast an application can be build by having methods/functions auto-generated.
What are the best-practices, is it good/bad to use those auto-generated methods, they can really save a lot of time.
All suggestions are welcome, also if you know some existing blog/discussion please let me know.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
确保您的模型非常紧凑，并且当您真正想做的只是填充组合框时，您的对象图不会导致整个数据库崩溃。 ;) 在我们的最后一个 Flex 项目中，我们团队的一部分向我们的管理层推销了使用 Hibernate 作为我们遗留关系数据库的持久层。销售宣传的一部分是该模型可以由向导生成。好吧，也许 LCDS 比 BlazeDS 更好地处理延迟加载，但是当我们第一次尝试加载组合框时，由于向导生成的自动生成关系（有时是递归的），我们提取了几兆数据。由于延迟加载，这些可能在正常的 Web 应用程序过程中不会被发现，但序列化将向您展示“N + 1 问题”的确切含义！
;)
Make sure your model is very tight, and that your object graph doesn't bring down the whole database when all you are really trying to do is fill a combo box. ;) On our last Flex project part of our team sold our management on using Hibernate as the persistence layer on our legacy relational database. Part of the sales pitch was that the model could just be generated by a wizard. Well, maybe LCDS handles lazy loading better than BlazeDS, but the first time we tried to load a combobox, we pulled several megs of data due to the autogenerated relations, sometimes recursive, that the wizards had generated. These probably wouldn't have ever come to light in the course of a normal web app, due to lazy loading, but serialization will show you the exact meaning of "N + 1 problem"!!
;)