Hi Tim
Tim Ward-2 wrote > I note that since the last set of logs/trace the version of EclipseLink > has increased from 2.6.x to 2.7.x. This changes the JPA version from 2.1 > to 2.2, which currently isn’t supported by Aries JPA or the Tx Control JPA > provider. This will be one of the issues. I have reverted back to 2.6.1. Tim Ward-2 wrote > That the Aries JPA Container bundle doesn’t seem to be deployed (just the > spec API and the EclipseLink Adapter) The JPA Container bundle is deployed, it is just not printed in the list output. If I run it with list -t 0 I can see the bundle. Tim Ward-2 wrote > You have three different copies of the JPA API deployed (one at 2.2, and > two at 2.1) I have removed the 2.2 and only kept the 2.1 Tim Ward-2 wrote > This is a new method added to the JPA service API in version 1.1. If > you’re seeing it appear as a LinkageError, a NoSuchMethodError, or > possibly an AbstractMethodError then this indicates that you have a 1.0 > implementation deployed that has broken import metadata (i.e. it’s > importing a consumer range when it’s a provider). Which bundle do I need to update? Thanks so much Cobus -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
