深夜福利视频在线观看,亚洲视频一区,亚洲精品乱码视频

ThinkingTalking — Tue, 13 Oct 2009 02:51:00 GMT

引用自：http://www.groovycn.com/2009/02/grails-10-tips/

如果要列举近些年来Java领域中最令�h�Ȁ动的事�g�Q�Grails的诞生绝对应该榜上有名。在打开Grails官方�|�站�Ӟ�� 你会在浏览器的标题栏上看到这��L��内容�Q?#8220;Grails - ��L��此�l�束”。虽然这句话不见得适用于所有场合，但对于不��从事Java Web开发的人来��_��赞同者恐怕不在少数。由于具备Rails风格的框架、兼容绝大多数Java语法的Groovy动态语�a�、以业界口碑良好的框架�ؓ�? ��、对企业现有Java开发资产的保护、Plugin架构�{�特点，再加上Spring�C�֌�的强力介入，Grails行情看涨应该是意料之中的�?/p>

然而Grails却没有看上去那么��单，在其包装的糖衣之下，有着许多作�ؓJava Web开发者不得不了解的知识。最�q�，Peter Delahunty发表了题�?a >Grails开发者需要知道的10个技�?/a>的博文。不要被标题所�q�h��了，�q�里所说的“技�?#8221;可不是那些语�a�层面�?#8220;技�?#8221;�Q�把它们�U�Cؓ“��”恐怕更合适一些�?br />
技�?�Q�把Grails的书�c�买来读诅R��对此，Peter Delahunty推荐了已出版的《Definitive Guide to Grails 2nd edition》和《Groovy and Grails Recipes》，以及卛_��出版的《Grails in Action》�?/p>

技�?�Q�学习Groovy�Q��ƈ按照Groovy�q�行思考。Peter Delahunty通过一个例子说明了Java思维和Groovy思维的不同�?/p>

�q�儿有个好例子：

传播操作�W�（spread operator�Q�：*

在Java中，要想遍历一�l��h�q�收集�h名。我可能得这样写�Q?/p>
List names = new ArrayList();



for (Iterator iterator = people.iterator(); iterator.hasNext();) {



Person person = (Person) iterator.next();



names.add(person.getName());



}



System.out.println(names);
用Groovy�Q�我会这么写�Q?/p>
def names = people*.name



println names
呵呵�Q�简单吧。我�q�可以这样写�Q?/p>
def names = people.collect {it.name}



println names

在这个徏议中�Q�他列�D了一些资源：

Groovy官方�|�站
PLEAC

以及一些书�c�：

Programming Groovy
Groovy Recipies
Groovy in action

技�?�Q�了解Grails的各个插件。Peter Delahunty�l�出的理由：Grails本��n是个插�g�pȝ��Q�而且现在已经有大量的插�g可供下蝲。在自行实现之前�Q�不妨看看其中是否有�U�手的�?/p>

技�?�Q�学习Hibernate和Spring。这一点不隄��解，既然Grails是徏立在�q�些工具之上的，了解�q�些工具本��n的��用，对于熟练使用Grails自然大有脄��?/p>

技�?�Q��单元��试、集成测试和一般测试的自动化。Peter Delahunty在这里推荐了两个Grails的插�Ӟ��Testing Plugin�?a >Functional testing plugin。前者将成�ؓGrails 1.1的内�|�插件�?/p>

技�?�Q��用好的IDE。Peter Delahunty表示�Q�他自己使用的是Intellij�Q�但对于Netbeans也寄予厚望�?/p>

技�?�Q�学习�ƈ使用HTML W3C标准�?#8220;遵��@标准��消除你90%的问�?#8221;�Q�Peter Delahunty如是说�?/p>

技�?�Q�看上去不错一定不错。这其实说的�?#8220;面子工程”�Q�通过提高应用的外观设计来提高应用的竞争力。Peter Delahunty�l�出�?个资源：

99designs.com
圆角矩�Ş产生�?/a>

技�?�Q��用Firefox上的Firebug。对于浏览器端的调试工作�Q�Firebug�l�对是一个必备工兗��?/p>

