<?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/"
	>

<channel>
	<title>haxx qua non</title>
	<atom:link href="http://haxx.sinequanon.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://haxx.sinequanon.net</link>
	<description></description>
	<pubDate>Mon, 19 Oct 2009 18:58:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Security policy permissions for Grails in Tomcat</title>
		<link>http://haxx.sinequanon.net/2009/06/security-policy/</link>
		<comments>http://haxx.sinequanon.net/2009/06/security-policy/#comments</comments>
		<pubDate>Thu, 04 Jun 2009 23:27:59 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[security]]></category>

		<category><![CDATA[tomcat]]></category>

		<guid isPermaLink="false">http://haxx.sinequanon.net/?p=200</guid>
		<description><![CDATA[Here are the permissions I&#8217;ve used for Grails apps deployed to Tomcat running the Java security manager. The Grails 1.0.x permissions are for a simple CRUD app. So far the Grails 1.1 permissions are just for a Hello World app. They&#8217;re not cut-and-paste: some thought is required to apply to individual server setups and some [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2009/06/security-policy/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Tomcat AJP/1.3 Connector issues</title>
		<link>http://haxx.sinequanon.net/2009/03/tomcat-ajp13-connector-issues/</link>
		<comments>http://haxx.sinequanon.net/2009/03/tomcat-ajp13-connector-issues/#comments</comments>
		<pubDate>Fri, 27 Mar 2009 17:20:26 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[AJP]]></category>

		<category><![CDATA[tomcat]]></category>

		<guid isPermaLink="false">http://haxx.sinequanon.net/?p=178</guid>
		<description><![CDATA[The documentation for Tomcat 6.0.18 AJP/1.3 Connectors is incomplete and misleading. It seems to indicate that there is exactly one class for AJP, but there are actually three and the one you get may not match the documentation.

I tried to use the new executor but kept getting exceptions like:
[DATE] org.apache.catalina.startup.ConnectorCreateRule _setExecutor
WARNING: Connector [org.apache.catalina.connector.Connector@11e1e67] does not [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2009/03/tomcat-ajp13-connector-issues/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails 1.1 logging</title>
		<link>http://haxx.sinequanon.net/2009/03/grails-11-logging/</link>
		<comments>http://haxx.sinequanon.net/2009/03/grails-11-logging/#comments</comments>
		<pubDate>Thu, 26 Mar 2009 17:21:48 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[meta]]></category>

		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://haxx.sinequanon.net/?p=166</guid>
		<description><![CDATA[Grails 1.1 has changed logging setup completely, introducing a new DSL closure. For the most part it&#8217;s cool, but the syntax looks the same sometimes for both log level and appender assignments. I&#8217;ve updated my previous posts on debug logging and stacktrace.log. For the record, included below is the complete log4j closure I&#8217;m now using [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2009/03/grails-11-logging/feed/</wfw:commentRss>
		</item>
		<item>
		<title>less, sudo, and /dev/null: Permission denied</title>
		<link>http://haxx.sinequanon.net/2009/03/less-sudo-and-devnull-permission-denied/</link>
		<comments>http://haxx.sinequanon.net/2009/03/less-sudo-and-devnull-permission-denied/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 21:33:09 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[/dev/null]]></category>

		<category><![CDATA[less]]></category>

		<category><![CDATA[sudo]]></category>

		<guid isPermaLink="false">http://haxx.sinequanon.net/?p=150</guid>
		<description><![CDATA[Sigh. The ubiquitous utility less does a really bad and hard to understand thing. For some time now, it behaves not just as a reader but also a writer: it writes a history file (specified by the environment variable LESSHISTFILE which is $HOME/.lesshst by default). If you want less to be writing things, fine, but [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2009/03/less-sudo-and-devnull-permission-denied/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Rails logged_in_user idiom</title>
		<link>http://haxx.sinequanon.net/2008/10/rails-logged_in_user-idiom/</link>
		<comments>http://haxx.sinequanon.net/2008/10/rails-logged_in_user-idiom/#comments</comments>
		<pubDate>Tue, 07 Oct 2008 18:04:21 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=113</guid>
		<description><![CDATA[I recently refactored another developer&#8217;s code to clean up some massive amounts of database pings to retrieve the current user object. The main problem was in the use of the logged_in_user or current_user idiom in Rails. Several places give good examples but leave out the details that were bugging my project.

user.id
Firstly, don&#8217;t store the user [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2008/10/rails-logged_in_user-idiom/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails error.gsp security</title>
		<link>http://haxx.sinequanon.net/2008/10/grails-errorgsp-security/</link>
		<comments>http://haxx.sinequanon.net/2008/10/grails-errorgsp-security/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 20:13:59 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=91</guid>
		<description><![CDATA[The default generated error.gsp view in Grails displays the stacktrace for any exceptions that occur. That&#8217;s nice for debugging in a development environment but it is a security issue for production as it is information leakage. We can easily turn this off when not in development, and do something useful like redirect to the application [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2008/10/grails-errorgsp-security/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails stacktrace.log</title>
		<link>http://haxx.sinequanon.net/2008/09/grails-stacktracelog/</link>
		<comments>http://haxx.sinequanon.net/2008/09/grails-stacktracelog/#comments</comments>
		<pubDate>Tue, 30 Sep 2008 23:58:57 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=78</guid>
		<description><![CDATA[Grails 1.0.x started creating a stacktrace.log file in the directory where the servlet container starts. In a development environment, using grails run-app, that&#8217;s simple enough&#8212; it appears in the top level of your application. In a production environment, this becomes a problem. Your production container (e.g. Tomcat) may start someplace where it can&#8217;t create files, [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2008/09/grails-stacktracelog/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails logging</title>
		<link>http://haxx.sinequanon.net/2008/09/grails-logging/</link>
		<comments>http://haxx.sinequanon.net/2008/09/grails-logging/#comments</comments>
		<pubDate>Wed, 24 Sep 2008 19:39:07 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=72</guid>
		<description><![CDATA[To turn on display of debug log messages in Grails 1.0.2, add this to the bottom of grails-app/conf/Config.groovy:


environments {
  development {
    log4j {
      logger {
         grails."app"="debug,stdout"
         //grails="debug,stdout"    [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2008/09/grails-logging/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails testing</title>
		<link>http://haxx.sinequanon.net/2008/09/grails-testing/</link>
		<comments>http://haxx.sinequanon.net/2008/09/grails-testing/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 19:10:37 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[grails]]></category>

		<category><![CDATA[junit]]></category>

		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=58</guid>
		<description><![CDATA[The Grails docs talk about testing and have some example test methods but fail to describe some simple but necessary mechanics to get it going. The test methods should be in a class that extends GroovyTestCase (that word doesn&#8217;t appear at all when searching the Grails website). The class name must end with Tests since [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2008/09/grails-testing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Grails .gitignore</title>
		<link>http://haxx.sinequanon.net/2008/09/grails-gitignore/</link>
		<comments>http://haxx.sinequanon.net/2008/09/grails-gitignore/#comments</comments>
		<pubDate>Thu, 18 Sep 2008 19:14:06 +0000</pubDate>
		<dc:creator>jja</dc:creator>
		
		<category><![CDATA[tech]]></category>

		<category><![CDATA[git]]></category>

		<category><![CDATA[grails]]></category>

		<guid isPermaLink="false">http://blog.sinequanon.net/?p=49</guid>
		<description><![CDATA[I&#8217;ve started playing with git for source code revision management. Here is my first cut at a .gitignore for a Grails 1.0.3 project. Note that for previous versions you will also need (at least) a line /plugins/core


# .gitignore for Grails 1.0.3

# web application files that are overwritten by "grails upgrade"
#  cf. GRAILS_HOME/scripts/Upgrade.groovy, target( upgrade [...]]]></description>
		<wfw:commentRss>http://haxx.sinequanon.net/2008/09/grails-gitignore/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
