<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Persistence Ignorance</title>
	<link>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Sat, 17 May 2008 09:48:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: Mats Helander</title>
		<link>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5447</link>
		<pubDate>Fri, 16 Mar 2007 10:25:52 +0000</pubDate>
		<guid>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5447</guid>
					<description>Specifying your mapping meta data with attributes can be kind of convenient, but one good thing with using xml is that it is easier to use a specialized tool for creating and maintaining it, which won't have to try to mess about with your code files, adding attributes to them. 

NPersist also supports both attributes and xml nowadays, since the best way is obviously to have the option to decide for yourself which you prefer, but I have to agree with Simon that it probably won't take long until code files have more attributes than code in them, so in my opinion the xml files are still the better way to go.

/Mats</description>
		<content:encoded><![CDATA[<p>Specifying your mapping meta data with attributes can be kind of convenient, but one good thing with using xml is that it is easier to use a specialized tool for creating and maintaining it, which won&#8217;t have to try to mess about with your code files, adding attributes to them. </p>
<p>NPersist also supports both attributes and xml nowadays, since the best way is obviously to have the option to decide for yourself which you prefer, but I have to agree with Simon that it probably won&#8217;t take long until code files have more attributes than code in them, so in my opinion the xml files are still the better way to go.</p>
<p>/Mats
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Simon</title>
		<link>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5443</link>
		<pubDate>Thu, 15 Mar 2007 14:50:28 +0000</pubDate>
		<guid>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5443</guid>
					<description>It's funny how things go around in circle.  I thought one of the main purposes of using XML is to separate configuration out of the source code.  Annotation will become source code in a different form.  Next thing you know you'll end up with more annotation than the actual code.  People will start whining again.</description>
		<content:encoded><![CDATA[<p>It&#8217;s funny how things go around in circle.  I thought one of the main purposes of using XML is to separate configuration out of the source code.  Annotation will become source code in a different form.  Next thing you know you&#8217;ll end up with more annotation than the actual code.  People will start whining again.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeff Perrin</title>
		<link>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5442</link>
		<pubDate>Thu, 15 Mar 2007 13:05:58 +0000</pubDate>
		<guid>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5442</guid>
					<description>Really? That's not so good.</description>
		<content:encoded><![CDATA[<p>Really? That&#8217;s not so good.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ayende Rahien</title>
		<link>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5440</link>
		<pubDate>Thu, 15 Mar 2007 06:48:29 +0000</pubDate>
		<guid>http://www.jeffperrin.com/index.php/2007/03/14/persistence-ignorance/#comment-5440</guid>
					<description>It is certainly a LOT easier to have it done via attributes, but it is essential that it won't be done _just_ with attributes.
The Microsoft approach a the moment seems to require BOTH attributes and multiply XML files.</description>
		<content:encoded><![CDATA[<p>It is certainly a LOT easier to have it done via attributes, but it is essential that it won&#8217;t be done _just_ with attributes.<br />
The Microsoft approach a the moment seems to require BOTH attributes and multiply XML files.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
