Hi JB, May I have the issue number, if it is already created?
Meanwhile is there any workaround for this problem? (other than downgrading Aries version) Thanks, Mohammad Shamsi On Wed, 2 Sep 2015 at 13:18 Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi Mohammad, > > it sounds like a bug in Aries JPA Blueprint. > > I gonna create the Jira and fix that. > > Regards > JB > > On 09/02/2015 12:19 PM, Mohammad Shamsi wrote: > > Hi All, > > > > I am upgrading an application from Karaf 3.0.3 to 4.0.1 and facing an > > strange JPA related issue. > > > > As it mentioned in the email title, the JPA related bundle is waiting > > for JPA namespace handler. > > > > I can see that "Aries JPA Blueprint" version 2.1.0 is started > > successfully but it is registering a slightly different namespace > handler: > > > > */objectClass = [org.apache.aries.blueprint.NamespaceHandler]/ > > * > > */osgi.service.blueprint.namespace = > > http://aries.apache.org/xmlns/jpan/v1.0.0/ > > * > > > > As you see the url contains "jpan" but not "jpa". > > > > I tried to change the url in the blueprint xml file and add "jpan" > > instead of "jpa" but faced another issue in runtime: > > */Caused by: org.xml.sax.SAXParseException; cvc-complex-type.2.4.c: The > > matching wildcard is strict, but no declaration can be found for element > > 'jpa:context'./* > > */ > > /* > > Any idea what could be the possible issue? > > > > Regards, > > Mohammad Shamsi > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