技�?0�Q�跟上Groovy和Grails�C�֌�的步伐。在�q�最后一个徏议中�Q�Peter Delahunty�l�出了获取Groovy和Grails信息的主要资源链接：

Grails官方�|�站
Groovy和Grails相关的博�?/a>

Grails创始人Graeme Rocher的Twitter
Groovy��目领导人Guillaume Laforge的Twitter
Groovyblogs.org的创始�hGlen Smith

请务必阅读Peter Delahunty�?a >原文。对于Grails的新老��用者，你都可以从Peter Delahunty的徏议中有所收获。关于InfoQ中文站Groovy和Grails的其它内容，误��?a >�q�里�?a >�q�里�?/p>

ThinkingTalking 2009-10-13 10:51 发表评论

Grails in Eclipse

ThinkingTalking — Tue, 13 Oct 2009 02:44:00 GMT

Importing a Grails Project

Grails automatically creates Eclipse project and classpath files for you. The Groovy plugin is helpful for working with Grails projects, but not required in order to import a project: do not rely on it for assistance.To import a Grails project just right-click in the "Package Explorer" and select "Import" then "Existing project into Workspace" and "Browse" to the location of your project.

Then immediately click "Ok" followed by "Finish" and your project will be set-up. Using other methods of importing the project may prove to be problematic due to compile location.

There is a known issue that Grails will not run properly if you try to use the root directory of your drive as your project, or paths with spaces.

Setting up Eclipse Environment Variables

You will need to create an Eclipse classpath variable called GRAILS_HOME that points to the location where you installed Grails for the project to build successfullly by going to Windows -> Preferences… -> Java -> Build path -> Classpath Variables -> New.

If you don't already have GRAILS_HOME as part of your standard environment, in order to run your Grails project, you will need to establish that value in the Run dialog (Run...) under the Environment tab, to the same value as above.

If your Grails project has Grails plugins installed then you will need to add the directories directly under the plugins/src/ folder to your Eclipse source path. This is done through right clicking on the folder (usually called "Groovy" or "Java") then selecting build path -> source folder. Otherwise you may get errors in the import statements.

Also, if you are using JSP you will need to add your JDK's tools.jar library to your project classpath otherwise jetty will display compilation errors. See this page for info: http://nuin.blogspot.com/2005/05/launch-jetty-from-eclipse-solving.html

If you are using the Eclipse Groovy plugin then make sure you enable the preference 'Disable Groovy Compiler Generating Class Files' (newer versions: Project -> Preferences -> Groovy Project Preferences / older versions: Windows -> Preferences -> Groovy Preferences). By default this option is disabled and generates class files for your groovy files, and stores them in the basedir of your Grails project. When these class files are generated, unexpected behaviour is encountered like not able to generate controllers and views for your domain classes.
THIS DOES NOT APPLY IF YOU INTEND TO USE DEBUGGING (read the section 'Step debugging' below)

Running a Grails application

Grails also automatically creates an Eclipse run configuration for you. To run the project you are in use the "Run" dropdown to open the "Run" dialog then under "Java Applications" find the name of your project select it and click "Run". The Grails application will load embedded inside Eclipse, any changes made inside the Eclipse project can be auto-reloaded.

If you are getting exceptions like

org.mortbay.util.MultiException[java.io.FileNotFoundException: {yourpath}/web-app]

at org.mortbay.http.HttpServer.doStart(HttpServer.java:731)

at org.mortbay.util.Container.start(Container.java:72)

at grails.util.GrailsMain.main(GrailsMain.java:67)

then you need to do is run the ant target:

grails dev package

which will package up grails into the web-app directory in the same way as the "grails run-app" command will. This is then used as the base for eclipse to execute.

For some other errors or quirky behavior, it is often helpful to run the command

grails clean

Step Debugging with Eclipse

You can step debug a Grails application if you install the latest build of the Groovy Eclipse plug-in.

Eclipse debugging depends on the class files generated by the Groovy compiler, so make sure 'Disable Groovy Compiler Generating Class Files' is not checked (Project -> Properties -> Groovy Project Properties) and the output folder is set to e.g. "bin-groovy". Then edit the ".classpath" file in your project directory and manually remove the entry for "bin-groovy".

To debug an application, do the following:

