It wasn't merely an MVC framework, but a convention-over-configuration MVC framework.
它并非纯粹的mvc框架，而是一种约定优于配置的mvc框架。
Grails is a project aimed at allowing you to write Groovy web applications as quickly as possible, using a convention-over-configuration approach.
Grails是一个项目，旨在让您通过使用一种惯例优先原则(convention - over - configuration)的方式尽快地编写Groovyweb应用程序。
Lift can use a JNDI-supplied connection, using a convention-over-configuration approach: It automatically looks for a data source bound to the JNDI name.
Lift可以通过“约定优先于配置”方式使用JNDI提供的连接：它会自动寻找与JNDI名称绑定的数据源。
Because it USES a convention over configuration approach, the work required to set up a mediation is minimized.
由于它采用约定优于配置的方法，因而最大限度地减少了建立中介所需的工作。
These services are usually offered with "convention over configuration," meaning that they are delivered with the idea of accommodating the most common use cases.
这些服务通常根据“配置惯例”提供，即根据适应最常见使用的情形这一思想提供。
Here you see the benefits of convention over configuration in action: no XML files are required to match these elements up.
从这里可以看出约定优于配置的优点：无需XML文件就可以匹配这些元素。
I want to see something built on top of MS MVC that even more-so favors Convention over Configuration — including but not limited to generators and such.
我想看到一些在MSMVC之上的实现，它们更加遵循“惯例胜于配置”的理念——包括生成器以及更多的功能。
Some shops definitely do require that flexibility, but for the other 80%, aren't some sensible defaults (al a convention over configuration) well worth the productivity gains?
有的商店的确要求那种灵活性，但是对于其它的80%，一些合理的缺省设置(习惯优于配置)难道不值得提高生产力？
Rails illustrates the value of frameworks, the generative power of dynamic languages like Ruby, and how following convention over configuration yields numerous advantages to developers.
Rails说明了框架的价值，动态语言，像Ruby的原动力，以及如何遵守配置的惯例来为开发人员形成许多优势。
The convention part of convention over configuration lets you sit down with any Grails application and know immediately which bits are stored in what bucket.
约定优于配置中的约定部分使您可以拥有任何Grails应用程序，并立即知道各个部分之间的联系。
Ruby on Rails practically invented the term "convention over configuration," and it makes it so easy to create an application.
Rubyon Rails在实践中产生了“约定优于配置(convention over configuration)”一词，并且使用它可以轻松地创建应用程序。
Without it we would not have Grails: Groovy metaprogramming makes convention over configuration possible.
没有它就没有Grails：groovy元编程(metaprogramming)让“惯例优于配置”成为了可能。
This code looks at the name of the invoked class and method and matches these to the name of a Hibernate query using convention over configuration.
该代码查看调用的类和方法的名称，并使用配置上的约定将其与Hibernate查询的名称相匹配。
Convention over configuration means that a developer needs to conform to all of the naming conventions Rails USES, avoiding custom configurations.
约定优于配置意味着开发人员需要遵循Rails使用的所有命名约定，避免自定义配置。
Grails leverages the principles of convention over configuration and don't repeat yourself to greatly reduce the amount of code you need to write for a typical Web application.
Grails利用“约定优于配置(convention over configuration)”和“不要重复自己(don ' t repeat yourself)”的原则，极大地减少了编写典型Web应用程序所需的代码量。
Convention over configuration also leads to "aha!" moments for new Rails developers because the controller and model code is so concise.
约定优于配置也会使新的Rails开发人员能够立即上手，因为控制器和模型代码特别简洁。
For green-field development, I find convention over configuration makes sense.
对于green -field开发，我发现惯例优先于配置是很有意义的。
Implement Annotations as complementary to "Convention over Configuration" principle (e.g. in Spring).
将注解作为“规约优于配置”法则的补充(如spring)。
Because plan() doesn't end with a render() or a redirect(), convention over configuration dictates that grails-app/views/trip/plan.gsp will be displayed.
由于plan()不是以render()或redirect()结束，根据约定优于配置原则，显示的将是grails-app/views/trip/plan.gsp。
Because plan() doesn't end with a render() or a redirect(), convention over configuration dictates that grails-app/views/trip/plan.gsp will be displayed.
由于plan()不是以render()或redirect()结束，根据约定优于配置原则，显示的将是grails-app/views/trip/plan.gsp。
应用推荐