<?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: Why I haven&#8217;t tried JPA?</title>
	<atom:link href="http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/</link>
	<description>Mert Can Akkan's java tips,options, news...</description>
	<lastBuildDate>Wed, 03 Mar 2010 10:08:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: hohonuuli</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-11</link>
		<dc:creator>hohonuuli</dc:creator>
		<pubDate>Tue, 08 Jan 2008 05:53:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-11</guid>
		<description>I&#039;ve been using JPA with some new projects. I&#039;ve been VERY happy with it; I&#039;m looking forward to it&#039;s continued evolution and development.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using JPA with some new projects. I&#8217;ve been VERY happy with it; I&#8217;m looking forward to it&#8217;s continued evolution and development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: altuure</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-9</link>
		<dc:creator>altuure</dc:creator>
		<pubDate>Mon, 07 Jan 2008 18:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-9</guid>
		<description>In Fact I totally agree with you. But In a production environment you can skip some basic feature like caching and querying.
Yes it is really good to work with different frameworks but it is also very risky to mix them unnecessarily. 
JPA may be an industry standard for some day but for  now it is immature and a subset of open standards JPA/TopLink

Thanks.</description>
		<content:encoded><![CDATA[<p>In Fact I totally agree with you. But In a production environment you can skip some basic feature like caching and querying.<br />
Yes it is really good to work with different frameworks but it is also very risky to mix them unnecessarily.<br />
JPA may be an industry standard for some day but for  now it is immature and a subset of open standards JPA/TopLink</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tug</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-8</link>
		<dc:creator>Tug</dc:creator>
		<pubDate>Mon, 07 Jan 2008 15:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-8</guid>
		<description>The link that Altuure mentioned talk about Toplink because Toplink is the Reference Implementation of JPA, so part of the JavaEE RI: Glassfish.

Altuure, base on the fac that JPA allows you to take advantage of its implementation layer using the Delegate API, why not trying to push a JPA usage to be &quot;standard&quot; and use the &quot;hibernate&quot; part only when needed. To take advance of a &quot;real&quot; standard instead of what could be called a defacto standard. And put yourself with a richer resume?
I think that JPA has been a great effort in term of standardization and adoption of principle really pushed by user experience (instead of simple having a pure R&amp;D approach).</description>
		<content:encoded><![CDATA[<p>The link that Altuure mentioned talk about Toplink because Toplink is the Reference Implementation of JPA, so part of the JavaEE RI: Glassfish.</p>
<p>Altuure, base on the fac that JPA allows you to take advantage of its implementation layer using the Delegate API, why not trying to push a JPA usage to be &#8220;standard&#8221; and use the &#8220;hibernate&#8221; part only when needed. To take advance of a &#8220;real&#8221; standard instead of what could be called a defacto standard. And put yourself with a richer resume?<br />
I think that JPA has been a great effort in term of standardization and adoption of principle really pushed by user experience (instead of simple having a pure R&amp;D approach).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: altuure</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-7</link>
		<dc:creator>altuure</dc:creator>
		<pubDate>Mon, 07 Jan 2008 10:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-7</guid>
		<description>I posted the link to show there is no solution in JPA for audit logging.
Author show its solution  with toplink API</description>
		<content:encoded><![CDATA[<p>I posted the link to show there is no solution in JPA for audit logging.<br />
Author show its solution  with toplink API</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Schmidt</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-6</link>
		<dc:creator>Stephan Schmidt</dc:creator>
		<pubDate>Mon, 07 Jan 2008 10:42:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-6</guid>
		<description>The link you&#039;ve supplied seems to concern TopLink, how does that concern Hibernate and JPA?

Peace
-stephan</description>
		<content:encoded><![CDATA[<p>The link you&#8217;ve supplied seems to concern TopLink, how does that concern Hibernate and JPA?</p>
<p>Peace<br />
-stephan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: altuure</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-5</link>
		<dc:creator>altuure</dc:creator>
		<pubDate>Mon, 07 Jan 2008 09:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-5</guid>
		<description>Hi, JPA is just a subset of hibernate

JPA do not support with no vendor support.
caching,logging,interceptor

to support these you have to use some vendor API
eg:
http://tapestryofthoughts.blogspot.com/2007/05/glassfish-and-audit-logging.html</description>
		<content:encoded><![CDATA[<p>Hi, JPA is just a subset of hibernate</p>
<p>JPA do not support with no vendor support.<br />
caching,logging,interceptor</p>
<p>to support these you have to use some vendor API<br />
eg:<br />
<a href="http://tapestryofthoughts.blogspot.com/2007/05/glassfish-and-audit-logging.html" rel="nofollow">http://tapestryofthoughts.blogspot.com/2007/05/glassfish-and-audit-logging.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Schmidt</title>
		<link>http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-4</link>
		<dc:creator>Stephan Schmidt</dc:creator>
		<pubDate>Mon, 07 Jan 2008 08:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.altuure.com/2008/01/07/why-i-havent-try-jpa/#comment-4</guid>
		<description>Hi, could you explain how Hibernate3 differs from JPA? 

Peace
-stephan


-- 
Stephan Schmidt :: stephan@reposita.org
Reposita Open Source - Monitor your software development
http://www.reposita.org 
Blog at http://stephan.reposita.org - No signal. No noise.</description>
		<content:encoded><![CDATA[<p>Hi, could you explain how Hibernate3 differs from JPA? </p>
<p>Peace<br />
-stephan</p>
<p>&#8211;<br />
Stephan Schmidt :: <a href="mailto:stephan@reposita.org">stephan@reposita.org</a><br />
Reposita Open Source &#8211; Monitor your software development<br />
<a href="http://www.reposita.org" rel="nofollow">http://www.reposita.org</a><br />
Blog at <a href="http://stephan.reposita.org" rel="nofollow">http://stephan.reposita.org</a> &#8211; No signal. No noise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