Open up the Groovy file you want to debug (lets say a controller called {{BookController.groovy}}) then set a break point on the line you want to stop at. (set a breakpoint by double clicking in the far left "gutter")
Now debug the application in the same way as you did in the above section on "Running a Grails application" except with the "Debug" menu.
Load your browser and navigate to the action that calls the code.

Eclipse should then stop at the appropriate place and you can then inspect variables and step through the code. If you have the Grails source code set-up on your Source path you can step into that code too.

Adding domain classes etc.

You can configure grails as an "External Tool", allowing you to create domain classes etc. from within Eclipse:

Select "Run > External Tools > External Tools Configurations...".
Double-click "Program"
Enter a name of "Grails".
Browse the file system for the location of grails or grails.bat.
Set the working directory to "${project_loc}".
Set the arguments as "${string_prompt}".
Under the "Refresh" tab, set to refresh the "project containing the selected resource" upon completion.
Under the "Common" tab, tick "Display in favorites menu".

You can then run Grails by clicking the down arrow next to the external tool icon (run with a suitcase) and selecting "Grails", for example:

Choose "Grails" from the external tools drop-down.
Enter "create-domain-class" in the dialogue box.
In the console window, follow the prompts as normal.
Open your new class from grails-app/domain.

Editing GSP files

The gsp files are just jsp files with a special taglib. The extension gsp has to be added as follows:

General -> Editors -> File Associations: add *.gsp and link the JSP Editor to it.
General -> Content Types Fold out Text -> JSP and add *.gsp

This enables jsp editing for the gsp files. To enable code completion add the following at the start of the gsp (Grails before version 1.1 only):

<%@ taglib prefix="g" uri="/web-app/WEB-INF/tld/grails.tld" %>

Since Grails 1.1 this no longer works.

Unit Tests

To run Grails/Groovy unit tests, the easiest way is just to create a junit run configuration, but specifying "groovy.util.AllTestSuite" as the main class. More info on general groovy unit testing in grails here

To run a single test, create a run-config as described above or duplicate an existing entry. Select "Run a single test", select your project and the test class. Save and test your config. You can also rerun a single test in the (g)unit test view by clicking with the right mouse button on an single test and selecting "Run".

Troubleshooting

If you getting the following error every time you save *.groovy file in your project:

An internal error occurred during: "Building workspace".

BUG! exception in phase 'conversion' in source unit '...' Error:

duplicate class declaration for name: … and class:

org.codehaus.groovy.ast.ClassNode@...[name:...]

try the following:

Right click on package explorer's project name and open "Properties..." dialog.
Select "Builders" and make sure that "Groovy Builder" is checked.
Select "Java Compiler/Building" and check "Enable project specific settings".
Append "*.groovy" to "Filtered Resources" text field, to prevent ".groovy" files being copied to the output directory. Note that the path separator is "," not ";"
Apply changes and close dialog.
Clean your project. Make sure that the output directory doesn't contain "*.groovy" files

If Eclipse complains that it can not find the sources where breakpoints are set ensure the following:

