tag:blogger.com,1999:blog-23356474874690398252018-08-28T12:12:26.152-07:00Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-2335647487469039825.post-77663478339828728402010-01-31T07:51:00.000-08:002010-01-31T07:59:29.713-08:00

The Scala List class introduces foldLeft and foldRight which will be unfamiliar to Java developers. The fold methods apply a function to each element in the list either starting at the first element or the last, for foldLeft and foldRight respectfully. The result of the function applied to the first element is passed to the second function. Clear as mud? Let me explain with an example Create

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com1tag:blogger.com,1999:blog-2335647487469039825.post-62294871150407265852009-10-10T12:14:00.001-07:002009-10-10T12:31:31.184-07:00

The edit component is a combination of the view and create components shown previously. The addition of the edit component lets us remove the CRUDify trait from the Item MetaMapper object as well as removing all the override menuloc methods. object Item extends Item with LongKeyedMetaMapper[Item] { override def fieldOrder = List(name, amount) } Add a file called edit.html in the src/

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com10tag:blogger.com,1999:blog-2335647487469039825.post-44096585069568349742009-09-13T11:29:00.001-07:002009-09-13T11:29:35.648-07:00

The delete view provided by the CRUDify trait gives a page that shows the details of the Item that is going to be deleted. The page has a button which when pressed deletes the Item from the database. The URL of the delete view is http://localhost:8080/item/delete/1 . The delete view is very similar to the create view. The major differences are that the Item can not be edited, the view needs

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com2tag:blogger.com,1999:blog-2335647487469039825.post-83897636177832240382009-09-07T10:30:00.001-07:002009-09-07T10:37:24.604-07:00

The CRUDify trait adds a view url for a item. In this post we will turn off this view and build our own. To turn off the CRUDify view override the viewMenuLoc method in the Item object override def viewMenuLoc = Empty The view item the url is http://localhost:8080/item/view/1 where final part of the url is the primary key (PK) of the item. To write our own version of the view functionality

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com3tag:blogger.com,1999:blog-2335647487469039825.post-48069088796121154082009-08-30T13:41:00.000-07:002009-08-30T13:42:19.024-07:00

The create form is one of the other pages CRUDify trait provides. To hand roll your own form deactivate the 'Create Item' menu in the Item class by overriding the createMenuLoc method on the Item class. override def createMenuLoc = Empty Add a file called create.html in the /src/main/webapp/item/ folder. The create.html file should contain some sample text to test the page with.

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com6tag:blogger.com,1999:blog-2335647487469039825.post-44099713935687553972009-08-26T14:43:00.001-07:002009-08-28T11:22:50.586-07:00

The CRUDify Lift trait is a fast way to get CRUD functionality in to the application but often finer control is required over the functionality. The CRUDify trait provides view, edit, delete and list functionality for the Entity which mixes in the trait. Each piece of functionality can be turned on or off.To turn off the list functionality override the showAllMenuLoc in the Item class.override

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com1tag:blogger.com,1999:blog-2335647487469039825.post-39850252772730514772009-08-19T14:02:00.001-07:002009-09-15T11:37:17.606-07:00

Building a CRUD application in Lift is straight forward. First use maven to create a new Lift application .mvn archetype:generate -U \ -DarchetypeGroupId=net.liftweb \ -DarchetypeArtifactId=lift-archetype-basic \ -DarchetypeVersion=1.0 \ -DremoteRepositories=http://scala-tools.org/repo-releases \ -DgroupId=com.shopping \ -DartifactId=shopping \ -Dversion=0.1-SNAPSHOT After maven has finished

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com7tag:blogger.com,1999:blog-2335647487469039825.post-37368854328032237222008-10-07T12:12:00.000-07:002008-10-08T13:07:47.131-07:00

Adding indexes to my domain classes caused the performance of inserting five hundred thousand records into my database to drop significantly. The solution I found was to drop the indexes before I started the insert and recreate them afterward. In this post I'll explain how to use hibernate to create and drop index statements for a domain class and add how to implement this logic as two new

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com2tag:blogger.com,1999:blog-2335647487469039825.post-18949880342462482542008-09-14T14:10:00.000-07:002008-09-14T14:21:43.008-07:00

After adding all my ItemReaders, ItemWriters and Steps to resources.groovy in order to bootstrap using SpringBatch I found that it was looking rather bloated.  I don't need to bootstrap my spring application context with these beans every time I start my app but rather only in certain environments, when I set a environment property or if I move to a new database etc.  I could put a large if

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com0tag:blogger.com,1999:blog-2335647487469039825.post-9947211662890378912008-09-12T10:54:00.000-07:002008-10-15T13:49:32.765-07:00

Normal Bootstrapping As part of the current app I'm putting together I needed to populate my database with data from some flat files. The initial approach was to create a BootStrap class for each of the domain classes. Each of my BootStrap classes read the input file, splits each line, maps each item from the line to a attribute of the domain object and then saves the object. class

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com6tag:blogger.com,1999:blog-2335647487469039825.post-61621581462347625522008-08-13T13:48:00.000-07:002008-09-12T12:27:35.041-07:00

I've just started looking at Grails and been trying to install the Simple Captcha Plugin. Following the instructions on grails.org gave java.io.FileNotFoundException: /Users/blah/collab-todo/plugins/Captcha-0.5/plugin.xml The reason for this is that the plugin expect grails version 0.5 and I'm running version 1.0.3. To fix the problem I expanded the zip file, cd'-ed' into the directory and

Olliehttp://www.blogger.com/profile/03780823279661146672noreply@blogger.com5