<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>Java Code Geeks &#187; Burt Beckwith</title> <atom:link href="http://www.javacodegeeks.com/author/Burt-Beckwith/feed/" rel="self" type="application/rss+xml" /><link>http://www.javacodegeeks.com</link> <description>Java 2 Java Developers Resource Center</description> <lastBuildDate>Wed, 19 Jun 2013 16:00:34 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.5.1</generator> <item><title>A Grails plugin to bridge Spring Security and Shiro</title><link>http://www.javacodegeeks.com/2013/01/a-grails-plugin-to-bridge-spring-security-and-shiro.html</link> <comments>http://www.javacodegeeks.com/2013/01/a-grails-plugin-to-bridge-spring-security-and-shiro.html#comments</comments> <pubDate>Fri, 11 Jan 2013 11:38:30 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Java]]></category> <category><![CDATA[Apache Shiro]]></category> <category><![CDATA[Grails]]></category> <category><![CDATA[Security]]></category> <category><![CDATA[Spring]]></category> <category><![CDATA[Spring Security]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=6837</guid> <description><![CDATA[I started using Spring Security in 2007 when I was tasked with adding security to a Spring/Hibernate application at the company I was working for. There were a few options to choose from, none of them particularly friendly to work with, and we chose Acegi Security because it was the most popular option for Spring [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/01/a-grails-plugin-to-bridge-spring-security-and-shiro.html/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Grails SQL Logging part 2 &#8211; groovy.sql.Sql</title><link>http://www.javacodegeeks.com/2012/11/grails-sql-logging-part-2-groovy-sql-sql.html</link> <comments>http://www.javacodegeeks.com/2012/11/grails-sql-logging-part-2-groovy-sql-sql.html#comments</comments> <pubDate>Thu, 01 Nov 2012 22:59:49 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Groovy]]></category> <category><![CDATA[Grails]]></category> <category><![CDATA[Logging]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=2792</guid> <description><![CDATA[I discussed options for logging Hibernate-generated SQL in an earlier post but today I was trying to figure out how to see the SQL from groovy.sql.Sql and didn’t have much luck at first. The core problem is that the Sql class uses a java.util.logging.Logger (JUL) while the rest of the world uses a Log4j logger (often with [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/11/grails-sql-logging-part-2-groovy-sql-sql.html/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Grails: Autodiscovery of JPA-annotated domain classes</title><link>http://www.javacodegeeks.com/2012/10/grails-autodiscovery-of-jpa-annotated-domain-classes.html</link> <comments>http://www.javacodegeeks.com/2012/10/grails-autodiscovery-of-jpa-annotated-domain-classes.html#comments</comments> <pubDate>Sun, 28 Oct 2012 11:22:10 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Groovy]]></category> <category><![CDATA[Grails]]></category> <category><![CDATA[JPA]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=2496</guid> <description><![CDATA[There are some issues to be fixed with the support for adding JPA annotations (for example @Entity) to Groovy classes in grails-app/domain in 2.0. This is due to the changes made to adding most GORM methods to the domain class bytecode with AST transformations instead of adding them to the metaclass at runtime with metaprogramming. [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/10/grails-autodiscovery-of-jpa-annotated-domain-classes.html/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Logging Hibernate SQL</title><link>http://www.javacodegeeks.com/2012/10/logging-hibernate-sql.html</link> <comments>http://www.javacodegeeks.com/2012/10/logging-hibernate-sql.html#comments</comments> <pubDate>Tue, 23 Oct 2012 08:05:59 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Groovy]]></category> <category><![CDATA[Grails]]></category> <category><![CDATA[JBoss Hibernate]]></category> <category><![CDATA[Logging]]></category> <category><![CDATA[SQL]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=2166</guid> <description><![CDATA[There are two well-known ways to log Hibernate SQL in Grails; one is to add logSql = true in DataSource.groovy (either in the top-level block for all environments or per-environment) &#160; &#160; &#160; &#160; &#160; &#160; dataSource { dbCreate = ... url = ... ... logSql = true } and the other is to use [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/10/logging-hibernate-sql.html/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Stuff I Learned from Grails Consulting</title><link>http://www.javacodegeeks.com/2012/10/stuff-i-learned-from-grails-consulting.html</link> <comments>http://www.javacodegeeks.com/2012/10/stuff-i-learned-from-grails-consulting.html#comments</comments> <pubDate>Tue, 02 Oct 2012 13:00:00 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Groovy]]></category> <category><![CDATA[Grails]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/stuff-i-learned-from-grails-consulting.html</guid> <description><![CDATA[I don’t do much Grails consulting since I work for the Engineering group, and we have an excellent group of support engineers that usually work directly with clients. I do occasionally teach the 3-day Groovy and Grails course but I’ve only been on two onsite consulting gigs so far, and one was a two-week engagement [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/10/stuff-i-learned-from-grails-consulting.html/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Using Servlet 3.0 Async Features in Grails 2.0</title><link>http://www.javacodegeeks.com/2012/06/using-servlet-30-async-features-in.html</link> <comments>http://www.javacodegeeks.com/2012/06/using-servlet-30-async-features-in.html#comments</comments> <pubDate>Sat, 02 Jun 2012 15:00:00 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[Grails]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/using-servlet-3-0-async-features-in-grails-2-0.html</guid> <description><![CDATA[I was talking to someone last week about the new support for Servlet 3.0 async features in Grails 2 and realized I didn’t know that much about what was available. So I thought I’d try it out and share some examples. The documentation&#160;is a little light on the subject, so first some background information. The [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/06/using-servlet-30-async-features-in.html/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Using Servlet 3.0 Async Features in Grails 2.0</title><link>http://www.javacodegeeks.com/2012/06/using-servlet-30-async-features-in.html</link> <comments>http://www.javacodegeeks.com/2012/06/using-servlet-30-async-features-in.html#comments</comments> <pubDate>Sat, 02 Jun 2012 15:00:00 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[Grails]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/using-servlet-3-0-async-features-in-grails-2-0.html</guid> <description><![CDATA[I was talking to someone last week about the new support for Servlet 3.0 async features in Grails 2 and realized I didn’t know that much about what was available. So I thought I’d try it out and share some examples. The documentation&#160;is a little light on the subject, so first some background information. The [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/06/using-servlet-30-async-features-in.html/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Make your Spring Security @Secured annotations more DRY</title><link>http://www.javacodegeeks.com/2012/06/make-your-spring-security-secured.html</link> <comments>http://www.javacodegeeks.com/2012/06/make-your-spring-security-secured.html#comments</comments> <pubDate>Fri, 01 Jun 2012 01:00:00 +0000</pubDate> <dc:creator>Burt Beckwith</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[Annotations]]></category> <category><![CDATA[DRY]]></category> <category><![CDATA[Spring]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/make-your-spring-security-secured-annotations-more-dry.html</guid> <description><![CDATA[Recently a user on the Grails User mailing list wanted to know how to reduce repetition when defining @Secured annotations. The rules for specifying attributes in Java annotations are pretty restrictive, so I couldn’t see a direct way to do what he was asking. Using Groovy doesn’t really help here since for the most part [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/06/make-your-spring-security-secured.html/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 1/9 queries in 0.060 seconds using apc
Object Caching 1175/1247 objects using apc
Content Delivery Network via jcg.javacodegeeks.netdna-cdn.com

Served from: www.javacodegeeks.com @ 2013-06-19 21:53:45 -->