Step filtering is enabled for groovy.*, org.codehaus.* (more about this http://groovy.codehaus.org/Debugging+with+Eclipse )
Build out put for the project is in a separate folder (say /bin ). Make sure this is present for Project->Properties->Groovy Project Properties

Few other recommendations:

Make sure to add all the libraries from grails-app/lib folder to the project
Using verbose logging/tracing through log4j.properties until everything works from the Eclipse IDE. Sometimes if some library is not found, unless it is printed in the console, it is difficult to find out what went wrong.
Make sure to use the same JDK for tools.jar as well as the runtime jar rt.jar. Do note sometimes using the JRE instead of rt.jar causes problems.
Sometimes "launch configuration" generated by grails is not in sync with the way ant's build.xml works. In Grails 0.3 ensure that following VM parameters (do note not program arguments, but VM arguments ) are set "-Dorg.mortbay.xml.XmlParser.NotValidating=true". Without this there will be XML Parser exception thrown when launched from the IDE.

Brute Force method:

If running from IDE has issues, most likely it is because some library is missing. Ensure that all libraries under GRAILS_HOME/dist, GRAILS_HOME/ant/lib, GRAILS_HOME/lib and your project folder/lib are added to the build path of the project.

ThinkingTalking 2009-10-13 10:44 发表评论

ThinkingTalking — Tue, 13 Oct 2009 02:40:00 GMT

1、JDK安装�?br /> 2、到官网上下载grails。http://www.grails.org/Download
3、解压，配置GRAILS_HOME�Q�Path
4、在命��o行输入：grails。如果出现帮助信息，说明安装成功�?br /> 5、开始应用程序�?br /> 选择一个工作目录，在命令行输入�Q�grails create-app demo�?br /> 会在当前目录下生成一个demo文�g夹，里面有自动生成的好多文�g�Q�这��是一个grails��目�?br /> The "create-app" target created a Grails data source artifact for you in the "<..>/grails-app/conf" directory called DataSource.groovy with closures for each of the standard environments: Development, TestData, and Production.
�q�就是一个可�q�行的web��目。输�? grails run-app
在浏览器输入:http://localhost:8080/demo
6、cd 到demo目录�Q�在命��o行输入：grails create-domain-class User�Q�创��Z��个User实体�c�R�?br /> cd到demo\grails-app\domain目录下，�q�里存放所有的实体�c�R��修改User.groovy文�g为：

class   User {

String name

String password



String toString() {

" $name : $password "

}



static  constraints  =  {

name(blank:  false )

password(blank:  false , size:  6 .. 16 )

}

7、在命��o行输入：grails generate-all User�?/span>为User产生所有CRUD操作需要的代码�Q�如控制器UserController.groovy�Q�和��面�Q�如list.gsp�Q?br /> 8、输入：grails create-controller Login生成控制�?/span>
9�?/span>修改demo\grails-app\controllers\LoginController.groovy的内容�ؓ�Q?br />

class LoginController {

def loginService



def index = { }



def login = {

User u = new User()

u.properties = params

if (params.name && params.password) {



def user = loginService.check(u)



if (user) {

flash.message = "Welcome ${user.name}"

render(view: "ok", model: [user: user])

} else {

flash.error = "Invalid ${u.name} with ${u.password}"

render(view: "login", model: [user: u])

}

} else {

render(view: "login", model: [user: u])

}

}

}

10、输入：grails create-service Login。创��Z��务逻辑�?/span>
11�?/span>修改demo\grails-app\services\LoginService.groovy的内容�ؓ�Q?br />

class LoginService {



boolean transactional = true



def check(User u) {

def user = User.findWhere(name: u.name, password: u.password)

return user

}



def serviceMethod() {

// TODO

}

}

12�?span style="color: #000099;">修改demo\grails-app\conf\ApplicationBootStrap.groovy�Q�将一个User实例保存到数据库(grails自带hsqldb和jetty)中，内容如下�Q?/span>

class ApplicationBootStrap {



def init = { servletContext ->

new User(name: "demo", password: "123456").save()

}

def destroy = {

}

}

13�?span style="color: #000099;">�?#8220;命��o�?#8221;中，输入“grails run-app”�Q�运行我们的Web应用

14�?span style="color: #000099;">打开��览器，输入�Q?/span>http://localhost:8080/demo/login/login �Q�在Name处输入demo�Q�Password处输�?23456�Q�点�?#8216;Login’�Q?/span>

ThinkingTalking 2009-10-13 10:40 发表评论

ThinkingTalking — Tue, 13 Oct 2009 01:58:00 GMT

1、安装JDK。不知道怎么安装的可癑ֺ�一下�?br /> 2、安装GDK。一�׃��步：
�Q?�Q�下载：http://dist.groovy.codehaus.org/distributions/groovy-binary-1.6.5.zip
�Q?�Q�配�|�GROOVY_HOME�Q�和配置JAVA_HOME一�?br /> �Q?�Q�配�|�Path。将GROOVY_HOME下的bin��d��到path中�?br /> 3、Hello World!
在windows命��o行环境下输入�Q�groovyConsole �Q�回车�?br /> 在文本区域输入：println ‘Hello World!‘ 然后回�R�?br /> 按ctrl+R�l�合键运行�?br />

ThinkingTalking 2009-10-13 09:58 发表评论