<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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>Comments on: Grails JSecurity Plugin version 0.4 released</title>
	<atom:link href="http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/feed" rel="self" type="application/rss+xml" />
	<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released</link>
	<description>A search for meaning in software and life</description>
	<lastBuildDate>Thu, 06 Oct 2011 21:33:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-1021</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 29 Apr 2010 05:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-1021</guid>
		<description>Are you seeing these errors when you run the application via &lt;tt&gt;grails run-app&lt;/tt&gt; at the command line? Or in your IDE? If the latter, make sure that the JSecurity JAR file is on the classpath.

Also note that JSecurity has been renamed to Apache Shiro, so you should install the corresponding plugin: &lt;tt&gt;grails install-plugin shiro&lt;/tt&gt;</description>
		<content:encoded><![CDATA[<p>Are you seeing these errors when you run the application via <tt>grails run-app</tt> at the command line? Or in your IDE? If the latter, make sure that the JSecurity JAR file is on the classpath.</p>
<p>Also note that JSecurity has been renamed to Apache Shiro, so you should install the corresponding plugin: <tt>grails install-plugin shiro</tt></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashwini</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-1019</link>
		<dc:creator>Ashwini</dc:creator>
		<pubDate>Thu, 29 Apr 2010 00:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-1019</guid>
		<description>Hi Peter,

I&#039;m new to Grails and JSecurity. I could run basic application on grails and tried to use the JSecurity plugin. The import classes in any Realm file i create are showing up as unresolved errors. Is there a jar file I need to add somewhere to correct this? 

Thanks for your time,
Ashwini</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>I&#8217;m new to Grails and JSecurity. I could run basic application on grails and tried to use the JSecurity plugin. The import classes in any Realm file i create are showing up as unresolved errors. Is there a jar file I need to add somewhere to correct this? </p>
<p>Thanks for your time,<br />
Ashwini</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-621</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 21 Oct 2009 20:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-621</guid>
		<description>Hi Michael,

I&#039;m afraid you caught the documentation in a transitional state as I prepare for a 1.0 release. As I was writing it, I realised that quick-start should probably do more than it does at the moment, hence the reference to a filters class. Certainly the JSecurity documentation is out of date, so that&#039;s why I started to update the Shiro docs. As I get time, I&#039;ll work some more on them.

On the out-of-the-box example, you could always consider the grails.org application, although I believe that uses JSecurity still. Another option is Nimble, which is based on the Shiro plugin but provides extra features, including an admin UI. I&#039;ll probably borrow its idea of creating a BootStrap class to create some test users for quick-start.

Cheers,

Peter</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>I&#8217;m afraid you caught the documentation in a transitional state as I prepare for a 1.0 release. As I was writing it, I realised that quick-start should probably do more than it does at the moment, hence the reference to a filters class. Certainly the JSecurity documentation is out of date, so that&#8217;s why I started to update the Shiro docs. As I get time, I&#8217;ll work some more on them.</p>
<p>On the out-of-the-box example, you could always consider the grails.org application, although I believe that uses JSecurity still. Another option is Nimble, which is based on the Shiro plugin but provides extra features, including an admin UI. I&#8217;ll probably borrow its idea of creating a BootStrap class to create some test users for quick-start.</p>
<p>Cheers,</p>
<p>Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-617</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 21 Oct 2009 09:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-617</guid>
		<description>Peter, I&#039;m not sure if you&#039;ve seen the documentation page for Shiro on the grails plugin site. Go to:

http://grails.org/plugin/shiro

Imagine then that you are a new user trying for the first time to use Shiro. First of all you encounter the confusion with renaming, from jsecurity, to shiro, then to ki or whatever.

Then you begin to follow the documentation, which you immediately get stuck with because it doesn&#039;t say how to install the plugin.

Maybe you&#039;re smart enough to go and do a grails install-plugin shiro, but you&#039;ll soon get stuck again because the quick-install  doesn&#039;t quite install all the files (no filter files are created) it should. As you then return to the documentation you find quite a cliff hanger at the bottom:

&quot;Of course, there are no users in the system yet, so you can&#039;t successfully log in. Let&#039;s rectify that now&quot;

THE END. That&#039;s it. No more documentation.

Peter, I an countless others appreciate the work that&#039;s been done here, but what good is it if you&#039;re the only one who understands how to use it?

Please do two things before you even think of adding another feature or fixing a bug:

First of all some decent documentation needs to be written. This is critical.

Secondly it would be extremely nice if there was an out-of-the-box working example that one could download and just &quot;grails run-app&quot; right away.

These two things would make it so much more easy for people like myself to appreciate the time and efford you and others have put into this project. Right now it&#039;s causing nothing but frustration.

Thanks for letting me blow off some steam here.</description>
		<content:encoded><![CDATA[<p>Peter, I&#8217;m not sure if you&#8217;ve seen the documentation page for Shiro on the grails plugin site. Go to:</p>
<p><a href="http://grails.org/plugin/shiro" rel="nofollow">http://grails.org/plugin/shiro</a></p>
<p>Imagine then that you are a new user trying for the first time to use Shiro. First of all you encounter the confusion with renaming, from jsecurity, to shiro, then to ki or whatever.</p>
<p>Then you begin to follow the documentation, which you immediately get stuck with because it doesn&#8217;t say how to install the plugin.</p>
<p>Maybe you&#8217;re smart enough to go and do a grails install-plugin shiro, but you&#8217;ll soon get stuck again because the quick-install  doesn&#8217;t quite install all the files (no filter files are created) it should. As you then return to the documentation you find quite a cliff hanger at the bottom:</p>
<p>&#8220;Of course, there are no users in the system yet, so you can&#8217;t successfully log in. Let&#8217;s rectify that now&#8221;</p>
<p>THE END. That&#8217;s it. No more documentation.</p>
<p>Peter, I an countless others appreciate the work that&#8217;s been done here, but what good is it if you&#8217;re the only one who understands how to use it?</p>
<p>Please do two things before you even think of adding another feature or fixing a bug:</p>
<p>First of all some decent documentation needs to be written. This is critical.</p>
<p>Secondly it would be extremely nice if there was an out-of-the-box working example that one could download and just &#8220;grails run-app&#8221; right away.</p>
<p>These two things would make it so much more easy for people like myself to appreciate the time and efford you and others have put into this project. Right now it&#8217;s causing nothing but frustration.</p>
<p>Thanks for letting me blow off some steam here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-316</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Mon, 14 Sep 2009 16:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-316</guid>
		<description>Making JSecUser abstract should work as long as you extend it with your own user domain class. I don&#039;t think it&#039;s particularly useful doing so, though, because the default Grails behaviour is for all domain classes in a hierarchy to share the same database table.</description>
		<content:encoded><![CDATA[<p>Making JSecUser abstract should work as long as you extend it with your own user domain class. I don&#8217;t think it&#8217;s particularly useful doing so, though, because the default Grails behaviour is for all domain classes in a hierarchy to share the same database table.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-289</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 07 Sep 2009 22:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-289</guid>
		<description>Hmmm, well in the least, I wouldn&#039;t want to be in a position where modifying the domain classes prevents me from upgrading. I would like to be able to take advantage of any new features that may emerge.

I&#039;m thinking that I could always merge the new domain classes with my modified ones, but that will get a bit tedious if the upgrades are frequent and large. So I&#039;m thinking subclassing the domain classes would be much easier. 

I only need to modify the JSecUser class, though. I just want to add a few extra attributes (i.e., email). I also want to keep the database representative of the actual domain classes being used in the system. So I&#039;m thinking of making the JSecUser class an abstract data type, so no table is created for it. This would also render the JSecUser class un-instantiable. Is that going to cause any problems with Shiro?</description>
		<content:encoded><![CDATA[<p>Hmmm, well in the least, I wouldn&#8217;t want to be in a position where modifying the domain classes prevents me from upgrading. I would like to be able to take advantage of any new features that may emerge.</p>
<p>I&#8217;m thinking that I could always merge the new domain classes with my modified ones, but that will get a bit tedious if the upgrades are frequent and large. So I&#8217;m thinking subclassing the domain classes would be much easier. </p>
<p>I only need to modify the JSecUser class, though. I just want to add a few extra attributes (i.e., email). I also want to keep the database representative of the actual domain classes being used in the system. So I&#8217;m thinking of making the JSecUser class an abstract data type, so no table is created for it. This would also render the JSecUser class un-instantiable. Is that going to cause any problems with Shiro?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-270</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 05 Sep 2009 05:46:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-270</guid>
		<description>If you don&#039;t modify your own copies, you can run them to get new versions if and when they are changed. But typically, if they work for you, then you might as well keep them as they are.</description>
		<content:encoded><![CDATA[<p>If you don&#8217;t modify your own copies, you can run them to get new versions if and when they are changed. But typically, if they work for you, then you might as well keep them as they are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-265</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 04 Sep 2009 12:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-265</guid>
		<description>Would there ever be a need to run those commands again?</description>
		<content:encoded><![CDATA[<p>Would there ever be a need to run those commands again?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-264</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 04 Sep 2009 06:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-264</guid>
		<description>Your domain class files won&#039;t be overwritten when you upgrade. If you run the &quot;create-*-realm&quot; or &quot;quick-start&quot; commands again, they will ask whether you want to overwrite the existing files.</description>
		<content:encoded><![CDATA[<p>Your domain class files won&#8217;t be overwritten when you upgrade. If you run the &#8220;create-*-realm&#8221; or &#8220;quick-start&#8221; commands again, they will ask whether you want to overwrite the existing files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.cacoethes.co.uk/blog/groovyandgrails/grails-jsecurity-plugin-version-0-4-released/comment-page-1#comment-263</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 03 Sep 2009 22:32:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.cacoethes.co.uk/blog/?p=75#comment-263</guid>
		<description>As you can tell, I&#039;m fairly new to Grails. I was wondering if you could tell me if its safe to modify the domain class files installed by the QuickStart script. Would they be overwritten if I were to update the Shiro plugin?</description>
		<content:encoded><![CDATA[<p>As you can tell, I&#8217;m fairly new to Grails. I was wondering if you could tell me if its safe to modify the domain class files installed by the QuickStart script. Would they be overwritten if I were to update the Shiro plugin?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

