You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by no...@apache.org on 2011/03/15 14:45:26 UTC
svn commit: r787010 - in /websites/production/aries: ./
content/modules/jpaproject.html
Author: not
Date: Tue Mar 15 13:45:26 2011
New Revision: 787010
Log:
Publishing merge to aries site by not
Modified:
websites/production/aries/ (props changed)
websites/production/aries/content/modules/jpaproject.html
Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Tue Mar 15 13:45:26 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-787006
+/websites/staging/aries/trunk:782169-787009
Modified: websites/production/aries/content/modules/jpaproject.html
==============================================================================
--- websites/production/aries/content/modules/jpaproject.html (original)
+++ websites/production/aries/content/modules/jpaproject.html Tue Mar 15 13:45:26 2011
@@ -252,43 +252,46 @@ Release 4, Version 4.2" available for pu
<p>Step 1 : Module</p>
<p>Every jar deployed on an OSGI platform must be adapted to be conform to OSGI standard. That means that the maven
packaging which is defined as the default value must be defined to bundle</p>
-<p>{code}
- <groupId>org.apache.aries.samples.blog</groupId>
- <artifactId>org.apache.aries.samples.blog.persistence.jpa</artifactId>
- <name>Apache Aries blog sample persistence</name>
- <packaging>bundle</packaging>
-{code} </p>
+<div class="codehilite"><pre><span class="nt"><groupId></span>org.apache.aries.samples.blog<span class="nt"></groupId></span>
+<span class="nt"><artifactId></span>org.apache.aries.samples.blog.persistence.jpa<span class="nt"></artifactId></span>
+<span class="nt"><name></span>Apache Aries blog sample persistence<span class="nt"></name></span>
+<span class="nt"><packaging></span>bundle<span class="nt"></packaging></span>
+</pre></div>
+
+
<p>and that you must configure the maven-bundle-plugin (http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html)
to generate the MANIFEST.MF file required by OSGI platform.</p>
<p>Remark : the modification to be made (packages to be imported or exported depends on your project setting)</p>
-<p>{code}
- <plugin>
- <groupId>org.apache.felix</groupId>
- <artifactId>maven-bundle-plugin</artifactId>
- <configuration>
- <instructions>
- <Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
- <Private-Package>org.apache.aries.samples.blog.persistence.jpa.<em></Private-Package>
- <Export-Package>!org.apache.aries.samples.blog.persistence.jpa.</em></Export-Package>
- </instructions>
- </configuration>
- </plugin>
-{code}</p>
+<div class="codehilite"><pre><span class="nt"><plugin></span>
+ <span class="nt"><groupId></span>org.apache.felix<span class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>maven-bundle-plugin<span class="nt"></artifactId></span>
+ <span class="nt"><configuration></span>
+ <span class="nt"><instructions></span>
+ <span class="nt"><Bundle</span><span class="err">-SymbolicName</span><span class="nt">></span><span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">artifactId</span><span class="cp">}</span><span class="nt"></Bundle-SymbolicName></span>
+ <span class="nt"><Private</span><span class="err">-Package</span><span class="nt">></span>org.apache.aries.samples.blog.persistence.jpa.*<span class="nt"></Private-Package></span>
+ <span class="nt"><Export</span><span class="err">-Package</span><span class="nt">></span>!org.apache.aries.samples.blog.persistence.jpa.*<span class="nt"></Export-Package></span>
+ <span class="nt"></instructions></span>
+ <span class="nt"></configuration></span>
+<span class="nt"></plugin></span>
+</pre></div>
+
+
<p>To allow the Aries JPA Container to setup your persistence layer (akka : instantiate the entityFactory with the information
provided into the persistence.xml file), an additional modification must be made in your pom.xml file to package this file
into the META-INF directory</p>
-<p>{code}
- <plugin>
- <groupId>org.apache.felix</groupId>
- <artifactId>maven-bundle-plugin</artifactId>
- <configuration>
- <instructions>
- <Meta-Persistence>META-INF/persistence.xml</Meta-Persistence>
- ...
- </instructions>
- </configuration>
- </plugin>
-{code}</p>
+<div class="codehilite"><pre><span class="nt"><plugin></span>
+ <span class="nt"><groupId></span>org.apache.felix<span class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>maven-bundle-plugin<span class="nt"></artifactId></span>
+ <span class="nt"><configuration></span>
+ <span class="nt"><instructions></span>
+ <span class="nt"><Meta-Persistence></span>META-INF/persistence.xml<span class="nt"></Meta-Persistence></span>
+ ...
+ <span class="nt"></instructions></span>
+ <span class="nt"></configuration></span>
+<span class="nt"></plugin></span>
+</pre></div>
+
+
<p>When this step is done, your pom.xml file is ready to be used to package and install your bundle into the maven repository
and next into a OSGI container (Apache Felix, Apache Karaf, Eclipse Equinox)</p>
<p>Step 2 : Adapt the persistence file</p>
@@ -299,14 +302,13 @@ the datasource with a key used to find i
specification has made a proposition to provide a similar mechanism that Aries JNDI project covers (http://aries.apache.org/modules/jndiproject.html).</p>
<p>To access to the datasource, you must provide within the <jta-data-source> or <non-jta-data-source> depending if you use a JTA
transaction manager or not.</p>
-<p>{code}
- <persistence-unit name="ReportIncident" transaction-type="JTA">
- <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider></p>
-<div class="codehilite"><pre> <span class="nt"><jta-data-source></span>osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/reportincidentdb)<span class="nt"></jta-data-source></span>
+<div class="codehilite"><pre><span class="nt"><persistence-unit</span> <span class="na">name=</span><span class="s">"ReportIncident"</span> <span class="na">transaction-type=</span><span class="s">"JTA"</span><span class="nt">></span>
+ <span class="nt"><provider></span>org.apache.openjpa.persistence.PersistenceProviderImpl<span class="nt"></provider></span>
+
+ <span class="nt"><jta-data-source></span>osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/reportincidentdb)<span class="nt"></jta-data-source></span>
</pre></div>
-<p>{code}</p>
<p>With J2EE applications, you simply use the jdbc key with the name of the datasource associated (jdbc/reportincidentdb). As OSGI uses a
different mechanism, we must define two parameters, the "osgi:service" wich will allow to find from the OSGI Service registry (aka proxy)
the interface "javax.sql.DataSource" and the name of the service "osgi.jndi.service.name", which is a filter property, with its jndi name associated.</p>
@@ -316,12 +318,12 @@ transaction manager or not.</p>
with the classes of your DAO layer and add Transactional aspect into the methods. This way of work allows to complety
embed existing projects into ARIES sphere without modifications</p>
<p>Here are the modifications to do in the blueprint xml file located under OSGI-INF/blueprint</p>
-<p>{code}
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.0.0"
xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.0.0"
- default-activation="lazy"></p>
+ default-activation="lazy">
+
<div class="codehilite"><pre><span class="nt"><bean</span> <span class="na">id=</span><span class="s">"incidentDAO"</span>
<span class="na">class=</span><span class="s">"org.apache.camel.example.reportincident.dao.impl.IncidentDAOImpl"</span><span class="nt">></span>
<span class="nt"><tx:transaction</span> <span class="na">method=</span><span class="s">"*"</span> <span class="na">value=</span><span class="s">"Required"</span> <span class="nt">/></span> (1)
@@ -349,17 +351,17 @@ embed existing projects into ARIES spher
</pre></div>
-<p></blueprint>
-{code}</p>
-<p>(1) The <tx:transaction> tag allows to inject in your DAO layer the transactional aspect and using the following symbol
+</blueprint>
+
+<p>(1) The <tx:transaction> tag allows to inject in your DAO layer the transactional aspect and using the following symbol
"*", Aries Transaction manager will create for each method a session to begin / commit or rollback a transaction in your class
-The scope of the transaction can be defined using the attribute value.
-(2) The JPA context is created using <jpa:context>. The entityManager (which corresponds to the property of your DAO class) will be
+The scope of the transaction can be defined using the attribute value.<br />
+(2) The JPA context is created using <jpa:context>. The entityManager (which corresponds to the property of your DAO class) will be
injected using the property="entityManager". The reference to your unit name (defined in the persistence.xml file) is passed with the
attribute unitname.
-file.
-(3) The <service> allows to expose an interface on the OSGI Registry Service using as key the name of the interface ("javax,sql.Datasource").
-The <service-properties> will let to define a property that we will use to retrieve the datasource from the registry</p>
+file.<br />
+(3) The <service> allows to expose an interface on the OSGI Registry Service using as key the name of the interface ("javax,sql.Datasource").
+The <service-properties> will let to define a property that we will use to retrieve the datasource from the registry</p>
<p>Step 4 : Package the solution</p>
<p>To package and deploy the solution, execute a "maven clean install" instruction and deploy your project on you OSGI platform</p></div>
<!-- Content -->