<?xml version="1.0" encoding="utf-8"?>

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:admin="http://webns.net/mvcb/"
xmlns:cc="http://web.resource.org/cc/"
xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://weblogs.java.net/blog/ss141213/">
<title>Sahoo&apos;s Blog</title>
<link>http://weblogs.java.net/blog/ss141213/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:creator></dc:creator>
<dc:date>2008-05-12T11:23:37-08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.01D" />


<items>
<rdf:Seq><rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2008/05/updated_instruc.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2008/05/bug_in_bundlege.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2008/04/glassfish_v3_on.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2008/01/getting_started_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2008/01/getting_started.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2007/11/my_maven_experi.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2007/11/my_experience_w.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/11/welcome_to_glas.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/10/persistence_con.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/07/using_openjpa_a_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/05/using_kodo_as_j.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/05/which_glassfish.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/03/using_java_pers_1.html" />
<rdf:li rdf:resource="http://weblogs.java.net/blog/ss141213/archive/2006/01/when_can_i_use.html" />
</rdf:Seq>
</items>

</channel>

<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2008/05/updated_instruc.html">
<title>Updated instructions to use OpenJPA in GlassFish</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2008/05/updated_instruc.html</link>
<description>Layout of OpenJPA installation has changed since I last blogged about using OpenJPA in GlassFish, so many users who are unaware of this difference face some trouble while using OpenJPA in GlassFish. I thought of updating the instructions; hence this blog.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2008-05-12T11:23:37-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2008/05/bug_in_bundlege.html">
<title>Bug in Bundle.getResource() in Knopflerfish?</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2008/05/bug_in_bundlege.html</link>
<description>I observed some difference in behavior while running an OSGi test case on Knopflerfish, and decided to investigate further. Here is the outcome...</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2008-05-01T00:38:52-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2008/04/glassfish_v3_on.html">
<title>GlassFish V3 on OSGi - Part I</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2008/04/glassfish_v3_on.html</link>
<description>We have put back initial code that enables GlassFish V3 to run on an *OSGi* R4 platform. This is in addition to it being able to run on its own runtime, i.e., HK2. Since I have been involved in this effort from the very beginning, I will be blogging about it in days to come. Today is just the start.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2008-04-15T19:56:21-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2008/01/getting_started_1.html">
<title>Getting started with HK2 - Part II</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2008/01/getting_started_1.html</link>
<description>As promised in my last blog, in this blog I am going to expand our Hello World sample to demonstrate module management, class loading, component injection features in HK2.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2008-01-28T12:29:35-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2008/01/getting_started.html">
<title>Getting started with HK2 - Part I</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2008/01/getting_started.html</link>
<description>Using a &quot;Hello World&quot; type sample, I show how to get started with HK2. Those of you who don&apos;t know what is HK2, it is the short name for &quot;Hundred Kilobyte Kernel,&quot; HKK further reduced to HK2. It is being used in development of ultra light weight, modular, next generation GlassFish application server. HK2 is not just meant for GlassFish or application server type applications; any Java SE programmer can use it to write modular applications. It has a very nice component model with IoC support.</description>
<dc:subject>Community: Java Enterprise</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2008-01-28T06:30:07-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2007/11/my_maven_experi.html">
<title>My experience while writing an annotation processor - part II</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2007/11/my_maven_experi.html</link>
<description>In my last blog I talked about Java related issues that I faced while writing an annotation processor that would generate persistence.xml file when I compile my JPA entity classes. To complete the story, this time I will share my maven experiences.</description>
<dc:subject>J2SE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2007-11-30T01:39:21-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2007/11/my_experience_w.html">
<title>My experience while writing an annotation processor - part I</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2007/11/my_experience_w.html</link>
<description>Recently I was writing an annotation processor that would generate persistence.xml file when I compile my JPA entity classes. While writing this compiler plugin certain things did not behave the way I was expecting. I will talk about them in two parts. In this part I will talk about Java related issues.</description>
<dc:subject></dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2007-11-27T09:40:20-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html">
<title>A javac plugin to manage your persistence.xml</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2007/11/a_javac_plugin_1.html</link>
<description>Java Persistence API specification requires its users to not only provide a persistence.xml file but also enumerate managed persistence class names in that file. In this article, I talk about a Java compiler plugin that can create the persistence.xml file for you automatically during normal course of Java code compilation and show how easy it is to use in your existing build scripts - be it maven or ant or shell script.</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2007-11-26T07:54:43-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/11/welcome_to_glas.html">
<title>Welcome to GlassFish @ FOSS.IN 2006</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/11/welcome_to_glas.html</link>
<description>FOSS.IN is one of the world&apos;s largest and most focussed FOSS events, held annually in India. GlassFish team of Sun Microsystems, which participate in one of the most important open source efforts initiated by Sun Microsystems, will not only talk about GlassFish &amp; Java EE platform, but will also have a live demo running at their booth. This blog gives details about the demo that&apos;s going to be shown their. </description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-11-23T09:00:29-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/10/persistence_con.html">
<title>Persistence Context propagation</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/10/persistence_con.html</link>
<description>While using Java Persistence API in an enterprise application, there is often a need to access access entities in the same persistence context in different components involved in a particular request. Using a very simple Java EE application, this article shows how to achieve this in an elegant and portable way. The technique described here is completely portable across any Java EE 5 compatible application server because it uses a standard feature called *persistence context propagation*.</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-10-27T11:01:45-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/07/using_openjpa_a_1.html">
<title>Using OpenJPA as Java Persistence API provider in GlassFish</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/07/using_openjpa_a_1.html</link>
<description>Pluggability of third party Java Persistence API providers into a Java EE container offers Java EE users exciting combinations to use. Earlier we had shown how to use Hibernate and Kodo in GlassFish. Now it&apos;s time for OpenJPA. I thought I shall give a try using it in GlassFish. This blog reinforces the fact that it could not be easier to plug in a third-party persistence provider in GlassFish.</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-07-27T15:31:02-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/05/using_kodo_as_j.html">
<title>Using Kodo as Java Persistence API provider in GlassFish</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/05/using_kodo_as_j.html</link>
<description>Pluggability of third party Java Persistence API providers into a Java EE container offers Java EE users exciting combinations to use. Earlier we had shown how to use Hibernate in GlassFish. Now it&apos;s time for Kodo, which is another high performance &amp; popular O/R mapping solution. Recently Kodo 4.0GA was released and it supports Java Persistence API. So, I thought I shall give a try using it in GlassFish.</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-05-28T03:44:45-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/05/which_glassfish.html">
<title>Which GlassFish build to use?</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/05/which_glassfish.html</link>
<description>Some of the recent postings in the GlassFish forum suggest that there is some confusion in the GlassFish user community about which GlassFish build to use. This is largely because of activities happening in more than one branch in CVS. I will try to respond to the confusion here.</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-05-05T01:45:53-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/03/using_java_pers_1.html">
<title>Using Java Persistence API in application client in Java EE platform</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/03/using_java_pers_1.html</link>
<description>The Java Persistence API is the standard API for the management of persistence and object/relational mapping in Java EE 5 platform. It can be used in three types of containers, viz: ejb container, web container and application client container. In this blog, we will talk about using this API in application clients. We also discuss two different way of packaging the application.</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-03-21T01:03:23-08:00</dc:date>
</item>
<item rdf:about="http://weblogs.java.net/blog/ss141213/archive/2006/01/when_can_i_use.html">
<title>When can I use hibernate as EJB3 persistence provider in GlassFish</title>
<link>http://weblogs.java.net/blog/ss141213/archive/2006/01/when_can_i_use.html</link>
<description>A number of folks have asked me question about using Hibernate in GlassFish. Read on to know the state of things...</description>
<dc:subject>J2EE</dc:subject>
<dc:creator>ss141213</dc:creator>
<dc:date>2006-01-17T01:08:55-08:00</dc:date>
</item>


</rdf:RDF>
