Hi Giuseppe, just open a pull request, someone else might be able to take a look at it in that case. :-)
regards, Achim 2015-01-20 9:20 GMT+01:00 Giuseppe Gerla <[email protected]>: > Hi JB > Sorry if I come back on this, but for me it is important to use the jpa > configuration from blueprint file. > Any news about this? > > > Thanks > Giuseppe > > 2014-12-30 11:35 GMT+01:00 Jean-Baptiste Onofré <[email protected]>: > > > Hi Guiseppe, > > > > and thanks for the update. > > > > I will take a look asap. > > I keep you posted. > > > > Regards > > JB > > > > > > On 12/27/2014 04:33 PM, Giuseppe Gerla wrote: > > > >> Hi all > >> I worked on this point during holidays and I prepared a working version. > >> In my solution there are 2 PersistenceContextProvider services > registered. > >> The first is GlobalPersistenceManager, same before, but now with > >> property org.apache.aries.jpa.context.type=context. The second one > >> is PersistenceBundleManager with property > >> org.apache.aries.jpa.context.type=unit. In this way, when the NSHandler > >> processes the Blueprint xml file notify unit name and bundle to > "context" > >> service and properties to "unit" service. The "unit" service create a > new > >> EntityManagerFactory using these properties. > >> > >> I think this is the solution with less impact. Please refer to my fork ( > >> https://github.com/ggerla/aries/tree/trunk/jpa) to check the code. > >> > >> > >> regards > >> Giuseppe > >> > >> 2014-12-17 16:37 GMT+01:00 Jean-Baptiste Onofré <[email protected]>: > >> > >> Hi Giuseppe, > >>> > >>> it sounds good to me. Let me give some time to review your changes > >>> deeper. > >>> > >>> Regards > >>> JB > >>> > >>> > >>> On 12/09/2014 01:53 PM, Giuseppe Gerla wrote: > >>> > >>> Hi > >>>> I'm working on two issues in object. I linked them because they are > >>>> duplicated. > >>>> The problem is a small bug in the parser that I resolved to commit > >>>> 56bf3dffd15be41e1e7151993d495c4ef19a87c1 on my fork > >>>> https://github.com/ggerla/aries/. > >>>> Please merge on official trunk and close the issue. > >>>> > >>>> I believe that you will have to open another issue because properties > >>>> that > >>>> are passed to JTAEntityManagerHandler are NOT used to create the > >>>> EnetityManager. > >>>> I try to explain better... Properties specified in jpa:map section are > >>>> passed to JTAEntityManagerHandler to create an EnetityManager > "managed" > >>>> with the call > >>>> > >>>> manager = emf.createEntityManager (props); > >>>> > >>>> where emf is an instance of QuiesceEMFHandler. The > EntityManagerFactory > >>>> implementation first create an EntityManager and then add properties > >>>> passed. So properties are NOT used for the creation. > >>>> I created a test to show that this does not work. > >>>> I also try to fix this problem with > >>>> commit 80bcaca80a09dd088ba25151376b68b646cffb0e. I do not like it so > >>>> much > >>>> but it could be a start point. > >>>> > >>>> > >>>> Wdyt? > >>>> > >>>> > >>>> Giuseppe > >>>> > >>>> > >>>> -- > >>> Jean-Baptiste Onofré > >>> [email protected] > >>> http://blog.nanthrax.net > >>> Talend - http://www.talend.com > >>> > >>> > >> > > -- > > Jean-Baptiste Onofré > > [email protected] > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
