Follow-up Karaf-eclipselink feature works as promised. Any discrepancies were most like caused by user-error :-)
Kind Regards, Erwin > On Mar 2, 2015, at 14:08, Erwin Hogeweg <[email protected]> wrote: > > Rodrigo, > >> 1. The value of transaction-type must be JTA. >> 2. you can’t use non-jta-data-source with aries, use jta-data-source. > Just following the examples in the Karaf Cookbook. RESOURCE-LOCAL is the > first step (p172), JTA is not covered until page 182 :-) > >> 3. Maybe you need to make a quick check in aires jpa documentation. > I will go through the Aries documentation as you suggest. > >> 3. After change this can you retest and provide some king of error >> description or exception in karaf log? > Will keep you posted. > > Thanks, > > Erwin > > >> >> Regards, >> Rodrigo >> >> >>> El 2/3/2015, a las 15:42, Erwin Hogeweg <[email protected]> escribió: >>> >>> Hi Rodrigo, >>> >>> Thanks for the response. >>> >>>> Your bundle with persistence.xml file include "Meta-Persistence: >>>> META-INF/persistence.xml" in MANIFEST.MF file? If not you can learn about >>>> JPA in OSGI in this URL: http://aries.apache.org/modules/jpaproject.html. >>> Yes, I think I have all that correct, unless I am overlooking a typo >>> somewhere. >>> >>> Created-By: Apache Maven Bundle Plugin >>> JPA-PersistenceUnits: erwins.pu >>> Meta-Persistence: META-INF/persistence.xml >>> Bundle-RequiredExecutionEnvironment: JavaSE-1.6 >>> >>> >>> <persistence-unit name="erwins.pu" transaction-type="RESOURCE_LOCAL"> >>> >>> >>> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> >>> >>> <!-- The data source is not managed by JTA, and it is obtained >>> via JNDI >>> from the OSGi service registry, using the OSGi JNDI >>> Service. --> >>> >>> <non-jta-data-source>osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/mypunonjta)</non-jta-data-source> >>> >>> Regards, >>> >>> Erwin >>> >>>> >>>> Regards, >>>> Rodrigo >>>> >>>>> El 2/3/2015, a las 15:22, Erwin Hogeweg <[email protected]> escribió: >>>>> >>>>> FWIW, >>>>> >>>>> I am experimenting with the karaf-eclipselink feature that Rodrigo posted >>>>> in the karaf mailing list a couple of weeks ago: >>>>> >>>>>> I create a small project to provide a reasonable way to include support >>>>>> for Eclipselink 2.5.2 in KARAF 3.0.3. This project provide a feature to >>>>>> install Eclipselink 2.5.2 with JPA 2.1 support and example of >>>>>> modification needed in persistence.xml. This modification are needed >>>>>> because Eclipselink need a JTA adaptor to Aries. The adaptor clases was >>>>>> extracted from unused Aries source code. (?) >>>>>> >>>>>> This is the url of project: >>>>>> https://bitbucket.org/rmserra/karaf-eclipselink >>>>>> >>>>>> Regards, >>>>>> Rodrigo >>>>> >>>>> All bundles appear to start properly, but I haven’t been able to get a >>>>> persistence provider yet. >>>>> >>>>> 188 | Active | 30 | 1.0.1 | Apache Aries >>>>> Transaction Blueprint >>>>> 189 | Active | 30 | 1.1.1 | Apache Aries >>>>> Transaction Manager >>>>> 190 | Active | 30 | 2.1.0.v201304241213 | Java Persistence >>>>> API 2.1 >>>>> 191 | Active | 30 | 1.0.2 | Aries JPA >>>>> Container API >>>>> 192 | Active | 30 | 1.0.4 | Aries JPA >>>>> Container blueprint integration for Aries blueprint >>>>> 193 | Active | 30 | 1.0.2 | Aries JPA >>>>> Container >>>>> 194 | Active | 30 | 1.0.4 | Aries JPA >>>>> Container Managed Contexts >>>>> 195 | Active | 30 | 3.2.0.v201302191141 | EclipseLink ANTLR >>>>> >>>>> 196 | Active | 30 | 3.3.1.v201302191223 | EclipseLink ASM >>>>> >>>>> 197 | Active | 30 | 2.5.2.v20140319-9ad6abd | EclipseLink Core >>>>> >>>>> 198 | Active | 30 | 2.5.2.v20140319-9ad6abd | EclipseLink Hermes >>>>> Parser >>>>> 199 | Active | 30 | 2.5.2.v20140319-9ad6abd | EclipseLink JPA >>>>> >>>>> 200 | Active | 30 | 1.0.2.SNAPSHOT | Karaf :: >>>>> Eclipselink >>>>> >>>>> Regards, >>>>> >>>>> Erwin >>>>> >>>>> >>>>> >>>>>> On Mar 2, 2015, at 11:37, Christian Schneider <[email protected]> >>>>>> wrote: >>>>>> >>>>>> There is no real Aries 1.0.0. Aries consists of a set of bundles that >>>>>> are each versioned independently. >>>>>> So you need to specify which exct set of bundles you used. >>>>>> >>>>>> Honestly it is quite difficult to get the combinations correctly. So I >>>>>> propose you try karaf 3.0.3 and install the aries modules you want from >>>>>> there. This will give you a working set of bundles. >>>>>> About the eclipslink support .. We got itests for it but I personally >>>>>> never tested it manually. I heard though that the newest eclipselink >>>>>> should work without the adapter. >>>>>> >>>>>> About 2). Yes I consider aries jpa to be production ready but you need >>>>>> to use the most current releases. The 1.0.0 version are definately not >>>>>> production ready. >>>>>> >>>>>> Christian >>>>>> >>>>>> >>>>>>> On 25.09.2012 02:32, Anatoly Osiko wrote: >>>>>>> Hello, JPA users, and hopefully, developers. >>>>>>> >>>>>>> RE: Aries 1.0.0, Aries trunk: jpa/jpa-container-eclipselink-adapter >>>>>>> >>>>>>> I managed Aries 1.0.0 declarative transaction support (via blueprint >>>>>>> container) to work with EclipseLink JPA only with the eclipselink >>>>>>> adapter, which, the latter, was compiled by me from the trunk of Aries, >>>>>>> and which doesn't appear in any "official" versioned release? >>>>>>> >>>>>>> Can anyone, please, enlighten me on >>>>>>> 1) the status of the org.apache.aries.jpa.eclipselink.adapter bundle >>>>>>> specifically, >>>>>>> and >>>>>>> 2) if Aries 1.0.0 is ready for the production use. >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> Anatoly. >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Christian Schneider >>>>>> http://www.liquid-reality.de >>>>>> >>>>>> Open Source Architect >>>>>> http://www.talend.com >>>>>> >>>>> >>>> >>> >> >
